MPECLIPSE-10 Fix for ignoring dependencies via <eclipse.dependency>false</eclipse.dependency>

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@115586 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
epugh 2004-06-28 22:07:32 +00:00
parent 63cc493cd1
commit 79c13ed882
3 changed files with 8 additions and 0 deletions

View File

@ -124,6 +124,9 @@
<j:when test="${eclipseDependency == 'true'}">
<classpathentry kind="src" path="/${lib.dependency.artifactId}"/>
</j:when>
<j:when test="${eclipseDependency == 'false'}">
<!-- ignore specific dependencies -->
</j:when>
<j:when test="${lib.dependency.groupId == 'junit'}">
<!-- ignoring junit dependency as we've already created it -->
</j:when>

View File

@ -25,6 +25,7 @@
</properties>
<body>
<release version="1.8" date="In CVS">
<action dev="epugh" type="add" issue="MPECLIPSE-10" due-to="Thierry Lack">Set eclipse.dependency=false to explicity ignore dependencies in classpath generation</action>
<action dev="evenisse" type="fix" issue="MPECLIPSE-29" due-to="Marc-Antoine Garrigue">Fix classpath generation when tests are not present</action>
<action dev="evenisse" type="fix" issue="MPECLIPSE-32">classpath includes must be relative directories</action>
</release>

View File

@ -127,6 +127,10 @@
This indicates that the dependency is another project in the workspace.
Note that the name of the referenced project is the artifactId.
</p>
<p>
The inverse also works. If you have included extra jars that shouldn't be
in the eclipse classpath then you can set <code>eclipse.dependency=false</code>
</p>
</section>
</body>
</document>