By default clean plugin just deletes target. So excluding something inside is unlikely to work well.
If I were you, I'd install and use a small software for Windows called unlocker. If your build fails cleaning, try to "unlock" target directory. You should see what is using the directory and you'll almost be done. It could be something both simple and nasty like the search indexer of windows... Been there myself... HTH Cheers Le 5 août 2011 16:30, "javafan2011" <[email protected]> a écrit : > yes I am working on windows machine, but i didnt run even unit test inside > this project. As someone else is working on this project. Also my project is > dependent on this module but even in my unit test I am not referring to > claases from this project, so how come it will keep the handle in windows > file system. I was reading about maven-clean-plugin and saw the > "<excludeDefaultDirectories>true</excludeDefaultDirectories>" option not > sure it is a good idea to use this option to ignore as in future i might > need to compile the project > > > > -- > View this message in context: http://maven.40175.n5.nabble.com/Maven-build-issue-tp4669414p4669689.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
