...
- Clear distinction between other running Tomcat instances
- Integration with desktop application launchers
- Shipping an a Tomcat-based product
In my particular use case I was creating native launchers for Apache JSPWiki (see https://jspwiki.apache.org)
...
- for Mac OS and Oracle JDK you can use AppBundler (see http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/packagingAppsForMac.html)
- for Windows you can use Launch4J (see http://launch4j.sourceforge.net)
The goal is to habe
Mac OS X AppBundler
The following snippet
...
- "APP_ROOT" is the directory of the Mac OS X launcher and will be expanded accordingly during run-time
- The current working directory is undefined therefore all "important" properties must be provided
- The two referenced JARs are effectively copied into the native launcher
- No JRE is packaged since it assumed that the JRE is available on the target box
- If you need to change the memory settings for an existing native app than you can edit the "Info.plist" directly
- If the native app is starting at all you get no error message which is a bit annoying - as work-around you can launch at the command line to see the output, e.g "./woas.app/Contents/MacOS/JavaAppLauncher"
Windows Launch4J
- Defines an a Ant task definition "launch4j"
- Invokes the "launch4j" tasks to create a native Mac OS X launcher
...