Re: [DISCUSSION] finishing Aether import: help find a new name

On Thursday 28 July 2016, Jason van Zyl wrote: > What the external name is can be whatever people feel is most suitable. > > We should jump into IRC, as I think that will be faster, to figure out how > it should be used. > > I’m a vehement -1 to changing the artifactIds or

Re: Why MavenProject is not an Artifact?

Hi Paul, i think you will like this link[1] where I tried to compare elements which have a GAV. I had to write this down when working on the maven-artifact-transfer component. I know how the Model is generated, so I kind of understand why the interface is missing. As you can see, all these

Why MavenProject is not an Artifact?

It seems that the Artifact interface could be mostly applied to MavenProject. I eyeball about 70% of the methods could apply. If this seems unreasonable, I think an interface could be refactored out from both of them supporting just these: String getGroupId(); String getArtifactId();

[GitHub] maven issue #88: [MNG-5910] Fixed the description of the POM reference & add...

Github user rajivpjs commented on the issue: https://github.com/apache/maven/pull/88 I know that you are busy. Could you please let me know whether there are any more changes to be done? Thanks. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] maven pull request #89: [MNG-5995] Removed maven-compat as it not required a...

Github user rajivpjs closed the pull request at: https://github.com/apache/maven/pull/89 --- 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 is

Model version (was: Re: [DISCUSSION] finishing Aether import: help find a new name)

Am 28.07.2016 um 19:18 schrieb Jason van Zyl: I’m a vehement -1 to changing the artifactIds or structure without a plan. +1 If something does not need to be renamed, then don't rename it. If something needs to be renamed, don't choose some kind of trademarkish name no-one knows what it

Re: Apache Commons BCEL 6.0 is out and clirr-maven-plugin

Thank you Olivier. Any plans for a release? Gary On Thu, Jul 28, 2016 at 12:04 AM, Olivier Lamy wrote: > all done. > > > Thanks > Olivier > > On 26 July 2016 at 23:44, Gary Gregory wrote: > > > Hi All: > > > > There seems to be some overlap in

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 2016-07-28 um 18:24 schrieb Christian Schulte: Am 07/28/16 um 18:21 schrieb Christian Schulte: Am 07/28/16 um 17:37 schrieb Andreas Sewe: Jason van Zyl wrote: It’s all Maven specific, it’s always been Maven specific and that’s unlikely to change after how many years? Even if it can employ

Re: [DISCUSSION] finishing Aether import: help find a new name

What the external name is can be whatever people feel is most suitable. We should jump into IRC, as I think that will be faster, to figure out how it should be used. I’m a vehement -1 to changing the artifactIds or structure without a plan. We have to change the groupId because we cannot

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 07/28/16 um 18:21 schrieb Christian Schulte: > Am 07/28/16 um 17:37 schrieb Andreas Sewe: >> Jason van Zyl wrote: >>> It’s all Maven specific, it’s always been Maven specific and that’s >>> unlikely to change after how many years? Even if it can employ >>> different strategies it’s still the

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 07/28/16 um 17:37 schrieb Andreas Sewe: > Jason van Zyl wrote: >> It’s all Maven specific, it’s always been Maven specific and that’s >> unlikely to change after how many years? Even if it can employ >> different strategies it’s still the Maven Artifact Resolution API. No >> one is going to use

Re: [DISCUSSION] finishing Aether import: help find a new name

Jason van Zyl wrote: > It’s all Maven specific, it’s always been Maven specific and that’s > unlikely to change after how many years? Even if it can employ > different strategies it’s still the Maven Artifact Resolution API. No > one is going to use this API to resolve from NuGet, NPMJS, PyPi or >

Re: [DISCUSSION] finishing Aether import: help find a new name

> On Jul 28, 2016, at 10:07 AM, Anders Hammar wrote: > > This might be a language thing. "Maven Artifact Resolver API" makes me > think this is only for resolving Maven artifacts, but my understanding is > that p2 artifacts is also supported by Tycho. Am I wrong? You are

Re: Build failed in Jenkins: core-it-maven-3-win #1233

Can someone take a look, please? Error: JAVA_HOME is set to an invalid directory. JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64" Please set the JAVA_HOME variable in your environment to match the location of your Java installation. Am 07/28/16 um 17:27 schrieb Apache Jenkins Server: > See

Re: [DISCUSSION] finishing Aether import: help find a new name

> > Tycho does not use Aether to resolve p2 artifacts. > I'll shut up then. :-) /Anders > > -- > Regards, > Igor > > On Thu, Jul 28, 2016, at 10:07 AM, Anders Hammar wrote: > > This might be a language thing. "Maven Artifact Resolver API" makes me > > think this is only for resolving Maven

Re: [DISCUSSION] finishing Aether import: help find a new name

Tycho does not use Aether to resolve p2 artifacts. -- Regards, Igor On Thu, Jul 28, 2016, at 10:07 AM, Anders Hammar wrote: > This might be a language thing. "Maven Artifact Resolver API" makes me > think this is only for resolving Maven artifacts, but my understanding is > that p2 artifacts is

Re: [DISCUSSION] finishing Aether import: help find a new name

This might be a language thing. "Maven Artifact Resolver API" makes me think this is only for resolving Maven artifacts, but my understanding is that p2 artifacts is also supported by Tycho. Am I wrong? Removing "Maven" and just call it Artifact Resolver API (ara) solves this. It's the API for

Re: [DISCUSSION] finishing Aether import: help find a new name

It’s all Maven specific, it’s always been Maven specific and that’s unlikely to change after how many years? Even if it can employ different strategies it’s still the Maven Artifact Resolution API. No one is going to use this API to resolve from NuGet, NPMJS, PyPi or anything else. Let’s just

Re: [DISCUSSION] finishing Aether import: help find a new name

Are we making the non-Maven-specific Aether library/code Maven-specific during this move? If not, then I don't think we should have the Maven part in the name. /Anders On Thu, Jul 28, 2016 at 10:40 AM, Michael Osipov wrote: > I fully agree with you Stephen! > > > Am

Re: [DISCUSSION] finishing Aether import: help find a new name

I fully agree with you Stephen! Am 2016-07-28 um 10:35 schrieb Stephen Connolly: I don't see that this needs a special name, so I am -1 on Akasha I like Maven Artifact Resolver API... but my only concern with the "mara" short form is that I'll keep replaying radio satire in my head every time

Re: [DISCUSSION] finishing Aether import: help find a new name

On 28 July 2016 at 09:35, Stephen Connolly wrote: > -1 on Akasha actually that should be -0. on Akasha... i.e. I am not vetoing the name, just really don't like it

Re: [DISCUSSION] finishing Aether import: help find a new name

I don't see that this needs a special name, so I am -1 on Akasha I like Maven Artifact Resolver API... but my only concern with the "mara" short form is that I'll keep replaying radio satire in my head every time I say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA What exactly is wrong

[DISCUSSION] finishing Aether import: help find a new name

Hi, The work on Aether import is progressing: as I commented on MNG-6007 recently, we now have to find a new name for the component at Apache. Then we'll update poms, documentation and git repo accordingly and we'll be ready to make releases. We already have first ideas, found by the PMC

Re: Apache Commons BCEL 6.0 is out and clirr-maven-plugin

all done. Thanks Olivier On 26 July 2016 at 23:44, Gary Gregory wrote: > Hi All: > > There seems to be some overlap in community between clirr-maven-plugin > Maven devs. > > Any thoughts on getting Clirr to use BCEL 6.0 a la: > >