When I first started using appassembler, I used programs, since I didn't need arguments at first. Using the assemble goal stuck these into a bin directory alongside the repo directory that was created.
This was really handy, because you could run the scripts without needing to run the package phase and the assembly descriptor was simpler. When I first created a (unix) daemon, I spent a long time looking for the resulting file, since the generated location was not clearly documented anywhere. It didn't help that when I finally found it, it was broken (MAPPASM-92). I'd like to add the option to place the output from generate-daemons in the assembleDirectory directly, without the intervening platform directory (i.e. directly into bin/). Advantages of putting daemon objects into assembleDirectory directly: - Scripts work in place when plugin runs, before package phase, saving time during development and testing - maven-assembly-plugin descriptors are simplified Disadvantages: - conflicting file names between unix/windows(booter?) and jsw which would require configuration parameter and/or loading change Other than the obvious avoiding of conflicts, is there any other advantage to using an extended path to store the generated daemons? -Dave P.S. Is this something good to discuss on the list or should this just be a ticket?
