[
https://issues.apache.org/jira/browse/MCLEAN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958673#comment-17958673
]
Olivier Lamy commented on MCLEAN-27:
------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-clean-plugin#208|https://github.com/apache/maven-clean-plugin/issues/208].
> fileset directory does not work as expected when cleaning "modules" in
> sub-directories
> --------------------------------------------------------------------------------------
>
> Key: MCLEAN-27
> URL: https://issues.apache.org/jira/browse/MCLEAN-27
> Project: Maven Clean Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.1.1
> Reporter: Jacob Robertson
> Assignee: Siveton Vincent
> Priority: Major
> Fix For: 2.2
>
>
> Following the example given on the plugin site, I used a fileset with a
> directory like so.
> {code}
> <plugin>
> <artifactId>maven-clean-plugin</artifactId>
> <configuration>
> <filesets>
> <fileset>
> <directory>
> src/main/application
> </directory>
> <includes>
> <include>*.jar</include>
> </includes>
> </fileset>
> </filesets>
> </configuration>
> </plugin>
> {code}
> I did this, or a variation on it, to several projects. I then created a
> parent pom in the directory above those projects, added them as modules in
> that pom, and ran "mvn clean" expecting to have those specified directories
> cleaned for me (of all jar files). However, it did not work. To get it to
> work, I had to prefix my directories with ${basedir}, for example
> "${basedir}/src/main/application".
> If this is the desired behavior, I recommend adding one sentence to the
> documentation to explain this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
