Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Tue, 10 Aug 2004 3:50 AM
Hi, I am marking this as incomplete as the first part has been added for the
integration tests. The second part I am not convinced is a good idea. If, for some
reason, I add a jar twice to my POM, I expect that should show up everywhere as an
error, versus masking it with a Set.. It seems that maven maybe in some sort of
pom:validate goal should flag it as an error.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-13
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-13
Summary: Two hacks to the eclipse plug-in in .classpath generation (see comments
for details)
Type: Improvement
Status: Closed
Priority: Major
Resolution: INCOMPLETE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Fix Fors:
1.8
Assignee:
Reporter: Diego Fernandez
Created: Wed, 16 Apr 2003 3:00 PM
Updated: Tue, 10 Aug 2004 3:50 AM
Description:
The attached file contains two hacks to the generation of the classpath in the
eclipse:generate-classpath plug-in:
1. Added the source directory for the integration unit tests.
(TODO: add cactus JARs to the classpath)
2. Add JARs only once (using a Set), this is useful when you have a junit in the
dependencies (or may be in the future when you have the cactus libs)
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
