The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 24 Mar 2004 10:36 PM
Body:
The excludes of <sourceModification> are only processed if the class isn't found. The
previous jelly snippet doesn't check the class is available
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-14&page=comments#action_17885
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPECLIPSE-14
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-14
Summary: Add the ability to exclude source
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: 1 week
Time Spent: Unknown
Remaining: 1 week
Project: maven-eclipse-plugin
Assignee:
Reporter: dion gillard
Created: Mon, 2 Jun 2003 7:49 PM
Updated: Wed, 24 Mar 2004 10:36 PM
Description:
>From "Doug Patterson" <[EMAIL PROTECTED]>
The Eclipse plugin creates a .classpath file with tags like:
<classpathentry kind="src" path="src/java">
Eclipse also supports an excluding attribute that filters out any files
matching the supplied pattern. I tweaked plugin.jelly (patch below) to check
for a maven.eclipse.exclude property in project.properties and modify
kind="src" entries accordingly. For example:
maven.eclipse.exclude=**/.svn/* # Stop Eclipse complaining about Subversion files
---------------------------------------------------------------------
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]
