Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#59 Mavenize the core code

Next Release
General (39)

Hi, I could see the two plugins linked on your site. It's a nice approach and very useful, but both are outdated.
It seems that those plugins are copying the code of L4J and put inside them code, so because this we can't use 3.0.2 with maven.
Would be very interesting to mavenize the necessary code (create a POM and deploy it to a maven repo) of this projects, so being be easy to maintain all projects in sync.

cheers and thanks for this excellent tool.


  • My thoughts is to divide the project in 3 parts (initially). launch4j-core, launch4j-ui, launch4j-demos.. and adequate the build for using maven 3.
    I already done that in my local repo for the launch4j-core, that what I need first for my internal maven deployment.
    But I can't finish for launch4j-ui yet because I just can't find a jar at any repository that contain the class com.jeta.forms.components.separator.TitledSeparator

    Does anyone knows about this class ?


  • +1 for mavenization

  • +1

  • Grzegorz Kowal
    Grzegorz Kowal

    • Priority: 5 --> 6
  • Lukasz Lenart
    Lukasz Lenart

    Just to let you know that I'm trying keep this plugin [1] up2date. The only problem is the Launch4j isn't pushed to Maven Central - changing that will make my life easier with publishing new versions :)

    [1] https://github.com/lukaszlenart/launch4j-maven-plugin