Re: [VOTE] Release Apache Maven Plugin Tools version 3.4, take 2

Hi, sha1 checked...Ok. checked with Maven 3.2.5, 3.1.1, 3.0.5, 2.2.1 via mvn -Prun-its clean verify without any issue... So +1 from me... Kind regards Karl Heinz Marbaise On 1/1/15 11:07 PM, Hervé BOUTEMY wrote: Hi, We solved 15 issues:

Re: OT: Xpp3 parser

Hi Jason, Jason van Zyl wrote: We do, it's been in plexus-utils for years in the org.codehaus.plexus.util.xml.pull package. Hmm. You took a private copy of the API (normally in xmlpull:xmlpull) and of xpp3:xpp3. However, since the Plexus parser no longer implements the official API

[GitHub] maven pull request: Improved visibility of collections and variabl...

Github user Tibor17 commented on the pull request: https://github.com/apache/maven/pull/34#issuecomment-68554366 @hboutemy @jvanzyl Any objections to push this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] maven-plugins pull request: Add flag to collect MANIFEST sections.

Github user asfgit closed the pull request at: https://github.com/apache/maven-plugins/pull/18 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: [GitHub] maven pull request: Improved visibility of collections and variabl...

On 2 January 2015 at 22:27, Tibor17 g...@git.apache.org wrote: Github user Tibor17 commented on the pull request: https://github.com/apache/maven/pull/34#issuecomment-68568625 The link should be in README.md. Look at README file @ JUnit and JavaHamcrest projects, where the most

[GitHub] maven pull request: Improved visibility of collections and variabl...

Github user jvanzyl commented on the pull request: https://github.com/apache/maven/pull/34#issuecomment-68555131 As a check did you run the ITs? There are a few collections that are expected to be mutable unfortunately. I haven't looked at the patch in detail to check but I can look

[GitHub] maven pull request: Improved visibility of collections and variabl...

Github user Tibor17 commented on the pull request: https://github.com/apache/maven/pull/34#issuecomment-68561294 @jvanzyl My ant build says BUILD SUCCESS. I saw your TODO comments moreless related to immutable objects. Currently the code is not ready for immutable objects

[GitHub] maven pull request: Improved visibility of collections and variabl...

Github user Tibor17 commented on the pull request: https://github.com/apache/maven/pull/34#issuecomment-68568625 The link should be in README.md. Look at README file @ JUnit and JavaHamcrest projects, where the most important is build status @ CloudBees and Travis

[GitHub] maven pull request: Improved visibility of collections and variabl...

Github user jvanzyl commented on the pull request: https://github.com/apache/maven/pull/34#issuecomment-68562504 Ant build? The ITs are in a separate repository. This may be helpful: http://takari.io/2014/06/01/contributing-to-maven-core.html There are are 700+

Re: [GitHub] maven pull request: Improved visibility of collections and variabl...

Hey Stephen, I have discarded my CloudBees account because they wanted my bank card # to pay. The free accounts do not seem to be free any longer. I wanted to have Surefire on CloudBees, but now won't be possible, and I really don't need top fast machines in Maven projects. -- View this message

[GitHub] maven-enforcer pull request: [MENFORCER-170|

Github user khmarbaise closed the pull request at: https://github.com/apache/maven-enforcer/pull/8 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] maven-enforcer pull request: [MENFORCER-169]

Github user khmarbaise closed the pull request at: https://github.com/apache/maven-enforcer/pull/7 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] maven-enforcer pull request: [MENFORCER-171]

Github user khmarbaise closed the pull request at: https://github.com/apache/maven-enforcer/pull/9 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: Releases, Continuous Delivery and the Future

Well, I for one find the x.y.z-nn somehow unusual. I'd prefer something simple like x.y.z and I don't give a f*ck if some numbers are skipped. +1 with Stephen: I've never seen someone complain about missing versions neither on ML nor IRL. Sure, I suppose people might wonder where the 4.x went if

Re: svn commit: r1649120 - in /maven/enforcer/trunk: enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/ enforcer-rules/src/test/java/org/apache/maven/plugins/enforcer/ enforcer-rules/src/

Hi Karl-Heinz, we don't know if there are other projects who use the EnforcerExpressionEvaluator. Changing the constructor signature might break code. Could you add a new constructor instead? thanks, Robert Op Fri, 02 Jan 2015 22:01:18 +0100 schreef khmarba...@apache.org: Author:

Re: [GitHub] maven pull request: Improved visibility of collections and variabl...

On Friday, January 2, 2015, Tibor Digana tibordig...@apache.org wrote: Hey Stephen, I have discarded my CloudBees account because they wanted my bank card # to pay. The free accounts do not seem to be free any longer. Oss accounts are still free, but not for 1-2 developer hobby projects...