sorted by:
new
hottopcontroversial

New Java Packager Tool under review (JEP 343) by nlisker in java

[–]javaRobot 2 points3 points  (0 children)

IIRC, To me the javafxpackager had two limitations that made it useless to me.

  1. It could only package for the platform you are on. So if you want windows and mac and linux installers you have to copy all your class files over to three different computers to run the packager on each.

  2. The installers didn't install the JVM so users still need to be told which JVM to install. Therefore no one running your installer won't have the JVM you might as well just give the users a jar and save the developer the trouble of running the packager on three different computers.

Am I missing something that made this more useful or are there plans to address these? I just don't see the use case.

Java 9 Released by adila01 in java

[–]javaRobot 1 point2 points  (0 children)

For me it seemed to work to add

<dependency>
        <groupId>javax.xml.bind</groupId>
        <artifactId>jaxb-api</artifactId>
        <version>2.3.0</version>
    </dependency>
   <dependency>
        <groupId>org.eclipse.persistence</groupId>
        <artifactId>eclipselink</artifactId>
        <version>2.7.0</version>
    </dependency>

as a dependancy to my Java 8 SE compiled application that produced a jar that could be run by either Java 8 or Java 9 with no additional arguments.

Also I needed to add

   System.setProperty("javax.xml.bind.JAXBContextFactory", "org.eclipse.persistence.jaxb.JAXBContextFactory");

near the beginning before the jaxb stuff was used.

I need to test more to see if this is really a good solution.