gradle-getdown-plugin hide installation/usage of launch4j

Today launch4j should be installed manually by users, then user should configure the path for the plugin (eg into $HOME/.gradle/gradle.properties). It would be fine if launch4j can be downloaded, installed (in cache) like in launch4j-maven-plugin, then user doesn't care if it's launch4j or an other backend-tool used to create .exe for windows. But a configuration should be keep to let user decide if he want to generate a .exe (via launch4j) or generate a script to launch the app on windows.

Nov 17 '14 14:11 davidB

What about adding support of https://plugins.gradle.org/plugin/edu.sc.seis.launch4j? Then user don't need to specify path to it.

Sep 03 '15 11:09 petrukhnov

Thanks for the suggestion, It's not clear if this plugin download launch4j or if it used a local installed (in PATH).

PS: sorry I forgot to hit "comment" button to submit.

Sep 07 '15 12:09 davidB

It will download launch4j and put it in build folder, then use it during build process.

Sep 07 '15 13:09 petrukhnov

I'll see if getdown-plugin can support/drive this plugin. Thanks for the info, (PR welcome ;-) )

On Mon, Sep 7, 2015 at 3:27 PM, Konstantin Petrukhnov < [email protected]> wrote:

It will download launch4j and put it in build folder, then use it during build process.

— Reply to this email directly or view it on GitHub https://github.com/davidB/gradle-getdown-plugin/issues/15#issuecomment-138298026 .

Sep 07 '15 15:09 davidB