Re: [VOTE] Maven Pmd Plugin 3.0 (take 2)

+1 Regards, Hervé Le jeudi 7 février 2013 11:00:44 Olivier Lamy a écrit : > Hi, > I'd like to release Maven Pmd Plugin 3.0. > Note this version is based on PMD 5.0.2 (reason for the version bump). > We fixed 18 issues: > https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pr

Re: [VOTE] Maven Pmd Plugin 3.0 (take 2)

I agree. doc page added in trunk and site redeployed http://maven.apache.org/plugins-archives/maven-pmd-plugin-3.0/examples/violation-exclusions.html As it's only a documentation page we usually don't retag/redeploy/etc.. a release for that. 2013/2/8 Mirko Friedenhagen : > Hello Olivier, > > I wit

maven-plugins pull request: MPIR-271: GIT support in project-info-reports:s...

GitHub user mfriedenhagen opened a pull request: https://github.com/apache/maven-plugins/pull/5 MPIR-271: GIT support in project-info-reports:scm A better description for GIT, I include a patch against https://svn.apache.org/repos/asf/maven/plugins/trunk@1442445. I tested the outco

Re: [VOTE] Maven Pmd Plugin 3.0 (take 2)

Hello Olivier, I withdraw my +1, as I think the documentation should be improved, so I would give it a +0.5 :-) (non-bindingly). While projects worked without modifications, I now wanted to give the new functionality of "MPMD-161: PMD/CPD violation exclusions by class/issue" [1] a try, but strugg

maven-plugins pull request: [MCOMPILER-178] add List parameter compilerArgs

GitHub user jsievers opened a pull request: https://github.com/apache/maven-plugins/pull/4 [MCOMPILER-178] add List parameter compilerArgs Add List parameter compilerArgs which only uses values of configuration XML elements. Deprecate Map parameter compilerArguments because

RE: [VOTE] Maven Pmd Plugin 3.0 (take 2)

+1 (non-binding) tested locally on a large multi module project. New violations introduced (presumably as the PMD default config has moved on). Not checked the report syntax is still the same (aka works in Jenkins) > -Original Message- > From: Mirko Friedenhagen [mailto:mfriedenha...@gma

Re: EOL of 1.5 as minimum

+1 There is no reason to have *NEW* development of Maven be hampered by obsolete technology. If anyone can't upgrade their Java runtime for whatever reason, they probably won't upgrade to a new Maven version as well. 3.0.4 works rather well and anyone should really be tying down their plugin versi

Re: Fast or exact ?

Hi guys, do you have figures regarding size and execution time? slower/bigger doesn't speak that much to help to choose a default config ;) *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/*