Re: [VOTE] Release Apache Maven Shared Utils version 3.1.0

+0 I have a failing unittest, but it seems this one already failed with 3.0.1 as well. And it is well known that symbolic link support and Windows doesn't go very well together. Robert Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! - in org.apache.

Re: [jira] [Updated] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

Am 07/23/16 um 20:31 schrieb Karl Heinz Marbaise: > Hi Christian, > > Ok first activation problem looks like being solved I've retested this > with my example project...Thanks for fixing that... > > > But what is unclear to me why during the run information from another > profile in particular

Re: [jira] [Updated] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

Am 07/23/16 um 20:31 schrieb Karl Heinz Marbaise: > Hi Christian, > > Ok first activation problem looks like being solved I've retested this > with my example project...Thanks for fixing that... > > > But what is unclear to me why during the run information from another > profile in particular

Re: [jira] [Updated] (MNG-6070) Default profile in settings.xml must not use an id possibly already in use.

Hi Christian, Ok first activation problem looks like being solved I've retested this with my example project...Thanks for fixing that... But what is unclear to me why during the run information from another profile in particular the one which is defined in the parent of my echo-maven-plugin

Re: Deprecation of ArtifactFactory and its use in new code

Hi Robert,   Thanks for the info, I wasn't aware of this wiki page.   I pushed a fix of MDEPLOY-212 and MDEPLOY-213 using this idea in a forked repository of maven-plugins here https://github.com/Tunaki/maven-plugins/. All the IT still pass (expect from MDEPLOY-181 that is expected to fail) b

Re: [VOTE] Release Apache Maven Shared Utils version 3.1.0

here is my +1 Regards, Hervé Le mercredi 20 juillet 2016 23:40:03 Hervé BOUTEMY a écrit : > Hi, > > We solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&ve > rsion=12335944&styleName=Text > > Staging repo: > https://repository.apache.org/content/repos

[GitHub] maven pull request #88: [MNG-5910] Fixed the description of the POM referenc...

Github user khmarbaise commented on a diff in the pull request: https://github.com/apache/maven/pull/88#discussion_r71971452 --- Diff: maven-model-builder/src/test/resources/poms/factory/complexEmptyAndMissing.xml --- @@ -31,21 +31,5 @@ activated-1

Re: Building Apache Maven

Hi Rajiv, I have taken another look into your updated pull request... We usually don't use asterik imports...and furthermore you don't follow the code style guide we have: http://maven.apache.org/developers/conventions/code.html If you runn a full build of what you have changed checkstyle sh

[GitHub] maven issue #89: [MNG-5995] Removed maven-compat as it not required anymore ...

Github user khmarbaise commented on the issue: https://github.com/apache/maven/pull/89 I meant that you should try to compile an example project with the created Maven Core version? I don't meant you should build Maven core itself... --- If your project is set up for it, you can rep

Mentor Request

Hi My name is Rajiv and I am interested in working with the development of Apache Maven. I have recently started making contributions though Pull requests and would like to contribute to Apache Maven. I believe Apache Maven is in active development. I saw the Mentoring Programme on the Apache