try deleteme/** instead.
Additionally, having an absolute path in there seems like a bad idea
unless there is a very specific reason for it!
- Brett
2008/9/17 EJ Ciramella <[EMAIL PROTECTED]>:
> I'm having an issue where if there is a parent pom and a child pom, mvn
> clean won't use it's configured directories included in the plugin
> configuration.
>
>
>
> It reports its scanning them, but opts to do nothing:
>
>
>
> <plugin>
>
> <artifactId>maven-clean-plugin</artifactId>
>
> <version>2.2</version>
>
> <configuration>
>
> <filesets>
>
> <fileset>
>
> <directory>C:\some\other\dir</directory>
>
> <includes>
>
> <include>deleteme\**</include>
>
> </includes>
>
> </fileset>
>
> </filesets>
>
> <verbose>true</verbose>
>
> </configuration>
>
> </plugin>
>
>
>
> I see this:
>
>
>
> [INFO] task-segment: [clean]
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] [clean:clean]
>
> [INFO] Deleting file-set: C:\some\other\dir (included: [deleteme\**],
> excluded: [])
>
> [INFO] Scanning for deletable directories.
>
> [INFO] Re-scanning for deletable files.
>
> [INFO] [cobertura:clean {execution: default}]
>
>
>
> But everything is still there - any suggestions?
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
