1. META-INF resources
Dealing with META-INF resources in a cross platform independent way is not as easy as it sounds given that some versions of Windows simply disregard directory names with all caps and treat them as all lower caps. But Ant knows how to deal with this problem, and given that Gant is built on top of Ant so does Griffon. Placing a file under griffon-app/conf/metainf means it will be packaged inside the jar's META-INF directory. It even works for any directories you place there. As an added benefit of this new resource location is that all resources that are placed there will also be transparently available during testing, your code won't know the difference.2. Plugin packaging
Plugins have received a huge face lift in this release, one of the main areas is packaging. During plugin/addon packaging the following jars may be generated- griffon-<name>-<version>-sources.jar - contains all source files from griffon-app/*, src/main, src/test and additional source directories configured in Buildconfig.groovy
- griffon-<name>-<version>-javadoc.jar - contains groovydocs generated for all sources.
- griffon-<name>-<version>-test.jar - contains all compiled tests sources form src/test and all test resources from test/resources
3. Installer plugin integration
Griffon's package command let's you package an application in 4 default formats: zip, jar, applet and webstart. The Installer plugin provides additional installer/launcher targets, like izpack, rpm, deb, mac and windows. Until now you had to call the plugin's scripts to package the application for a particular target, for examplegriffon prepare-izpack griffon create-izpack
griffon package izpack
Keep on Groovying!
