Author: brett
Date: Fri Mar 20 13:38:47 2009
New Revision: 756460
URL: http://svn.apache.org/viewvc?rev=756460&view=rev
Log:
add a note about MNG-4056
Modified:
maven/site/trunk/src/site/apt/release-notes-preview.apt.vm
Modified: maven/site/trunk/src/site/apt/release-notes-preview.apt.vm
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/release-notes-preview.apt.vm?rev=756460&r1=756459&r2=756460&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/release-notes-preview.apt.vm (original)
+++ maven/site/trunk/src/site/apt/release-notes-preview.apt.vm Fri Mar 20
13:38:47 2009
@@ -56,6 +56,8 @@
* MNG-3475 - neither the script source directory nor the reporting output
directory were aligned to the base directory. While this was a bug, if you used
an expression such as <<<$\{basedir\}/$\{project.reporting.outputDirectory\}>>>
then where this would of worked in Maven 2.0.10, it will have two copies of the
project base directory in Maven 2.1.0+. You should remove the leading
<<<$\{basedir\}>>> from the expression - however note that in some cases this
will cause the build to be incompatible with earlier versions of Maven.
+ * MNG-4056 - Dependencies specified with a classifier of <<<sources>>> and
type of <<<jar>>> are correctly considered source JARs and no longer added to
the classpath. This is
{{{http://code.google.com/p/gwt-maven/issues/detail?id=200} known to affect the
GWT plugin}}
+
** Noteworthy Changes and improvements
* MNG-3760 - <<<$\{project.baseUri\}>>> has been added as a valid
expression in the POM, and is a valid URI equivalent of <<<$\{basedir\}>>>