The following comment has been added to this issue:
Author: David Eric Pugh
Created: Wed, 2 Mar 2005 12:57 PM
Body:
I think the idea of eclipse.dependency is to filter out completely those
dependencies.. The options are true/false, and default to true. So, if the
eclipse.dependency is skipped, that is the same as true.
It is possible we need to have something more like:
eclipse.dependencyType that specifies what something is...
Eric
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-59?page=comments#action_30417
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-59
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-59
Summary: Skipped dependency with eclipse.dependency false
Type: Bug
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Assignee:
Reporter: Henri Bonnehuit
Created: Mon, 29 Nov 2004 8:00 AM
Updated: Wed, 2 Mar 2005 12:57 PM
Environment: Java 1.4.2_04, win2k
Description:
A dependency element like:
<eclipse.dependency>true</eclipse.dependency>
in project.xml causes maven eclipse to skip the dependency completely,
rather than reverting to simple .classpath entry.
I have maven-eclipse-plugin-1.9.jar and maven v. 1.0.1
---------------------------------------------------------------------
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]
