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 actually using refer to files / folders in the trunk, not fixed versions. Example: ^/trunk/projectA/fileA fileA Therefore, when you check out a tagged release created with m-release-p somewhere in the future, the checked out files could be different compared to the time the release was created. To prevent this, I'm actually manually changing the svn:externals definition in the tagged release to reference fixed versions of the desired files/folders after m-release-p is finished: -r ^/trunk/projectA/fileA fileA Is there a way to automate this? According to the release notes of Subversion 1.9, there's a new option "--pin-externals" available for "svn copy". Is it possible to use that? If yes, how can I do this? I've also found this plugin here: https://github.com/MartinMReed/maven-svn-plugin What do you think? Regards Thorsten
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 we want to hold onto test results Is there any way to disable the automatic detection of project.build.directory, etc, and only delete custom filesets? Or is there another plugin/goal which would let me do this? I can write a mojo if I need to, but was hoping something was already out there. Thanks, Ben
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: org.apache.maven.plugins maven-clean-plugin default-cli ... second-cli ... now you can use: mvn clean:clean@default-cli mvn clean:clean@second-cli Kind regards Karl Heinz Marbaise On 12/17/15 7:36 PM, Ben Podgursky wrote: 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 we want to hold onto test results Is there any way to disable the automatic detection of project.build.directory, etc, and only delete custom filesets? Or is there another plugin/goal which would let me do this? I can write a mojo if I need to, but was hoping something was already out there. Thanks, Ben - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
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 `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: > > > > > > org.apache.maven.plugins > maven-clean-plugin > > > default-cli > > ... > > > > second-cli > > ... > > > > > > > > > now you can use: > > mvn clean:clean@default-cli > mvn clean:clean@second-cli > > Kind regards > Karl Heinz Marbaise > > > > On 12/17/15 7:36 PM, Ben Podgursky wrote: > >> 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 we want to hold onto test >> results >> >> Is there any way to disable the automatic detection of >> project.build.directory, etc, and only delete custom filesets? Or is >> there >> another plugin/goal which would let me do this? >> >> I can write a mojo if I need to, but was hoping something was already out >> there. >> >> >> Thanks, >> >> Ben >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
[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. http://maven.apache.org/plugins/maven-pmd-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-pmd-plugin 3.6 Release Notes - Apache Maven PMD Plugin - Version 3.6 Bug * [MPMD-218] Update to PMD 5.3.5 * [MPMD-217] False positive UselessParentheses * [MPMD-215] FieldDeclarationsShouldBeAtStartOfClass false positive * [MPMD-186] Class names with slash are omitted from exclusions on pmd:check Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
