Re: [VOTE] Release Maven Surefire Plugin version 2.17

2014-03-14 Thread Kristian Rosenvold
+1 Just in time for jdk8 ga :) K 14. Mars 2014 00:44 skrev Olivier Lamy ol...@apache.org følgende: +1 Tested on few projects. Thanks! Olivier On 13 March 2014 08:52, Andreas Gudian andreas.gud...@gmail.com wrote: Hi, long ago since we released the last Surefire version. It's

Re: [VOTE] Release Apache Maven PMD Plugin version 3.1

2014-03-14 Thread Dennis Lundberg
+1 from me On Tue, Mar 11, 2014 at 9:18 PM, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140styleName=Htmlversion=19131 There are still a couple of issues left in JIRA:

Re: MRELEASE-431

2014-03-14 Thread Simone Tripodi
Hi Rob, thanks a lot for the detailed feedback, very appreciated :) I just realise I didn't pass you enough informations to better understand the new context we are working on: in the OSGi world, aside the odd-even policy, we would like to wrap BND[1] APis which allow compare two bundles and

Re: MRELEASE-431

2014-03-14 Thread Baptiste Mathus
2014-03-13 19:19 GMT+01:00 Robert Scholte rfscho...@apache.org: To say it in your own words: IMHO I think you're wrong here ;) Version policy is about calculating the next version based on an input version. These are valid examples: default policy: getReleaseVersion(1-SNAPSHOT) = 1

Re: MRELEASE-431

2014-03-14 Thread Robert Scholte
Hi Simone, I think what you want is a way to make clear what kind of release it will be: major, minor, bugfix/micro. That's something which can be added to the request and looks reasonable for all policies. I'm not sure if an enum is correct here, any founded suggestion is welcome.

Re: MRELEASE-431

2014-03-14 Thread Simone Tripodi
Hi Robert, yes I agree, while making my prototype - it will be opensourced, by the way - I also realised that my Policy implementation is the wrong Maven phase: when asking for the next release version, it is supposed that current doesn't exist yet (unless someone publishes the SNAPSHOT, even

Re: MRELEASE-431

2014-03-14 Thread Robert Scholte
Op Fri, 14 Mar 2014 10:25:59 +0100 schreef Baptiste Mathus bmat...@batmat.net: 2014-03-13 19:19 GMT+01:00 Robert Scholte rfscho...@apache.org: To say it in your own words: IMHO I think you're wrong here ;) Version policy is about calculating the next version based on an input version.

Re: maven-jar-plugin:2.4 taking 15 minutes

2014-03-14 Thread Kristian Rosenvold
Usually this means pc'er running out of entropy. Try installing randomsound K 14. Mars 2014 09:04 skrev Vishal Kumar Gupta groups...@gmail.com følgende: Hi Team, OS - Ubuntu 12.04 TLS Issue:- 1) maven version - 3.2.1 - when i run plugin maven-jar-plugin:2.4 it completes in ~15 Minutes. 2)

Re: [VOTE] Release Apache Maven PMD Plugin version 3.1

2014-03-14 Thread Robert Scholte
+1 RAT: only approved licenses 'mvn verify -Prun-its': build success SHA1: correct Site: ok Robert Op Fri, 14 Mar 2014 08:20:57 +0100 schreef Dennis Lundberg denn...@apache.org: +1 from me On Tue, Mar 11, 2014 at 9:18 PM, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 10

Re: [VOTE] Release Apache Maven PMD Plugin version 3.1

2014-03-14 Thread Hervé BOUTEMY
+1 Regards, Hervé Le mardi 11 mars 2014 21:18:10 Dennis Lundberg a écrit : Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140styleName=H tmlversion=19131 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Maven Surefire Plugin version 2.17

2014-03-14 Thread Hervé BOUTEMY
+1 Regards, Hervé Le mercredi 12 mars 2014 22:52:21 Andreas Gudian a écrit : Hi, long ago since we released the last Surefire version. It's about time we change that ;-). We solved 16 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=19 536 There are

Working on the Changes Plugin

2014-03-14 Thread Dennis Lundberg
Hi all, When releasing the Checkstyle Plugin I noticed that our setup for generating and emailing the announcement using the Changes Plugin is broken. See these issues for details: http://jira.codehaus.org/browse/MCHANGES-280 http://jira.codehaus.org/browse/MCHANGES-292

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Karl Heinz Marbaise
Hi, so based on the discussion we can conclude the result as follows: src/main * are files required during compile time (production) src/main/java src/main/resources src/main/filters src/test * are files required during test time (unit testing; based on naming

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Karl Heinz Marbaise
Hello Dennis, src/main/config is used as the default value for configuration files in appassembler-maven-plugin @Mojo. Ah damn...Just forgot about that...;-) Thanks for that hint. On Tue, Mar 11, 2014 at 9:57 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, On 3/9/14 9:02 PM, Karl

Re: [VOTE] Release Maven Surefire Plugin version 2.17

2014-03-14 Thread Karl Heinz Marbaise
+1 (non binding). Tested (maven-surefire-plugin) with several projects Maven 3.2.1 Maven 3.1.0 Maven 3.1.1 Tested (maven-failsafe-plugin) with a few projects. Maven 3.2.1 Maven 3.1.1 Tested (maven-surefire-report-plugin) with a single project. Maven 3.2.1 On 3/12/14 10:52 PM, Andreas Gudian

Re: [VOTE] Release Apache Maven PMD Plugin version 3.1

2014-03-14 Thread Karl Heinz Marbaise
Hi, +1 (non binding) Tested with Maven 3.2.1, Maven 3.1.1, Maven 3.0.5 No problem. Kind regards Karl-Heinz Marbaise On 3/11/14 9:18 PM, Dennis Lundberg wrote: Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140styleName=Htmlversion=19131 There are

[RESULT] [VOTE] Release Apache Maven PMD Plugin version 3.1

2014-03-14 Thread Dennis Lundberg
Hi, The vote has passed with the following result: +1 (binding): Dennis Lundberg, Robert Scholte, Hervé Boutemy +1 (non binding): Michael Osipov, Karl Heinz Marbaise I will promote the artifacts to the central repo. On Tue, Mar 11, 2014 at 9:18 PM, Dennis Lundberg denn...@apache.org wrote:

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Mirko Friedenhagen
Karl-Heinz, so someone should maybe file an issue in the appassembler-maven-plugin, I think the layout you provided is reasonable. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Karl Heinz Marbaise
Hi Mirko, Karl-Heinz, so someone should maybe file an issue in the appassembler-maven-plugin, I think the layout you provided is reasonable. done so. http://jira.codehaus.org/browse/MNGSITE-195 Kind regards Karl-Heinz Marbaise Regards Mirko -- http://illegalstateexception.blogspot.com/

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Karl Heinz Marbaise
Hi Mirko, so someone should maybe file an issue in the appassembler-maven-plugin, I think the layout you provided is reasonable. Why for the appassembler-maven-plugin ? It currently uses src/config ? Should appassembler-maven-plugin stop using src/config ? Hm... Kind regards Karl-Heinz

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Dennis Lundberg
Hi, Did you change from src/main/config to src/config on purpose? In this case (i.e. when using the appassembler plugin) it really should be src/main/config, because the contents of that directory will end up in the main artifact. Similar to resources which might not be required at compile time,

Re: maven-assembly-plugin / Maven default folder layout

2014-03-14 Thread Mirko Friedenhagen
Hello Karl-Heinz, I thought you said appassembler would put configs wrongly into src/main/config instead of src/config. Now it seems the stuff is included in the artifact. IMO stuff going into the artifact should be beneath src/main while configs for e.g. plugins should go to src/config (say