You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by bu...@apache.org on 2016/01/24 13:28:54 UTC
svn commit: r978467 - in /websites/staging/maven/trunk/content: ./
docs/3.3.1/release-notes.html maven-site-1.0-site.jar
Author: buildbot
Date: Sun Jan 24 12:28:54 2016
New Revision: 978467
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/docs/3.3.1/release-notes.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jan 24 12:28:54 2016
@@ -1 +1 @@
-1726479
+1726483
Modified: websites/staging/maven/trunk/content/docs/3.3.1/release-notes.html
==============================================================================
--- websites/staging/maven/trunk/content/docs/3.3.1/release-notes.html (original)
+++ websites/staging/maven/trunk/content/docs/3.3.1/release-notes.html Sun Jan 24 12:28:54 2016
@@ -465,10 +465,8 @@
NOTE: For help with the syntax of this file, see:
http://maven.apache.org/doxia/references/apt-format.html -->
<div class="section">
-<h2><a name="Maven_3.3.1"></a>Maven 3.3.1</h2>
-<p>The Apache Maven team would like to announce the release of Maven 3.3.1. Many thanks for Karl Heinz Marbaise for writing up the most complete release notes which you can find here:</p>
-<p><a class="externalLink" href="http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features/">http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features/</a></p>
-<p>Maven 3.3.1 is <a href="../../download.html">available for download</a>.</p>
+<h2><a name="Overview"></a>Overview</h2>
+<p>The Apache Maven team would like to announce the release of Maven Version 3.3.1. The new Maven Version is <a href="../../download.html">available for download</a>.</p>
<p>Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project’s build, reporting and documentation from a central place.</p>
<p>Maven 3 aims to ensure backward compatibility with Maven 2, improve usability, increase performance, allow safe embedding, and pave the way to implement many highly demanded features.</p>
<p>The core release is independent of the plugins available. Further releases of plugins will be made separately. See the <a href="../../plugins/index.html">PluginList</a> for more information.</p>
@@ -482,10 +480,171 @@
<li>the reference documentation: <a class="externalLink" href="http://maven.apache.org/ref/3.3.1/">http://maven.apache.org/ref/3.3.1/</a></li>
</ul>
-<p>The full list of changes can be found in our <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12330193">issue management system</a>.</p></div>
+<p>The full list of changes can be found in our <a class="externalLink" href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12330193">issue management system</a>.</p>
+<p>The full list of all release notes for all versions can be found on the <a href="../../docs/history.html">history page of the Maven project</a>.</p></div>
<div class="section">
-<h2><a name="Complete_Release_Notes"></a>Complete Release Notes</h2>
-<p>See <a href="../../docs/history.html">complete release notes for all versions</a></p></div>
+<h2><a name="Release_Notes_In_Detail"></a>Release Notes In Detail</h2>
+<p>The new <a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/maven-announce/201503.mbox/%3C1954448.IV3m89R0sE%40herve-desktop%3E">Maven 3.3.1 Release is just out</a>. Let us take a deeper look into the new features/improvements:</p>
+
+<ul>
+
+<li>The first and most important thing is that <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5780">Maven 3.3.1 needs JDK 1.7</a>.</li>
+</ul>
+<div class="section">
+<h3><a name="Toolchains"></a>Toolchains</h3>
+
+<ul>
+
+<li>
+<p>In our days it becomes more and more important to be able to use different JDK to be used by Maven itself and which is used to compile/test your production code. This concept is know under the name <a href="../../download.html">Toolchains</a> which is unfortunately not very well-known.</p></li>
+
+<li>
+<p>The handling of the <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-3891"><tt>toolchains.xml</tt></a> file has been adjusted with the handling of <tt>settings.xml</tt> which means it will be searched within the <tt>${maven.home}/conf/</tt> folder and furthermore within the <tt>${user.home}/.m2/</tt> folder.</p></li>
+
+<li>
+<p>For a better understanding and as an example of the <tt>toolchains.xml</tt> file has been added to the <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5745">Maven distribution</a>.</p></li>
+
+<li>
+<p>Maven has been improved to read the <tt>toolchains.xml</tt> file <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5754">during initialization</a> instead of waiting till <a class="externalLink" href="http://maven.apache.org/plugins/maven-toolchains-plugin/">maven-toolchains-plugin</a> will read it.</p></li>
+</ul></div>
+<div class="section">
+<h3><a name="Core_Extensions"></a>Core Extensions</h3>
+
+<ul>
+
+<li>
+<p>Core Extension mechanism has <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5771">been improved</a> to make it simpler to use.</p></li>
+
+<li>
+<p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you have other dependencies) which contains the extension and put it manually into the <tt>${MAVEN_HOME}/lib/ext</tt> folder. This means you had to change the Maven installation. The consequence was that everyone who likes to use this needed to change it’s installation and makes the on-boarding for a developer much more inconvenient. The other option was to give the path to the jar on command line via <tt>mvn -Dmaven.ext.class.path=extension.jar</tt>. This has the drawback giving those options to your Maven build every time you are calling Maven. Not very convenient as well.</p></li>
+
+<li>
+<p>From now on this can be done much more simpler and in a more Maven like way. So you can define an <tt>${maven.projectBasedir}/.mvn/extensions.xml</tt> file which looks like the following:</p></li>
+</ul>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"><extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
+ <extension>
+ <groupId/>
+ <artifactId/>
+ <version/>
+ </extension>
+</extensions>
+</pre></div></div>
+
+<ul>
+
+<li>Now you can simply use an extension by defining the usual maven coordinates <tt>groupId</tt>, <tt>artifactId</tt>, <tt>version</tt> as any other artifact. Furthermore all transitive dependencies of those extensions will automatically being downloaded from your repository. So no need to create a shaded artifact anymore.</li>
+</ul>
+<p>An other advantage is that the <tt>${maven.projectBasedir}/.mvn/</tt> directory is located in the root of your Maven project and in conseuqence is part of your project which means you will check it in along with your project. So everyone who checks out your project automatically can use the extensions.</p>
+<p>One thing is important that the extensions will be resolved from the pluginRepository. This is important if you have configured the pluginRepository different from the repository.</p></div>
+<div class="section">
+<h3><a name="JVM_and_Command_Line_Options"></a>JVM and Command Line Options</h3>
+
+<ul>
+
+<li>
+<p><a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5767">Project specific jvm and command line otions</a></p></li>
+
+<li>
+<p>It’s really hard to define a general set of options for calling the maven command line. Usually this will be solved by putting this options to a script but this can now simple being done by defining <tt>${maven.projectBasedir}/.mvn/maven.config</tt> file which contains the configuration options for the command line. For example things like <tt>-T3 -U
+ --fail-at-end</tt>. So you only have to call maven just by using <tt>mvn clean
+ package</tt> instead of <tt>mvn -T3 -U --fail-at-end clean package</tt> and not to miss the <tt>-T3 -U --fail-at-end</tt> options. The <tt>${maven.projectBasedir}/.mvn/maven.config</tt> is located in the <tt>${maven.projectBasedir}/.mvn/</tt> folder which is in the root of a multi module build. This folder is part of the project and will be checked in into your version control. This results in being picked by everybody who checks out the project and no need to remember to call this project via <tt>mvn -T3 -U --fail-at-end clean package</tt> instead of <tt>mvn clean package</tt>.</p></li>
+
+<li>
+<p>In Maven it is not simple to define JVM configuration on a per project base. The existing mechanism based on an environment variable <tt>MAVEN_OPTS</tt> and the usage of <tt>${user.home}/.mavenrc</tt> is an other option with the drawback of not being part of the project.</p></li>
+
+<li>
+<p>Starting with this release you can define JVM configuration via <tt>${maven.projectBasedir}/.mvn/jvm.config</tt> file which means you can define the options for your build on a per project base. This file will become part of your project and will be checked in along with your project. So no need anymore for <tt>MAVEN_OPTS</tt>, <tt>.mavenrc</tt> files. So for example if you put the following JVM options into the <tt>${maven.projectBasedir}/.mvn/jvm.config</tt> file</p></li>
+</ul>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">-Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
+</pre></div></div>
+
+<ul>
+
+<li>you don’t need to remember of using this options in <tt>MAVEN_OPTS</tt> or switching between different configurations.</li>
+</ul></div>
+<div class="section">
+<h3><a name="Plugin_Goal_Invocation_from_Command_Line"></a>Plugin Goal Invocation from Command Line</h3>
+
+<ul>
+
+<li>Improvement for <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5768">Plugin Goal Invocation from command line</a></li>
+</ul>
+<p>If you call a plugin directly from command line like the following:</p>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">mvn exec:java
+</pre></div></div>
+<p>The configuration which is used here can be defined in your pom by using an execution id <tt>default-cli</tt>.</p>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"><project...>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>exec-maven-plugin</artifactId>
+ <version>1.3.2</version>
+ <executions>
+ <execution>
+ <id>default-cli</id>
+ <configuration>
+ <mainClass>com.soebes.test.First</mainClass>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+</project>
+</pre></div></div>
+<p>Starting with this Maven release you can now define several configuration for different executions on command like the following:</p>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums"><project...>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>exec-maven-plugin</artifactId>
+ <version>1.3.2</version>
+ <executions>
+ <execution>
+ <id>default-cli</id>
+ <configuration>
+ <mainClass>com.soebes.test.First</mainClass>
+ </configuration>
+ </execution>
+ <execution>
+ <id>second-cli</id>
+ <configuration>
+ <mainClass>com.soebes.test.Second</mainClass>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+</project>
+</pre></div></div>
+<p>So if you like to use the configuration given with the execution id: <tt>second-cli</tt> this can be done like this:</p>
+
+<div class="source">
+<div class="source"><pre class="prettyprint linenums">mvn exec:java@second-cli
+</pre></div></div>
+<p>So now you can define more than one configuration for command line executions.</p>
+
+<ul>
+
+<li>The Maven team has decided to <a class="externalLink" href="https://jira.codehaus.org/browse/MNG-5776">drop support for Win9x in launch scripts</a> at long last. Yeah.</li>
+</ul>
+<p>The above release notes have <a class="externalLink" href="http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features/">originally been written by Karl Heinz Marbaise and migrated afterwards to the Apache Maven project</a>.</p></div></div>
</div>
</div>
</div>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.