1.1.0

Some major improvements including changes to the generated .woa bundle structure, buildtime/runtime modification of bundle configuration (jvm, jvmOpts etc). Details in CHANGES.md.

New bundle structure (.woa)

• Removed all platform-specific directories, files and scripts (Contents/MacOS/, Contents/UNIX/, Contents/Windows/, MacOSClassPath.txt, UNIXClassPath.txt, MacOSXServerClassPath.txt, CLSSPATH.TXT, SUBPATHS.TXT)
• Removed Windows .cmd launch script
• Replaced the platform-specific classpath files with two simple files at the WOA root: config.txt and classpath.txt

Configurable Launch script

• jvm, jvmOptions, jdb, and jdbOptions are configurable in build.properties as they are in wolifecycle.
• In addition to build.properties these can now also be set as properties at different times, prefixed with launch.
  • At build time: mvn package -Dlaunch.jvm=/my/java, changes the value written to config.txt
  • At app launch time (CLI or JavaMonitor arguments): ./MyApp.woa/MyApp -launch.jvm=/my/java
  • Finally, you can use "environment specific" build.properties files to override properties. For example, if you have a build.properties.prod file, you can invoke maven with mvn package -Dbuild.env=prod and any values present in build.properties.prod will then override any values from build.properties.
  • So, who wins? Properties end up being looked up in this order — first with a value wins:
    • runtime args
    • buildtime args
    • build.properties.{environment}
    • build.properties
    • defaults

Maven integration

• New <createArchives> option creates tar.gz archives from the build products and attaches them as Maven artifacts for use with mvn install and mvn deploy (closes #7)

Housekeeping

• Renamed ng package to vermilingua (closes #35)
• Removed pinned plugin versions from lifecycle mappings — Maven resolves versions from its own defaults
• Various code cleanups and internal refactoring

Full Changelog: v1.0.6...v1.1.0