Menu ▾ ▴

#13 Support for relative paths

open
Manodasan Wignarajah
Interface Improvements (8)
5
2010-06-23
2010-06-23
drekbour
No

Packjacket always writes a hard-coded path to a <pack> files etc. Different developers may use different locations or operating systems!

Currently I have to "generate XML" then manually delete all paths (following the recommended Maven pattern, the izpack materials are all collected into an assembly directory before invoking it so no paths are required and everything is portable).

Recommendation: Include a "relative path" flag (ticked by default I feel). If selected, the "Generate XML" process will attempt to make all hard-coded paths relative to the location of the install.xml being saved and warn for any it cannot.

Discussion

  • Manodasan Wignarajah

    Manodasan Wignarajah - 2010-06-23

    We are currently working on this feature already and hope to have it ready for the next version of PackJacket.

     

  • Manodasan Wignarajah

    Manodasan Wignarajah - 2010-06-23
    • labels: --> Interface Improvements
    • assigned_to: nobody --> manodasan
     

  • Nobody/Anonymous

    Nobody/Anonymous - 2010-11-24

    Also would like to have "relative path" AND
    - make file path boxes in PackJacket editable ( so I can manually edit or even remove the filepath. Once a filepath has been specified, it is not possible NOT to specify a filepath GUI panel, side image and logo)
    - would there be a way to edit the .pjc project file to correct this?

     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB