maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MECLIPSE-439) Support filesets for clean goal
Date Sun, 06 Sep 2015 20:46:24 GMT

     [ https://issues.apache.org/jira/browse/MECLIPSE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MECLIPSE-439.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> Support filesets for clean goal
> -------------------------------
>
>                 Key: MECLIPSE-439
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-439
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message