onexip / jarbundler Goto Github PK

The link on the main page:

"Take a look at ./docs/index.html (Currently outdated. Sorry.)"

points to a non-existing site instead of the ./docs/index.html from the current HEAD revision.

Regards, Peter.

@slajar @tobium I did a couple of fixes and refactoring this weekend. This is the changelog:

• Massive code refactoring
  • code formatting
  • specify maven source encoding
  • fix Ant build files
  • run examples with a modern JavaApplicationStub (universalJavaApplicationStub)
• Bugfix: JarBundler on Windows created a classpath with backward slashes which broke the Info.plist file on macOS
  • \ in classpath are now replaced with /
• Remove support for Java 1.3
  • if no jvmversion attribute is set, the default version is now 1.4+
  • removed deprecated growboxintrudes attribute
  • removed deprecated liveresize attribute
  • removed deprecated smalltabs attribute
• Updated HelloWorld example to show JVM details, classpath and mainArgs
• Support for Java 9+ in jvmversion attribute

Additionally we already had these improvements on master since 3.3.0 release:

• Updates to docs and examples
• Optional supportsAutomaticGraphicsSwitching attribute which defaults to true (for Plist key NSSupportsAutomaticGraphicsSwitching)
  • PullRequest !14, thanks to Björn Kautler (@Vampire) for his contribution!
• Update Ant from 1.9.3 to 1.9.14

I tested with Maven and Ant and it seems stable :-)

May I suggest to release version 3.4.0 on Maven central? You still need to update the SNAPSHOT version and Readme Changelog once you're ready, but everything else should be good to go.

I've been working on a cloned version of jarbundler-3.3.0. I had thought of publishing it myself, but are you interested in a pull request? Small things so far (getting rid of deprecation warnings; JVMVersion also in Oracle plist; parsing modern version numbers (e.g. "9+") in setJVMVersion).

If you are interested, I'll send a pull request. If not, I'll keep it to myself. :-)

System
Model: MacBook Pro Retina, 13-inch Early 2015
OS: macOS Monterey
Java edition: JDK 8 (All Oracle)
Error
There is no main manifest in my Jarbundler jar file. This won't let me use jarbundler.

It is not finding the class loader. I get this:

Marisas-Mini:ThudNG-1.0 fstltna$ ant
Buildfile: /Users/fstltna/Documents/ThudNG2/ThudNG2/ThudNG-1.0/build.xml

BUILD FAILED
/Users/fstltna/Documents/ThudNG2/ThudNG2/ThudNG-1.0/build.xml:19: taskdef class net.sourceforge.jarbundler.JarBundler cannot be found
 using the classloader AntClassLoader[]

Total time: 0 seconds

Please help!

I’m building a GUI in Java using Eclipse and came across your AppBundler while looking for a way to bundle the .jar I had created as a mac application. I was wondering, after running the test code you had provided, how I can use the AppBundler with a .jar file that has already been made.

Hi,

I'm one of the recent contributors to informagen's JarBundler and I've added some improvements in the past year which didn't make it in the official release.
That's why they live in a separate repo here on GitHub: https://github.com/tofi86/Jarbundler/

It would be nice if you could merge these changes to your official repo now that you've taken over the ownership of JarBundler!

Modifications (also see my Readme):

• version 2.5.0 (2015-11-06)
  • Added optional contentSize attribute to JarBundler task (for Plist key NSPreferencesContentSize)
• version 2.4.0 (2015-05-15)
  • Added optional useJavaXKey attribute to JarBundler task (for universalJavaApplicationStub-Support)
  • Added optional hiResCapable attribute to JarBundler task (for Plist key NSHighResolutionCapable)
  • removed deprecated aboutmenuname attribute
  • removed deprecated infostring and shortinfostring attributes (use copyright attribute instead)
• version 2.3.0 (2014-04-01)
  • Added optional copyright attribute to JarBundler task (for Plist key NSHumanReadableCopyright)
  • Issue a warning when using deprecated aboutmenuname attribute
  • Issue a warning when using deprecated shortinfostring attribute
• version 2.2.1 (2014-01-25)
  • Added optional allowMixedLocalizations attribute to ant task. If true, the bundle supports the retrieval of localized strings from frameworks. This should be set to true if your app supports different languages. Default: false

The maven version number in pom.xml (3.2.2) and the ant build version number in build.xml (2.3.2) deferr.

I assume they should be matching, right?