The following issue has been updated: Updater: thierry lach (mailto:[EMAIL PROTECTED]) Date: Wed, 5 May 2004 4:53 PM Comment: Alternate patch. Changes: Attachment changed to classpath.jelly.patch --------------------------------------------------------------------- For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10&page=history --------------------------------------------------------------------- View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-10 Here is an overview of the issue: --------------------------------------------------------------------- Key: MPECLIPSE-10 Summary: added eclipseDependency='false' behavior Type: Improvement Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-eclipse-plugin Assignee: Reporter: Piotr Maj Created: Fri, 22 Aug 2003 6:43 AM Updated: Wed, 5 May 2004 4:53 PM 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]