You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Johns (JIRA)" <ji...@codehaus.org> on 2008/04/21 21:59:55 UTC
[jira] Created: (MECLIPSE-439) Support filesets for clean goal
Support filesets for clean goal
-------------------------------
Key: MECLIPSE-439
URL: http://jira.codehaus.org/browse/MECLIPSE-439
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Affects Versions: 2.5.1
Reporter: Michael Johns
It would be great if filesets with includes/excludes were supported for the clean goal. We have a situation where we have to commit our .settings directory due to the presence of some items that are not generated by the plugin, and the clean plugin simply deletes that whole directory. I'm envisioning something like the maven-clean-plugin, which lets us control exactly what we want to clean.
I realize that the plugin can generate custom configuration via the <additionalConfig> tag, which would allow us to regenerate the cleaned file, but if the additional config files are large, the XML in pom.xml can get unwieldy very fast. It would be easier to just commit the file and tell the plugin to not clean it.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-439) Support filesets for clean goal
Posted by "Michael Johns (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131625#action_131625 ]
Michael Johns commented on MECLIPSE-439:
----------------------------------------
I just dug into the source a little more, and I realized the plugin is smart enough to not delete custom files that I put in .settings. I saw it wiping out the entire directory earlier, and I figured it would just take my file with it, but it didn't. So that's good.
But even with this new understanding of how it works, I actually stand by my original improvement request. I still think it would be nice to have a finer control over just what gets cleaned.
> Support filesets for clean goal
> -------------------------------
>
> Key: MECLIPSE-439
> URL: http://jira.codehaus.org/browse/MECLIPSE-439
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Affects Versions: 2.5.1
> Reporter: Michael Johns
>
> It would be great if filesets with includes/excludes were supported for the clean goal. We have a situation where we have to commit our .settings directory due to the presence of some items that are not generated by the plugin, and the clean plugin simply deletes that whole directory. I'm envisioning something like the maven-clean-plugin, which lets us control exactly what we want to clean.
> I realize that the plugin can generate custom configuration via the <additionalConfig> tag, which would allow us to regenerate the cleaned file, but if the additional config files are large, the XML in pom.xml can get unwieldy very fast. It would be easier to just commit the file and tell the plugin to not clean it.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira