[RESULT] [VOTE] Release Apache Maven Shared Component: Maven Dependency Analyzer Version 1.6

Hi, The vote has passed with the following result: +1 (binding): Jason van Zyl, Karl Heinz Marbaise, Hervé Boutemy +1 (non binding): Anders Hammar I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise

[RESULT] [VOTE] Release Apache Maven Shared Component: Maven JarSigner Version 1.4

Hi, The vote has passed with the following result: +1 (binding): Benson Margulies, Hervé Boutemy, Karl Heinz Marbaise +1 (non binding): none I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise

Re: Releasing the dependency plugin?

Well, you're doing a good job so...;-) /Anders On Wed, Jan 21, 2015 at 10:02 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, So maven-dependency-analyzer is released... Should i start with Maven Dependency Plugin or would someone else take the chance ;-)... Kind regards Karl

[ANN] Apache Maven Shared Component: Maven JarSigner Version 1.4 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven JarSigner Version 1.4 This component provides some utilities to sign/verify jars/files in your Mojos. http://maven.apache.org/shared/maven-jarsigner/ You should specify the version in your

[ANN] Apache Maven Shared Component: Maven Dependency Analzyer Version 1.6 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Dependency Analyzer Version 1.6 Analyzes the dependencies of a project for undeclared or unused artifacts. http://maven.apache.org/shared/maven-dependency-analyzer/ You should specify the

[VOTE] Release Apache Maven JarSigner Plugin version 1.4

Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11990version=19865 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=XXXstatus=1 Staging repo:

[VOTE] Release Apache Maven JarSigner Plugin version 1.4

Hi, We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11990version=19865 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=XXXstatus=1 Staging repo:

Re: Releasing the dependency plugin?

Hi, So maven-dependency-analyzer is released... Should i start with Maven Dependency Plugin or would someone else take the chance ;-)... Kind regards Karl Heinz Marbaise On 1/18/15 3:04 PM, Karl Heinz Marbaise wrote: Hi, On 1/18/15 2:42 PM, Anders Hammar wrote: MDEP-466 [1] is the

[VOTE] Release Apache Maven Dependency Plugin version 2.10

Hi, We solved 9 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214version=20646 There are still a couple of issues left in JIRA: https://jira.codehaus.org/issues/?jql=project%20%3D%20MDEP%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging

Re: Releasing the dependency plugin?

Hi Anders, On 1/21/15 10:05 PM, Anders Hammar wrote: Well, you're doing a good job so...;-) Ok Ok...I'll take it ;-)... Karl Heinz /Anders On Wed, Jan 21, 2015 at 10:02 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote: Hi, So maven-dependency-analyzer is released... Should i start with

[GitHub] maven-surefire pull request: SUREFIRE-1136 Current working directo...

GitHub user norbertwnuk opened a pull request: https://github.com/apache/maven-surefire/pull/82 SUREFIRE-1136 Current working directory propagation in forked mode remove JDK 1.7 API usages in tests, integration test extended to justify deferred directory creation in

[GitHub] maven pull request: [MNG-5686] Use /usr/libexec/java_home to find ...

GitHub user ecki opened a pull request: https://github.com/apache/maven/pull/35 [MNG-5686] Use /usr/libexec/java_home to find JAVA_HOME This fixes the /usr/libexec/java_home choser (OSX) for the main script and adds the missing section to the other tows (ASF Commiter Signoff: ecki)

Re: Surefire Plugin does not handle workingDirectory in fork mode properly

Pull request with the fix - https://github.com/apache/maven-surefire/pull/82 NW On Wed, Jan 21, 2015 at 9:27 PM, Tibor Digana tibordig...@apache.org wrote: This is a traditional problem with animal-sniffer-maven-plugin. We had the same issue in JUnit project. Alrerady reported in JIRA

Re: problem with AAR dependency

On Jan 20, 2015, at 6:03 PM, William Ferguson william.fergu...@xandar.com.au wrote: Been thinking about this a little more. The TLDR version: I am suggesting that we provide more information and place a stricter syntax requirement of the POM *generated* by the build. This allows the

Re: Releasing the Checkstyle Plugin

Le mercredi 21 janvier 2015 14:44:27 Dennis Lundberg a écrit : There is some piece of code in Checkstyle 5.9 that uses Java 6+ classes/methods. I don't remember where, but it isn't covered by our integration tests. since our ITs use the 3 integrated rulesets, I suppose this is in a rule that

Re: Maven Dev Hangout Topics

Can anyone talk about the meta datas inside the repository? Such as, who is responsible(repository manager or specific plugins) to generate which? Which plugin will use what meta data resouces? How? etc. Thanks Guo Yingshou On Wed, Jan 21, 2015 at 11:14 PM, Jason van Zyl ja...@takari.io wrote:

Re: problem with AAR dependency

Well, at the moment it's the Android SDK team, but in the future it could be anybody. I look at the deployed POMs are as form of contract between the deployed artifact and it's consumers. So when the contract isn't explicit (eg dependency type info) then its open to misinterpretation. Maven

Re: Releasing the Checkstyle Plugin

On Thu, Jan 22, 2015 at 5:29 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Le mercredi 21 janvier 2015 14:44:27 Dennis Lundberg a écrit : There is some piece of code in Checkstyle 5.9 that uses Java 6+ classes/methods. I don't remember where, but it isn't covered by our integration tests.

Re: Surefire Plugin does not handle workingDirectory in fork mode properly

This is a traditional problem with animal-sniffer-maven-plugin. We had the same issue in JUnit project. Alrerady reported in JIRA http://jira.codehaus.org/browse/MANIMALSNIFFER-54 http://jira.codehaus.org/browse/MANIMALSNIFFER-40 I would like to have the check-test goal or a new parameter. It's

Re: Releasing the Checkstyle Plugin

Le vendredi 9 janvier 2015 13:29:06 Dennis Lundberg a écrit : I've started going through the open issues and have found a problem that I need som help with. It turns out that Checkstyle 5.9 uses Java 6 classes, even though it is not mentioned in the release notes. How do we want to handle

Re: Releasing the Checkstyle Plugin

There is some piece of code in Checkstyle 5.9 that uses Java 6+ classes/methods. I don't remember where, but it isn't covered by our integration tests. I'll have a look at it tomorrow evening, and see if I can produce an IT that catches it. Another thing that I have been thinking about is whether

Re: Releasing the Checkstyle Plugin

I'm confused. The current version of checkstyle is 6.2. Why is this discussion about 5.9? Should we make a branch that requires java whatever and is actually current? On Wed, Jan 21, 2015 at 8:44 AM, Dennis Lundberg denn...@apache.org wrote: There is some piece of code in Checkstyle 5.9 that

Re: Releasing the Checkstyle Plugin

Benson, please have a look at the road map in JIRA. The talk about Checkstyle 5.9 regards the 2.14 release that we have been preparing for during the last couple of weeks. On Wed, Jan 21, 2015 at 2:52 PM, Benson Margulies bimargul...@gmail.com wrote: I'm confused. The current version of

Maven Dev Hangout Topics

Anyone have anything they want me to throw on the list. So far we have: - Henning and the Basepom project - Igor talking about how to develop Maven plugins in M2E - Jason talking about better configuration for Maven plugins Thanks, Jason