Resources loaded from refpack is not relative to pack definition


When loading a refpack in a separate directory, resources need to be relative the install.xml. See




René Krell
July 27, 2018, 9:58 AM

Thanks for reporting, . Hopefully there will be someone to fix this, I'm fairly busy at the moment.

Eric Rose
July 27, 2018, 1:36 AM

I'm going to drop this issue WRT this bug. There is something odd going on with the refpackset usage that has changed between 5.1.1 and 5.1.2 and packs aren't picked up correctly using my old configuration. If I move the refpack elements from the refpackset file into the main descriptor, it all works, but the two-level reference doesn't work. If it appears this is a bug, I'll create a new report for it, but I need to investigate further.

Eric Rose
July 24, 2018, 3:40 AM

BTW, an explanation of the path structure in our projects: we have src/main/izpack/ as the location of the descriptor and all other izpack files and that hierarchy gets copied into target/staging/ basically as-is. I don't know if there are issues with such a process - we haven't seen any before.

Eric Rose
July 24, 2018, 3:36 AM

I have the same issue in 5.1.3. Interestingly, I can use the path "${staging.dir}/A/${izpack.basedir}/pack-specs" in the installation descriptor and the include resolves to "/home/ericr/workspace/work/mi-installer-spectrum/target/staging/A/src/main/izpack/pack-specs/ref.xml" but using "${staging.dir}/${izpack.basedir}/pack-specs" resolves the include to:


I don't know if that helps, or not. So far, I haven't been able to use any combination of izpack/maven variables that resolves to the correct path, either absolute or relative, to give me the correct location of the pack ref.

René Krell
June 25, 2018, 8:56 AM

, is it possible this change caused the trouble of , are you able to help him with this, please?

Your pinned fields
Click on the next to a field label to start pinning.


Tomas Forsman


Tomas Forsman