Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-882 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVEN-882 Summary: Eclipse plugin includes non-classpath dependencies in generated files Type: Bug Status: Unassigned Priority: Minor Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-eclipse Fix Fors: 1.1 Versions: 1.0-beta-10 1.0-rc1 Assignee: Reporter: dion gillard Created: Thu, 2 Oct 2003 7:57 PM Updated: Thu, 2 Oct 2003 7:57 PM Description: I am using the eclipse plugin for a project in which project.xml lists a dependency on a <type>tld</type> artifact. maven eclipse then generates a dependency on MAVEN_REPO/path/file.tld Arguable this has no value, but Eclipse also does not like it, producing "Unbound classpath variable" messages. Manually removing these guys in Eclipse solves the problem, but of course each execute of maven eclipse reintroduces the problem. It seems that one can add a <eclipse.depency> property to each dependency to cause special behavior. I think a solution would be to either: - Introduce a new property <eclipse.exclude>, or - Make the eclipse plug-in aware of the supported artifact types and only include artifacts of type: jar, war, sar etc. but not tld --------------------------------------------------------------------- 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]
