Allow manual control of classpath configuration about gradle-launch4j HOT 3 CLOSED

I think this can be incorporated into the copyConfigurable with a change in CreateXML

from gradle-launch4j.

@alexanderfloh would the commit help?

from gradle-launch4j.

@TheBoegl, thanks for the enhancement, I finally got around to give it a try.

Unfortunately I'm still unable to build my application, so I'll try to give more context.
As mentioned before, the application consists of multiple modules, and the distribution should look like this (items marked with a * should go in the classpath):

outputDir
| application.exe
+ \ module A
  + \ moduleA.jar *
    + \ lib (native .DLLs go here)
    + \ config *
    | <arbitrary other files>
+ \ module B
  + \ moduleB.jar *
    /* ... */
+ \ <third party libs> *

Ideally, I'd like to be able to convince the launch4j plugin to not make any assumptions about my directory structure. Just point it at a directory, specify what should be included in the classpath and have it generate an .exe-file.

Alternatively, being able to provide a CopySpec for copyConfigurable might work as well for me, but I'm a bit worried about that resulting in an unnecessary amount of copies of the output files.

Thanks for investing your time in this, I appreciate it.

from gradle-launch4j.