[MCLEAN-27] fileset directory does not work as expected when cleaning "modules" in sub-directories

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.1
• Fix Version/s: 2.2
• Assignee: Siveton Vincent
• Reporter: Jacob Robertson
• Created: 20/Sep/07 14:11
• Updated: 02/Sep/08 14:31
• Resolved: 14/Nov/07 07:29

Description

Following the example given on the plugin site, I used a fileset with a directory like so.

<plugin>
	<artifactId>maven-clean-plugin</artifactId>
	<configuration>
		<filesets>
			<fileset>
				<directory>
					src/main/application
				</directory>
				<includes>
					<include>*.jar</include>
				</includes>
			</fileset>
		</filesets>
	</configuration>
</plugin>

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.

Issue Links

• is related to: MCLEAN-36 filesets with an absolute path directory are ignored when !project.isExecutionRoot()
• relates to: MCLEAN-31 Always resolve relative path against the project's base directory