Jason just announced the release of maven-jar-plugin 2.1. (Thanks!)
Now I'm going to pick on the documentation. :) One of the major problems we had with the jar plugin was invalid manifests. The plugin would use the <description> as-is for Specification-Title, including line breaks, resulting in an invalid manifest. On this page http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html I read that "By default a manifest will contain something like the following: Manifest-Version: 1.0 Built-By: ${user.name} Created-By: Apache Maven Build-Jdk: ${java.version} Extension-Name: ${project.artifactId} Specification-Vendor: ${project.organization.name} Implementation-Vendor: ${project.organization.name} Implementation-Title: ${project.description} Implementation-Version: ${project.version} " Great, we're using <name> for Specification-Title now. That should be a single line, so no problem. Then I build a jar file, and the manifest contains only: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: wsmoak Build-Jdk: 1.5.0_05 Not quite what I expected. Using Emmanuel's suggestion of adding <configuration> also does not work. <configuration> <manifest> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries> <addDefaultImplementationEntries>true</addDefaultImplementationEntries> </manifest> </configuration> The documentation really needs to be fixed to reflect the true default manifest contents, and re-published. The fact that the suggested configuration doesn't work is another issue. And I can't find a list of what is allowed in <configuration> to double check what I'm doing. This is the reason I asked for a link to the wiki on every plugin page, so users at least have a chance to list errata and supply working examples until the site can be corrected. :( -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
