diff --git a/java/project.xml b/java/project.xml index 9be5f2ef..2e3025f6 100644 --- a/java/project.xml +++ b/java/project.xml @@ -22,7 +22,7 @@ 3 maven-java-plugin Maven Java Plugin - 1.6.1-SNAPSHOT + 1.6.1 Compile java code @@ -46,6 +46,11 @@ 1.6 MAVEN_JAVA_1_6 + + 1.6.1 + 1.6.1 + MAVEN_JAVA_1_6_1 + diff --git a/java/xdocs/changes.xml b/java/xdocs/changes.xml index fa43067e..6d147727 100644 --- a/java/xdocs/changes.xml +++ b/java/xdocs/changes.xml @@ -17,78 +17,78 @@ * limitations under the License. */ --> - - - Changes - dIon Gillard - Kurt Schrader - - - - Java report fails build if no source files present. - - - Compile fails using forked compiler when directory contains spaces. + + + Changes + dIon Gillard + Kurt Schrader + + + + Java report fails build if no source files present. + + + Compile fails using forked compiler when directory contains spaces. Also check for ${maven.gen.src}before compiling. - + New property maven.compile.failonerror. - + New property maven.compile.debuglevel. - + New property maven.compile.nowarn. - + Set maven.compile.deprecation=onby default. - - Compiling gives incorrect warning about target JVM version. - + + Compiling gives incorrect warning about target JVM version. + sourceModificationshandled incorrectly when more than one clause present. - - Broken support for maven.compile.extdirs. - Make a report with compiler output - Capture Deprecation Warnings. - - - Make it work by default with any version of the JDK - Deprecate dependency handle - Use assert taglib for tests - - - Allow specifying a JDK to compile with other than the running one - Add memory usage parameters to pass to the ant javac task - Add source property, default to 1.3. This is required to use JDK 1.5. - - - Remove clean goals and jar goals. Clean goals and jar goals move to clean plugin and jar plugin. - Added chgrp maven to jar:deploy. - Added velocity.log to files deleted on clean - - - Added the jar:install-snapshot goal to install a SNAPSHOT version jar in the local repository. - Added maven.compile.encoding property - Added docs on properties - - + + Broken support for maven.compile.extdirs. + Make a report with compiler output + Capture Deprecation Warnings. + + + Make it work by default with any version of the JDK + Deprecate dependency handle + Use assert taglib for tests + + + Allow specifying a JDK to compile with other than the running one + Add memory usage parameters to pass to the ant javac task + Add source property, default to 1.3. This is required to use JDK 1.5. + + + Remove clean goals and jar goals. Clean goals and jar goals move to clean plugin and jar plugin. + Added chgrp maven to jar:deploy. + Added velocity.log to files deleted on clean + + + Added the jar:install-snapshot goal to install a SNAPSHOT version jar in the local repository. + Added maven.compile.encoding property + Added docs on properties + + Added - goals documentation - - Added maven.compile.source, maven.compile.target, maven.compile.executable, maven.compile.fork and maven.compile.compilerargs properties to allow people with generics to build with Maven - Compilation now only happens if java source is present - Applied fix for MAVEN-102, which allows a manifest file to be specified, as well as the defaults when jar'ing. + goals documentation + + Added maven.compile.source, maven.compile.target, maven.compile.executable, maven.compile.fork and maven.compile.compilerargs properties to allow people with generics to build with Maven + Compilation now only happens if java source is present + Applied fix for MAVEN-102, which allows a manifest file to be specified, as well as the defaults when jar'ing. Added goals installing and deploying the plugin: -
    -
  1. plugin:install installs the plugin in Maven's plugins dir
    2. -
  2. plugin:deploy installs an unpacked version of the plugin in Maven's plugins dir
    3. -
-

This is meant to ease the installation of plugins without having to bootstrap or manually copy the generated plugin to Maven's plugins dir.

- - - - Initial plugin created - - +
    +
  1. plugin:install installs the plugin in Maven's plugins dir
    2. +
  2. plugin:deploy installs an unpacked version of the plugin in Maven's plugins dir
    3. +
+

This is meant to ease the installation of plugins without having to bootstrap or manually copy the generated plugin to Maven's plugins dir.

+ + + + Initial plugin created + +