The following comment has been added to this issue:
Author: dion gillard
Created: Sun, 24 Aug 2003 9:15 PM
Body:
I'd much rather we used the isClasspath dependency method on Dependency.
So I'm -1 to the patch.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-712
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-712
Summary: added eclipseDependency='false' behavior
Type: Improvement
Status: Unassigned
Priority: Minor
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin-eclipse
Fix Fors:
1.1
Versions:
1.0-beta-10
Assignee:
Reporter: Piotr Maj
Created: Fri, 22 Aug 2003 6:43 AM
Updated: Fri, 22 Aug 2003 6:43 AM
Environment: any
Description:
While generating .classpath file maven-eclipse-plugin includes all artifacts defined
in project.xml regardless of it's type. As a side effect it may be observed that even
JSP's *.tld files are included as Eclipse variables.It leads to project compile
problems. Actually such project won't compile at all.
To avoid such behavior I propose a silly patch attached, which takes care of
eclipseDependency property of artifacts. If it is set to 'false' the artifact will not
be listed in .classpath.
---------------------------------------------------------------------
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]
