

It’s looking for an ist file to be in the build directory. Set up the build.xml file from the various entries on the and Oracle articles referenced above and running ant causes a no such file exception.
Bundle java for os x 2017 001 mac os x#
Manually creating an App Bundle, Java 7 (1.7.0_45-b18), Mac OS X 10.9.2ĭownloaded appbundler-1.0.jar from, as described in the Oracle article above and put it in a test directory. why would eclipse claim to produce an app bundle if it did it the wrong way? Is it? Time to go build one manually and see. This article seems to imply a tool is needed at Java 7, so yep, great but why wouldn’t that be in eclipse already, i.e. So we check the ist in the app bundle, and find the main class is defined. This however is a rat-hole, there is indeed no main entry point defined in the manifest but a few more searches reveal the package isn’t invoked using java -jar xx.jar, it’s invoked using java -cp xx.jar mainEntryPoint.

A quick search around Console, shows:Ī quick google makes suggestions like there’s no main entry point defined in the jar file

Into Finder, double clicked the app and nothing happens. What was I trying to achieve was to create mac app bundle to put in a dmg to distribute my java desktop app. In Eclipse, generated a Mac app bundle using the export task. Lost 6 hours of my life tracking down this issue, and of course in the end it turns out to be my user error, although as always as a developer you challenge whether it needed to be this hard to debug.
