Page History

...

Status: Maven 2's assembly plugin lets you group filesets with a particular line ending and file mode, but these are not treated differently between zip and tar.gz without recreating the descriptor. I prefer this operation - making the main text files and batch files CRLF, shell scripts LF, and everything else untouched. Modern editors on both systems work with either, so all we need is for notepad to be able to read the .txt files, really.

The maven 1 dist plugin has been patched (in svn, pending 1.7 release) to support configurable filters for both crlf and lf conversion. CRLF is applied only in zip archives, lf (if present) afterwards. See http://jira.codehaus.org/browse/MPDIST-28.

Accurate Building Against 1.3

...

(More Info) It feels like the 'maven way' would be to specify the target JVM in the POM. Of course, it's not that easy. One of the wrinkles is that it may be that the way I've always done targetted releases (using a JVM of the current vintage) is not actually the right way. The problem is that older compilers may have bugs which have been addressed in later releases. So, AFAIK the best advice is to use -bootclasspath set and then use a modern JVM with the correct flags set.

Alternatively, in m1, maven.compile.executable can be set to force compilation on a specific jdk. The jar plugin (or comparable m2 thingy) should be able to record the correct jdk version in the manifest (m1 cannot do this currently).

IDE Friendly Source And Javadoc Jars

...

Brett has written on a solution to improve the multiproject site: http://maven.apache.org/plugins/maven-assembly-plugin/descriptor.html (above link looks misplaced - not clear what this has to do with site generation)

• Individual commons component sites must be able to be built independently and fully from svn and source distributions
• Commons component sites need to share a common look and feel, which may not be the same as the maven-supplied default
• Commons component sites need to share common navigation elements
• Site generation must include support for versioned javadocs
• It would be great not to have to include all of the images with all of the component sites and to reduce the size (incredible amounts of needless white space) of the generated html.