From ebfc785ce3e0727774a1c219736cd7e0a460da92 Mon Sep 17 00:00:00 2001 From: fgiust Date: Sat, 3 Dec 2005 13:50:50 +0000 Subject: [PATCH] [maven-scm-plugin] prepare release 1.10 git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@351945 13f79535-47bb-0310-9956-ffa450edef68 --- eclipse/xdocs/changes.xml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/eclipse/xdocs/changes.xml b/eclipse/xdocs/changes.xml index 3b90cc74..67455fb9 100644 --- a/eclipse/xdocs/changes.xml +++ b/eclipse/xdocs/changes.xml @@ -1,4 +1,4 @@ - + - Changes dIon Gillard - + Moved test classpath before main so test classpath resources override main ones eclipse:add-maven-repo doesn't update correct Eclipse property file for Eclipse 3.x - add-maven-repo fails if Eclipse hasn't been started yet. Property file needs to be created - by the plugin. - + add-maven-repo fails if Eclipse hasn't been started yet. Property file needs to be created by the plugin. Only create .classpath and javabuilder if sources are present Don't add duplicate java natures/builders if already specified using - maven.eclipse.projectnatures and maven.eclipse.buildcommands + maven.eclipse.projectnaturesand + maven.eclipse.buildcommands Only add javanature if sources are present Generates a .wtpmodules file for eclipse webtools (wtp 0.7 required) classpathentry contains trailing pipe character that confuses Eclipse 3.1 Java source location now defaults to - MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar (standard location where source artifacts are deployed by the m2 source plugin in - a legacy/m1 repository layout). The path ${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension} is still supported for backward compatibility - and it will be used only if a file already exists at that location. + MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar(standard location where source artifacts are deployed by the m2 source plugin in a legacy/m1 repository layout). The path + ${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension}is still supported for backward compatibility and it will be used only if a file already exists at that location. Setting relative path value to "maven.eclipse.output.dir" generates wrong absolute classpath entry Failing use cases for projects with just resources - Added eclipse:eclipse alias for the eclipse goal (match the maven 2 goal name) + Added + eclipse:eclipsealias for the + eclipsegoal (match the maven 2 goal name) + maven.eclipse.conclasspath is ignored when junit test src is not present