Re: Silly Saturday idea - If Maven Central were a bunch of Git repos

Interesting idea! All for experimenting with git! You did not take into account the protocol differences, fetching a single 8MB jar from Maven Central is easy, while fetching 6 MB via multiple git HTTP resources (even assuming git packs there will be multiple http calls) is probably more

Re: Several MRESOLVER issues

+1 for the 3 issues: good enhancements without risks Regards, Hervé Le dimanche 14 mai 2017, 00:33:18 CEST Michael Osipov a écrit : > Folks, > > who seconds the following issues for Maven Resolver 1.1: > > MRESOLVER-4: Use java.util.Objects#requireNonNull to intercept null input >

Re: [MNG-6169] Lifecycle/binding plugin version updates

On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote: > thank you Robert: this is exactly the logic I was looking for, and > explanation > of changes over time to improve user experience through reproducibility. > > Now the question is: should we change default plugin versions

Re: Silly Saturday idea - If Maven Central were a bunch of Git repos

There's one repo per thing that is versioned. All these are separate repos g: com/thoughtworks/paranamer a: paranamer type: javadoc is one repo g: com/thoughtworks/paranamer a: paranamer type: sources is one repo g: com/thoughtworks/paranamer a: paranamer type: classes is one repo

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.1

Am 2017-05-11 um 23:30 schrieb Karl Heinz Marbaise: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12338874 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.1

Hi, I need at least one more PMC vote.. (of course other VOTE's are appriciated).. Kind regards Karl Heinz Marbaise On 11/05/17 23:30, Karl Heinz Marbaise wrote: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12338874 There are still a

Re: [MNG-6169] Lifecycle/binding plugin version updates

Am 2017-05-15 um 09:20 schrieb Stephen Connolly: On Sun 14 May 2017 at 08:51, Hervé BOUTEMY wrote: thank you Robert: this is exactly the logic I was looking for, and explanation of changes over time to improve user experience through reproducibility. Now the question

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user michael-o commented on the issue: https://github.com/apache/maven/pull/116 @ifedorenko That's the only way w/o INFRA: commit message "This closes #xy". You cannot manually close via website. That's what I was trying to say. --- If your project is set up for it, you can

Upgrading maven-release-plugin to maven-scm-api 1.9.5 ?

Hi, Jgit provider exposes password if it contains special characters : SCM-817 (https://issues.apache.org/jira/browse/SCM-817) was fixed in maven-scm-api 1.9.5 which was released in July 1st, 2016. maven-scm-api 1.9.6 has even been released since

Re: Open Maven resolvers issue and release 1.1.0

IIRC 8, 9 and 10 change the current behavior of Maven a lot. I think we should transform the use cases first to ITs based on mock-repository-manager, which should make it a lot easier to understand what's happening. Next we need to decide what to change: code or documentation. thanks,

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user michael-o commented on the issue: https://github.com/apache/maven/pull/116 @jdillon Such a change is not suitable for a patch version in my opinion. Please file a JIRA issue for your local branch and push a branch for that. --- If your project is set up for it, you can

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user ifedorenko commented on the issue: https://github.com/apache/maven/pull/116 Opened https://issues.apache.org/jira/browse/MNG-6233. If you any concerns or suggestions, I suggest we continue the discussion there. @jdillon I can't close this pull request --- If

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user ifedorenko commented on the issue: https://github.com/apache/maven/pull/116 Wow. That's backwards. I wonder what will happen if I push my change with github's magic "fixes 116" pseudo comment. Guess there is one way to find out :-) --- If your project is set up for it,

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user jdillon commented on the issue: https://github.com/apache/maven/pull/116 @ifedorenko can close this if you like, wasn't sure what you mean about "a JIRA either way". If we close this and go with your changes (which if you have that mostly done for merge soon is what I

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user michael-o commented on the issue: https://github.com/apache/maven/pull/116 @ifedorenko Closing PRs requires a ticket with INFRA on JIRA. --- 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

[GitHub] maven issue #116: Fix jsr-330 injection of DefaultArtifactDescriptorReader

Github user jdillon commented on the issue: https://github.com/apache/maven/pull/116 @ifedorenko ftr I can close this, so but i'm confused about @michael-o comment that your change (I think that is what he meant) wasn't suitable for a patch release. --- If your project is set up

[MNG-6130] Loss of profile information in workaround for MNG-4900

Who seconds 6130 for 3.5.1? This is a one-line fix and all ITs pass. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [MNG-6130] Loss of profile information in workaround for MNG-4900

I think I miss a unittest or integration-test, just to be sure. On Mon, 15 May 2017 21:55:38 +0200, Michael Osipov wrote: Who seconds 6130 for 3.5.1? This is a one-line fix and all ITs pass. Michael

Re: [MNG-6130] Loss of profile information in workaround for MNG-4900

Am 2017-05-15 um 22:10 schrieb Robert Scholte: I think I miss a unittest or integration-test, just to be sure. The reporter says: "It's very tricky and hopefully not necessary, since the 1-line fix is provided" But you are right. This needs some verification. On Mon, 15 May 2017 21:55:38

Re: The maven-archetype-plugin paradox

Sorry guys, but as a maven-archetype-plugin user I don't share your views on this subject. Of course, I totally agree with the aim of this new 3.x release and the idea to be compliant with Maven3 behaviour and in particular the security features. However, there have been quite a lot of

Re: Silly Saturday idea - If Maven Central were a bunch of Git repos

One more repo: https://github.com/paul-hammant/mc-xs-all/ One branch for each of classes, javadoc, sources, and poms 15 javadoc original versions: 24.1M 16 sources original versions: 4.9M 27 classes original versions: 8.4M Afterwards git work the bare .git folder is: 8.4M *77.5% saving on

[GitHub] maven issue #115: Change out JAVA_HOME. Add JRE used. JRE used print /jre an...

Github user marcelosv commented on the issue: https://github.com/apache/maven/pull/115 OK, i go change and correct --- 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

[GitHub] maven issue #115: Change out JAVA_HOME. Add JRE used. JRE used print /jre an...

Github user eis commented on the issue: https://github.com/apache/maven/pull/115 Unfortunately it's not only line ending issue - you've changed the formatting on those files as well, so ignoring line endings (`?w=1`) the diff is still huge. It seems you've reformatted the entire

[GitHub] maven pull request #117: [MNG-5756] Java home output in mvn -v is misleading

GitHub user eis opened a pull request: https://github.com/apache/maven/pull/117 [MNG-5756] Java home output in mvn -v is misleading Renamed previous printing of JRE to "JRE used" and provided separate mechanism to actually tell value of JAVA_HOME You can merge this pull request

[GitHub] maven issue #115: Change out JAVA_HOME. Add JRE used. JRE used print /jre an...

Github user marcelosv commented on the issue: https://github.com/apache/maven/pull/115 ok. correct the code. :D --- 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

Open Maven resolvers issue and release 1.1.0

Hi folks, what to do with the remaining issues (pre-reset? Here is the list: MRESOLVER-3 Update dependencies MRESOLVER-8 ScopeDependencySelector incorrectly de-selects direct dependencies MRESOLVER-9 DefaultDependencyCollector does not correctly handle dependency management MRESOLVER-10 New