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

Github user jdillon commented on the issue: https://github.com/apache/maven/pull/116 the plexus @Requirement injection is probably why this works at all in Maven, though w/o using maven-resolver-provider in a pure guice/sisu environment, this fails and causes NPE: ```

[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 howdy, i'm fine to wait if you are gonna adjust to jsr330 that will be better generally for the project anyways IMO; i'm just trying to learn how to use the api and can live with this

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

Github user ifedorenko commented on the issue: https://github.com/apache/maven/pull/116 I have a commit on a local branch that fully converts maven-resolver-provider to jsr330, I can push that to master if you can wait few days. Either way we'll need a JIRA to track the changes.

[GitHub] maven pull request #116: Fix jsr-330 injection of DefaultArtifactDescriptorR...

GitHub user jdillon opened a pull request: https://github.com/apache/maven/pull/116 Fix jsr-330 injection of DefaultArtifactDescriptorReader ... which is not setting the VersionRangeResolver; cause NPE when use w/o plexus requirement injection You can merge this pull request into

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

Article updated to eliminate misunderstandings and talk about a different index for 'maven central' too. - ph On Sat, May 13, 2017 at 3:04 PM, Paul Hammant wrote: > I was discussing this of the list today, and it may interest people on dev@ > >

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

Hi, this is my +1 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 couple of issues left in JIRA:

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

This is quite similar to what "go get" does to golang. I'd say its worth a try On May 14, 2017 09:28, "Paul Hammant" wrote: > Article updated to eliminate misunderstandings and talk about a different > index for 'maven central' too. > > - ph > > On Sat, May 13, 2017 at 3:04

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

+1 Regards, Hervé Le jeudi 11 mai 2017, 23:30:29 CEST Karl Heinz Marbaise a écrit : > Hi, > > We solved 13 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227 > rsion=12338874 > > There are still a couple of issues left in JIRA: >

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

I don't understand what changed in Maven 3.1.0-alpha-1 that changed the behaviour: did you find which issue was fixed? Adding a pointer to that issue as comment (and not only in git commit message) would be useful before merging so that this change is understood when reading the code thanks

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

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 in Maven core? Does it improve Maven or not? To me, changing default plugin

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

Am 2017-05-14 um 09:33 schrieb Hervé BOUTEMY: I don't understand what changed in Maven 3.1.0-alpha-1 that changed the behaviour: did you find which issue was fixed? Unfortunately not. Issue titles weren't helpful, commit messages also. I assume this is an Aether update. Adding a pointer to