Re: Hijack mvn clean:clean to do file cleanup?

Hi Ben, you can define an execution with the id `default-cli` where you can configure the special filesSet for your purpose ...which you can execute from command line only via clean:clean... If you are in Maven 3.3.X+ you define several of them like this:

Hijack mvn clean:clean to do file cleanup?

We have a problem where our build servers fill up with jar artifacts post-build (we have a lot of java builds). I was hoping to attach an execution of clean:clean with a custom after the deploy phase. However, I don't want to sweep the whole target/ directory, just the filesets I define, since

Re: Hijack mvn clean:clean to do file cleanup?

So actually I'm just terrible at reading documentation there's a excludeDefaultDirectories parameter which does exactly what I want. So, disregard all. On Thu, Dec 17, 2015 at 10:41 AM, Karl Heinz Marbaise wrote: > Hi Ben, > > you can define an execution with the id

[ANN] Apache Maven PMD Plugin 3.6 Released

The Maven team is pleased to announce the release of the Apache Maven PMD Plugin, version 3.6 A Maven plugin for the PMD toolkit, that produces a report on both code rule violations and detected copy and paste fragments, as well as being able to fail the build based on these metrics.

Best practices: m-release-p and svn:externals

Hi, I have a few Maven projects that use svn:externals to link to code and/or resources stored in different paths in our Subversion repository. Compiling, packaging, deploying etc, works fine; even creating releases with m-release-p (release:prepare && release:perform). The svn:externals I'm