You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Hervé BOUTEMY <he...@free.fr> on 2016/07/28 07:13:16 UTC
[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 while working in private on the
topic:
- Akasha https://en.wikipedia.org/wiki/Akasha
- Maven Artifact Resolver API ("mara" when used as package name or artifactid
or in maven-mara-provider)
Does anybody have another idea?
Is there a preference in the community?
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Stephen Connolly <st...@gmail.com>.
On 28 July 2016 at 09:35, Stephen Connolly <st...@gmail.com>
wrote:
> -1 on Akasha
actually that should be -0.9999 on Akasha... i.e. I am not vetoing the
name, just really don't like it
Re: Model version (was: Re: [DISCUSSION] finishing Aether import: help find a new name)
Posted by Jason van Zyl <ja...@takari.io>.
So I think really what you want vis-a-vis artifact resolution is a way to have a new repository system session with new/altered implementations for fixes or new behavior. Possibly a new repository system as well. If the default behavior continues to work, anyone can do whatever radical things they might like to experiment with provided the user knowingly flips the switch to enable the non-default behavior. Currently there is a DefaultRepositorySytemSessionFactory and we might want to allow picking a new one of those so that new managers, selectors, and transformers can be used. Maybe we modify this slightly if we want a new a new collector or resolver. This is orthogonal to the model changes that may or may not be made.
How do we enable this? I think a bunch of CLI switch is cumbersome, so maybe we officially introduce feature toggles in the settings. Useful for us and if teams want to run with certain features it will be easier to share this configuration. If we’re going to employ feature toggles then I think the settings is likely the place to do it. If so I can probably make a prototype in a few hours. From settings session properties can be made that reach most of code from end to end. But this allows branching by abstraction and all behavior can live in master. We can see all the implementations in one place and users won’t have to go build special branches to try things out, it will just be in the standard snapshots and the releases. If the features are off by default it won’t surprise any existing users.
As for shoring up all the behaviour there are still 2-3 places where scopes are mutatate outside the scope of the existing Aether code which makes things fairly confusing. As I’m sure people people look at the final state and wonder how it happened because if they trace through Aether code everyone who does seems it didn’t happen there. That aspect is a mess. This should be consistent for plugins and the application resolution but it currently is not.
> On Jul 29, 2016, at 8:50 PM, Jason van Zyl <ja...@takari.io> wrote:
>
> The model version doesn’t necessarily have anything to do with resolution or any behavioral changes per se. I also don’t think a branch is necessary and we do branching by abstraction and figure out the feature toggles now and just keep it all in master.
>
>> On Jul 28, 2016, at 2:11 PM, Christian Schulte <cs...@schulte.it> wrote:
>>
>> 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 stands for but something self-describing as much as possible.
>>
>>> We have to change the groupId because we cannot deploy into Eclipse’s namespace but for anyone using this code just leave it how it is while making improvements.
>>
>> +1
>>
>>> The library as it stands functions and people are using it. We have something in Maven core that uses it and it’s pretty terrible but it’s a great place to start trying to flesh out something new because the ITs will catch most things.
>>
>> We have recently discussed the addition of some kind of feature toggles/switches/knobs and haven't come to a conclusion yet. I would like to make the following proposal:
>>
>> Rename the branch 'maven-3.x-next' to 'maven-next'. Use the model version to decide about how Maven should behave when it comes to a change in behaviour between a previous model version and the next model version. Update the model version right now to the next model version on that 'maven-next' branch so things can get going there (setup Jenkins and things like that e.g.) All I need to know for this is what is the model version we will be using in that 'maven-next' branch today. Is it a minor version increment (4.1) or a major one (5.0). The reason I would like to use the model version instead of some kind of feature toggle is to be able to deploy to central or somewhere else. So that Maven can detect how to behave also for POMs it downloads from the repositories instead of relying on some command line option.
>>
>> Regards,
>> --
>> Christian
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Model version (was: Re: [DISCUSSION] finishing Aether import: help find a new name)
Posted by Jason van Zyl <ja...@takari.io>.
The model version doesn’t necessarily have anything to do with resolution or any behavioral changes per se. I also don’t think a branch is necessary and we do branching by abstraction and figure out the feature toggles now and just keep it all in master.
> On Jul 28, 2016, at 2:11 PM, Christian Schulte <cs...@schulte.it> wrote:
>
> 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 stands for but something self-describing as much as possible.
>
>> We have to change the groupId because we cannot deploy into Eclipse’s namespace but for anyone using this code just leave it how it is while making improvements.
>
> +1
>
>> The library as it stands functions and people are using it. We have something in Maven core that uses it and it’s pretty terrible but it’s a great place to start trying to flesh out something new because the ITs will catch most things.
>
> We have recently discussed the addition of some kind of feature toggles/switches/knobs and haven't come to a conclusion yet. I would like to make the following proposal:
>
> Rename the branch 'maven-3.x-next' to 'maven-next'. Use the model version to decide about how Maven should behave when it comes to a change in behaviour between a previous model version and the next model version. Update the model version right now to the next model version on that 'maven-next' branch so things can get going there (setup Jenkins and things like that e.g.) All I need to know for this is what is the model version we will be using in that 'maven-next' branch today. Is it a minor version increment (4.1) or a major one (5.0). The reason I would like to use the model version instead of some kind of feature toggle is to be able to deploy to central or somewhere else. So that Maven can detect how to behave also for POMs it downloads from the repositories instead of relying on some command line option.
>
> Regards,
> --
> Christian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Model version (was: Re: [DISCUSSION] finishing Aether import: help
find a new name)
Posted by Christian Schulte <cs...@schulte.it>.
Am 28.07.2016 um 19:18 schrieb Jason van Zyl:
> I\u2019m 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 stands for but something self-describing as
much as possible.
> We have to change the groupId because we cannot deploy into Eclipse\u2019s namespace but for anyone using this code just leave it how it is while making improvements.
+1
> The library as it stands functions and people are using it. We have something in Maven core that uses it and it\u2019s pretty terrible but it\u2019s a great place to start trying to flesh out something new because the ITs will catch most things.
We have recently discussed the addition of some kind of feature
toggles/switches/knobs and haven't come to a conclusion yet. I would
like to make the following proposal:
Rename the branch 'maven-3.x-next' to 'maven-next'. Use the model
version to decide about how Maven should behave when it comes to a
change in behaviour between a previous model version and the next model
version. Update the model version right now to the next model version on
that 'maven-next' branch so things can get going there (setup Jenkins
and things like that e.g.) All I need to know for this is what is the
model version we will be using in that 'maven-next' branch today. Is it
a minor version increment (4.1) or a major one (5.0). The reason I would
like to use the model version instead of some kind of feature toggle is
to be able to deploy to central or somewhere else. So that Maven can
detect how to behave also for POMs it downloads from the repositories
instead of relying on some command line option.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Stephen Connolly <st...@gmail.com>.
On Thursday 28 July 2016, Jason van Zyl <ja...@takari.io> 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 structure without a plan.
> We have to change the groupId because we cannot deploy into Eclipse’s
> namespace but for anyone using this code just leave it how it is while
> making improvements.
> As I understand it, they said that they were OK with giving us a temporary
derogation to use the eclipse namespace as long as we made clear that this
was not precedent setting and we were working in good faith to move off and
the first indication of that good faith would be to change the name (even
if we cannot change the other things just yet)
As such I think we could actually deploy relocation poms in the eclipse
groupId as a migration pathway...
>
>
Consider it just moving the body of code from Eclipse because that’s all it
> is right now. If we’re going to make changes to the API in a new package
> space then just delegate to the Aether code, like we are doing in the core
> right now and maybe even working from the core if possible. Shore up and
> fix the usage in the core, we have artifact related code all over the place
> doing duplicate things that we should consolidate too. Swizzling the Aether
> code around and changing it all is not going to help anything at all.
> Fixing bugs, great. Making additions that leave the library compatible yet
> improve it, great. If it works in the core and works in the plugins it will
> work for everyone else.
>
> The library as it stands functions and people are using it. We have
> something in Maven core that uses it and it’s pretty terrible but it’s a
> great place to start trying to flesh out something new because the ITs will
> catch most things. There is also the questions of what kind of testing
> harness we need because everyone is sort of looking at how these changes
> affect the outcome but I think tools that perform deltas on the dirty tree
> and final list with their scope transformations should be considered before
> starting to fiddle with any existing Aether code.
>
> For now leave the Aether code in as close a state that from which it
> arrived here from Eclipse. No one has touched this stuff for years, I can’t
> see how anyone would think changing it all is a good idea because it’s not.
> At any rate, a discussion is in order before any change to it’s structure
> it made.
>
> > On Jul 28, 2016, at 12:24 PM, Christian Schulte <cs@schulte.it
> <javascript:;>> wrote:
> >
> > 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 Maven Artifact Resolution API. No
> >>>> one is going to use this API to resolve from NuGet, NPMJS, PyPi or
> >>>> anything else. Let’s just make it better for our specific use cases
> >>>> instead of imagining this is going to be a general purpose tool. It
> >>>> is clear that this never happened and probably never will.
> >>>
> >>> I think the confusion stems from the fact that there is both Maven (the
> >>> tool) and the Maven repository format (the combination of directory
> >>> structure, maven-metadata.xml, checksums files, etc.).
> >>>
> >>> The API we are talking about is for the Maven repository format and not
> >>> some other repository format (like p2, NuGet, ...). It may be used by
> >>> Maven *and* other tools (like Gradle, sbt, ...). In that sense, it is
> >>> *not* specific to the Maven tool, but it is specific to the Maven
> >>> repository format. Hence, calling it something with Maven in the name
> >>> makes sense to me.
> >>
> >> +1
> >>
> >>> FWIW, we (the Eclipse Code Recommenders project) have been using (first
> >>> Sonatype, then Eclipse) Aether since ~2010 to download recommendation
> >>> models stored in a repository which does follow the Maven repository
> >>> format, but which does not store your typical artifacts (JARs with
> >>> pom.xml). If that use case is still supported by the new API, I really
> >>> don't care how the API is called. ;-)
> >>
> >> +1
> >>
> >> It's an abstraction to access Maven(-format) repositories in a
> >> consistent way. Project name could be "Maven Repositories" and the
> >> artifacts could be
> >>
> >> maven-repositories-api
> >> maven-repositories-impl
> >> maven-repositories-utilities
> >> etc.
> >>
> >> No need to add "API" to the project name. It's more than that. In the
> >> end, it's just a name. We should avoid what was done in the past and try
> >> to use a self-describing name. We had to tell people what "Aether"
> >> stands for every now and then. This should be avoided.
> >>
> >> Regards,
> >>
> >
> > Group-Id: org.apache.maven.shared.repositories
> > Artifact-Id: maven-repositories-api, maven-repositories-impl, etc.
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> > For additional commands, e-mail: dev-help@maven.apache.org
> <javascript:;>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>
--
Sent from my phone
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
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 deploy into Eclipse’s namespace but for anyone using this code just leave it how it is while making improvements. Consider it just moving the body of code from Eclipse because that’s all it is right now. If we’re going to make changes to the API in a new package space then just delegate to the Aether code, like we are doing in the core right now and maybe even working from the core if possible. Shore up and fix the usage in the core, we have artifact related code all over the place doing duplicate things that we should consolidate too. Swizzling the Aether code around and changing it all is not going to help anything at all. Fixing bugs, great. Making additions that leave the library compatible yet improve it, great. If it works in the core and works in the plugins it will work for everyone else.
The library as it stands functions and people are using it. We have something in Maven core that uses it and it’s pretty terrible but it’s a great place to start trying to flesh out something new because the ITs will catch most things. There is also the questions of what kind of testing harness we need because everyone is sort of looking at how these changes affect the outcome but I think tools that perform deltas on the dirty tree and final list with their scope transformations should be considered before starting to fiddle with any existing Aether code.
For now leave the Aether code in as close a state that from which it arrived here from Eclipse. No one has touched this stuff for years, I can’t see how anyone would think changing it all is a good idea because it’s not. At any rate, a discussion is in order before any change to it’s structure it made.
> On Jul 28, 2016, at 12:24 PM, Christian Schulte <cs...@schulte.it> wrote:
>
> 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 Maven Artifact Resolution API. No
>>>> one is going to use this API to resolve from NuGet, NPMJS, PyPi or
>>>> anything else. Let’s just make it better for our specific use cases
>>>> instead of imagining this is going to be a general purpose tool. It
>>>> is clear that this never happened and probably never will.
>>>
>>> I think the confusion stems from the fact that there is both Maven (the
>>> tool) and the Maven repository format (the combination of directory
>>> structure, maven-metadata.xml, checksums files, etc.).
>>>
>>> The API we are talking about is for the Maven repository format and not
>>> some other repository format (like p2, NuGet, ...). It may be used by
>>> Maven *and* other tools (like Gradle, sbt, ...). In that sense, it is
>>> *not* specific to the Maven tool, but it is specific to the Maven
>>> repository format. Hence, calling it something with Maven in the name
>>> makes sense to me.
>>
>> +1
>>
>>> FWIW, we (the Eclipse Code Recommenders project) have been using (first
>>> Sonatype, then Eclipse) Aether since ~2010 to download recommendation
>>> models stored in a repository which does follow the Maven repository
>>> format, but which does not store your typical artifacts (JARs with
>>> pom.xml). If that use case is still supported by the new API, I really
>>> don't care how the API is called. ;-)
>>
>> +1
>>
>> It's an abstraction to access Maven(-format) repositories in a
>> consistent way. Project name could be "Maven Repositories" and the
>> artifacts could be
>>
>> maven-repositories-api
>> maven-repositories-impl
>> maven-repositories-utilities
>> etc.
>>
>> No need to add "API" to the project name. It's more than that. In the
>> end, it's just a name. We should avoid what was done in the past and try
>> to use a self-describing name. We had to tell people what "Aether"
>> stands for every now and then. This should be avoided.
>>
>> Regards,
>>
>
> Group-Id: org.apache.maven.shared.repositories
> Artifact-Id: maven-repositories-api, maven-repositories-impl, etc.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Michael Osipov <mi...@apache.org>.
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
>>>> 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 make it better for our specific use cases
>>>> instead of imagining this is going to be a general purpose tool. It
>>>> is clear that this never happened and probably never will.
>>>
>>> I think the confusion stems from the fact that there is both Maven (the
>>> tool) and the Maven repository format (the combination of directory
>>> structure, maven-metadata.xml, checksums files, etc.).
>>>
>>> The API we are talking about is for the Maven repository format and not
>>> some other repository format (like p2, NuGet, ...). It may be used by
>>> Maven *and* other tools (like Gradle, sbt, ...). In that sense, it is
>>> *not* specific to the Maven tool, but it is specific to the Maven
>>> repository format. Hence, calling it something with Maven in the name
>>> makes sense to me.
>>
>> +1
>>
>>> FWIW, we (the Eclipse Code Recommenders project) have been using (first
>>> Sonatype, then Eclipse) Aether since ~2010 to download recommendation
>>> models stored in a repository which does follow the Maven repository
>>> format, but which does not store your typical artifacts (JARs with
>>> pom.xml). If that use case is still supported by the new API, I really
>>> don't care how the API is called. ;-)
>>
>> +1
>>
>> It's an abstraction to access Maven(-format) repositories in a
>> consistent way. Project name could be "Maven Repositories" and the
>> artifacts could be
>>
>> maven-repositories-api
>> maven-repositories-impl
>> maven-repositories-utilities
>> etc.
>>
>> No need to add "API" to the project name. It's more than that. In the
>> end, it's just a name. We should avoid what was done in the past and try
>> to use a self-describing name. We had to tell people what "Aether"
>> stands for every now and then. This should be avoided.
>>
>> Regards,
>>
>
> Group-Id: org.apache.maven.shared.repositories
> Artifact-Id: maven-repositories-api, maven-repositories-impl, etc.
I do even think that the 'shared' is not necessary, since this is going
to be a standalone component with several artifacts. It deserves to be
Maven Repositories and MREPOSITORIES in JIRA.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
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\u2019s all Maven specific, it\u2019s always been Maven specific and that\u2019s
>>> unlikely to change after how many years? Even if it can employ
>>> different strategies it\u2019s still the Maven Artifact Resolution API. No
>>> one is going to use this API to resolve from NuGet, NPMJS, PyPi or
>>> anything else. Let\u2019s just make it better for our specific use cases
>>> instead of imagining this is going to be a general purpose tool. It
>>> is clear that this never happened and probably never will.
>>
>> I think the confusion stems from the fact that there is both Maven (the
>> tool) and the Maven repository format (the combination of directory
>> structure, maven-metadata.xml, checksums files, etc.).
>>
>> The API we are talking about is for the Maven repository format and not
>> some other repository format (like p2, NuGet, ...). It may be used by
>> Maven *and* other tools (like Gradle, sbt, ...). In that sense, it is
>> *not* specific to the Maven tool, but it is specific to the Maven
>> repository format. Hence, calling it something with Maven in the name
>> makes sense to me.
>
> +1
>
>> FWIW, we (the Eclipse Code Recommenders project) have been using (first
>> Sonatype, then Eclipse) Aether since ~2010 to download recommendation
>> models stored in a repository which does follow the Maven repository
>> format, but which does not store your typical artifacts (JARs with
>> pom.xml). If that use case is still supported by the new API, I really
>> don't care how the API is called. ;-)
>
> +1
>
> It's an abstraction to access Maven(-format) repositories in a
> consistent way. Project name could be "Maven Repositories" and the
> artifacts could be
>
> maven-repositories-api
> maven-repositories-impl
> maven-repositories-utilities
> etc.
>
> No need to add "API" to the project name. It's more than that. In the
> end, it's just a name. We should avoid what was done in the past and try
> to use a self-describing name. We had to tell people what "Aether"
> stands for every now and then. This should be avoided.
>
> Regards,
>
Group-Id: org.apache.maven.shared.repositories
Artifact-Id: maven-repositories-api, maven-repositories-impl, etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 07/28/16 um 17:37 schrieb Andreas Sewe:
> Jason van Zyl wrote:
>> It\u2019s all Maven specific, it\u2019s always been Maven specific and that\u2019s
>> unlikely to change after how many years? Even if it can employ
>> different strategies it\u2019s still the Maven Artifact Resolution API. No
>> one is going to use this API to resolve from NuGet, NPMJS, PyPi or
>> anything else. Let\u2019s just make it better for our specific use cases
>> instead of imagining this is going to be a general purpose tool. It
>> is clear that this never happened and probably never will.
>
> I think the confusion stems from the fact that there is both Maven (the
> tool) and the Maven repository format (the combination of directory
> structure, maven-metadata.xml, checksums files, etc.).
>
> The API we are talking about is for the Maven repository format and not
> some other repository format (like p2, NuGet, ...). It may be used by
> Maven *and* other tools (like Gradle, sbt, ...). In that sense, it is
> *not* specific to the Maven tool, but it is specific to the Maven
> repository format. Hence, calling it something with Maven in the name
> makes sense to me.
+1
> FWIW, we (the Eclipse Code Recommenders project) have been using (first
> Sonatype, then Eclipse) Aether since ~2010 to download recommendation
> models stored in a repository which does follow the Maven repository
> format, but which does not store your typical artifacts (JARs with
> pom.xml). If that use case is still supported by the new API, I really
> don't care how the API is called. ;-)
+1
It's an abstraction to access Maven(-format) repositories in a
consistent way. Project name could be "Maven Repositories" and the
artifacts could be
maven-repositories-api
maven-repositories-impl
maven-repositories-utilities
etc.
No need to add "API" to the project name. It's more than that. In the
end, it's just a name. We should avoid what was done in the past and try
to use a self-describing name. We had to tell people what "Aether"
stands for every now and then. This should be avoided.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Andreas Sewe <se...@st.informatik.tu-darmstadt.de>.
Jason van Zyl wrote:
> It\u2019s all Maven specific, it\u2019s always been Maven specific and that\u2019s
> unlikely to change after how many years? Even if it can employ
> different strategies it\u2019s still the Maven Artifact Resolution API. No
> one is going to use this API to resolve from NuGet, NPMJS, PyPi or
> anything else. Let\u2019s just make it better for our specific use cases
> instead of imagining this is going to be a general purpose tool. It
> is clear that this never happened and probably never will.
I think the confusion stems from the fact that there is both Maven (the
tool) and the Maven repository format (the combination of directory
structure, maven-metadata.xml, checksums files, etc.).
The API we are talking about is for the Maven repository format and not
some other repository format (like p2, NuGet, ...). It may be used by
Maven *and* other tools (like Gradle, sbt, ...). In that sense, it is
*not* specific to the Maven tool, but it is specific to the Maven
repository format. Hence, calling it something with Maven in the name
makes sense to me.
FWIW, we (the Eclipse Code Recommenders project) have been using (first
Sonatype, then Eclipse) Aether since ~2010 to download recommendation
models stored in a repository which does follow the Maven repository
format, but which does not store your typical artifacts (JARs with
pom.xml). If that use case is still supported by the new API, I really
don't care how the API is called. ;-)
Best wishes,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Anders Hammar <an...@hammar.net>.
>
> 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 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 resolving artifacts in Maven.
> > But, it might just be me interpreting this wrong.
> >
> > /Anders
> >
> > On Thu, Jul 28, 2016 at 3:47 PM, Jason van Zyl <ja...@takari.io> 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 anything else. Let’s
> > > just make it better for our specific use cases instead of imagining
> this is
> > > going to be a general purpose tool. It is clear that this never
> happened
> > > and probably never will. Does it matter?
> > >
> > > > On Jul 28, 2016, at 6:12 AM, Anders Hammar <an...@hammar.net>
> wrote:
> > > >
> > > > 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 <
> michaelo@apache.org>
> > > > wrote:
> > > >
> > > >> 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
> > > >>> I
> > > >>> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
> > > >>>
> > > >>> What exactly is wrong with org.apache.maven.ara or
> > > >>> org.apache.maven.artifact.resolver.api if we compare with
> > > >>> org.apache.maven.mara to me the m in mara is redundant because we
> > > already
> > > >>> have the maven... so either if we want a short package name then
> `ara`
> > > is
> > > >>> better... or we want an understandable package name... same goes
> for
> > > >>> artifactIds
> > > >>>
> > > >>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr>
> wrote:
> > > >>>
> > > >>> 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 while working in
> > > private on
> > > >>>> the
> > > >>>> topic:
> > > >>>> - Akasha https://en.wikipedia.org/wiki/Akasha
> > > >>>> - Maven Artifact Resolver API ("mara" when used as package name or
> > > >>>> artifactid
> > > >>>> or in maven-mara-provider)
> > > >>>>
> > > >>>>
> > > >>>> Does anybody have another idea?
> > > >>>> Is there a preference in the community?
> > > >>>>
> > > >>>> Regards,
> > > >>>>
> > > >>>> Hervé
> > > >>>>
> > > >>>>
> ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>
> > > >>
> > >
> > > Thanks,
> > >
> > > Jason
> > >
> > > ----------------------------------------------------------
> > > Jason van Zyl
> > > Founder, Takari and Apache Maven
> > > http://twitter.com/jvanzyl
> > > http://twitter.com/takari_io
> > > ---------------------------------------------------------
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Igor Fedorenko <ig...@ifedorenko.com>.
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 also supported by Tycho. Am I wrong?
> Removing "Maven" and just call it Artifact Resolver API (ara) solves
> this.
> It's the API for resolving artifacts in Maven.
> But, it might just be me interpreting this wrong.
>
> /Anders
>
> On Thu, Jul 28, 2016 at 3:47 PM, Jason van Zyl <ja...@takari.io> 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 anything else. Let’s
> > just make it better for our specific use cases instead of imagining this is
> > going to be a general purpose tool. It is clear that this never happened
> > and probably never will. Does it matter?
> >
> > > On Jul 28, 2016, at 6:12 AM, Anders Hammar <an...@hammar.net> wrote:
> > >
> > > 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 <mi...@apache.org>
> > > wrote:
> > >
> > >> 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
> > >>> I
> > >>> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
> > >>>
> > >>> What exactly is wrong with org.apache.maven.ara or
> > >>> org.apache.maven.artifact.resolver.api if we compare with
> > >>> org.apache.maven.mara to me the m in mara is redundant because we
> > already
> > >>> have the maven... so either if we want a short package name then `ara`
> > is
> > >>> better... or we want an understandable package name... same goes for
> > >>> artifactIds
> > >>>
> > >>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
> > >>>
> > >>> 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 while working in
> > private on
> > >>>> the
> > >>>> topic:
> > >>>> - Akasha https://en.wikipedia.org/wiki/Akasha
> > >>>> - Maven Artifact Resolver API ("mara" when used as package name or
> > >>>> artifactid
> > >>>> or in maven-mara-provider)
> > >>>>
> > >>>>
> > >>>> Does anybody have another idea?
> > >>>> Is there a preference in the community?
> > >>>>
> > >>>> Regards,
> > >>>>
> > >>>> Hervé
> > >>>>
> > >>>> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >>
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Takari and Apache Maven
> > http://twitter.com/jvanzyl
> > http://twitter.com/takari_io
> > ---------------------------------------------------------
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
> On Jul 28, 2016, at 10:07 AM, Anders Hammar <an...@hammar.net> 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 wrong. Tycho uses p2 to resolve artifacts.
> Removing "Maven" and just call it Artifact Resolver API (ara) solves this.
> It's the API for resolving artifacts in Maven.
> But, it might just be me interpreting this wrong.
>
Artifact Resolution API is fine too.
> /Anders
>
> On Thu, Jul 28, 2016 at 3:47 PM, Jason van Zyl <ja...@takari.io> 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 anything else. Let’s
>> just make it better for our specific use cases instead of imagining this is
>> going to be a general purpose tool. It is clear that this never happened
>> and probably never will. Does it matter?
>>
>>> On Jul 28, 2016, at 6:12 AM, Anders Hammar <an...@hammar.net> wrote:
>>>
>>> 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 <mi...@apache.org>
>>> wrote:
>>>
>>>> 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
>>>>> I
>>>>> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
>>>>>
>>>>> What exactly is wrong with org.apache.maven.ara or
>>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>>> org.apache.maven.mara to me the m in mara is redundant because we
>> already
>>>>> have the maven... so either if we want a short package name then `ara`
>> is
>>>>> better... or we want an understandable package name... same goes for
>>>>> artifactIds
>>>>>
>>>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>>
>>>>> 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 while working in
>> private on
>>>>>> the
>>>>>> topic:
>>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>>> artifactid
>>>>>> or in maven-mara-provider)
>>>>>>
>>>>>>
>>>>>> Does anybody have another idea?
>>>>>> Is there a preference in the community?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hervé
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Anders Hammar <an...@hammar.net>.
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 resolving artifacts in Maven.
But, it might just be me interpreting this wrong.
/Anders
On Thu, Jul 28, 2016 at 3:47 PM, Jason van Zyl <ja...@takari.io> 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 anything else. Let’s
> just make it better for our specific use cases instead of imagining this is
> going to be a general purpose tool. It is clear that this never happened
> and probably never will. Does it matter?
>
> > On Jul 28, 2016, at 6:12 AM, Anders Hammar <an...@hammar.net> wrote:
> >
> > 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 <mi...@apache.org>
> > wrote:
> >
> >> 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
> >>> I
> >>> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
> >>>
> >>> What exactly is wrong with org.apache.maven.ara or
> >>> org.apache.maven.artifact.resolver.api if we compare with
> >>> org.apache.maven.mara to me the m in mara is redundant because we
> already
> >>> have the maven... so either if we want a short package name then `ara`
> is
> >>> better... or we want an understandable package name... same goes for
> >>> artifactIds
> >>>
> >>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
> >>>
> >>> 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 while working in
> private on
> >>>> the
> >>>> topic:
> >>>> - Akasha https://en.wikipedia.org/wiki/Akasha
> >>>> - Maven Artifact Resolver API ("mara" when used as package name or
> >>>> artifactid
> >>>> or in maven-mara-provider)
> >>>>
> >>>>
> >>>> Does anybody have another idea?
> >>>> Is there a preference in the community?
> >>>>
> >>>> Regards,
> >>>>
> >>>> Hervé
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
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 make it better for our specific use cases instead of imagining this is going to be a general purpose tool. It is clear that this never happened and probably never will. Does it matter?
> On Jul 28, 2016, at 6:12 AM, Anders Hammar <an...@hammar.net> wrote:
>
> 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 <mi...@apache.org>
> wrote:
>
>> 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
>>> I
>>> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
>>>
>>> What exactly is wrong with org.apache.maven.ara or
>>> org.apache.maven.artifact.resolver.api if we compare with
>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>> have the maven... so either if we want a short package name then `ara` is
>>> better... or we want an understandable package name... same goes for
>>> artifactIds
>>>
>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>
>>> 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 while working in private on
>>>> the
>>>> topic:
>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>> artifactid
>>>> or in maven-mara-provider)
>>>>
>>>>
>>>> Does anybody have another idea?
>>>> Is there a preference in the community?
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Anders Hammar <an...@hammar.net>.
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 <mi...@apache.org>
wrote:
> 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
>> I
>> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
>>
>> What exactly is wrong with org.apache.maven.ara or
>> org.apache.maven.artifact.resolver.api if we compare with
>> org.apache.maven.mara to me the m in mara is redundant because we already
>> have the maven... so either if we want a short package name then `ara` is
>> better... or we want an understandable package name... same goes for
>> artifactIds
>>
>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>
>> 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 while working in private on
>>> the
>>> topic:
>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>> artifactid
>>> or in maven-mara-provider)
>>>
>>>
>>> Does anybody have another idea?
>>> Is there a preference in the community?
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Michael Osipov <mi...@apache.org>.
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 I
> say it, e.g. https://www.youtube.com/watch?v=d6ITDfkwKTA
>
> What exactly is wrong with org.apache.maven.ara or
> org.apache.maven.artifact.resolver.api if we compare with
> org.apache.maven.mara to me the m in mara is redundant because we already
> have the maven... so either if we want a short package name then `ara` is
> better... or we want an understandable package name... same goes for
> artifactIds
>
> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>
>> 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 while working in private on
>> the
>> topic:
>> - Akasha https://en.wikipedia.org/wiki/Akasha
>> - Maven Artifact Resolver API ("mara" when used as package name or
>> artifactid
>> or in maven-mara-provider)
>>
>>
>> Does anybody have another idea?
>> Is there a preference in the community?
>>
>> Regards,
>>
>> Hervé
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Uwe Barthel <ba...@x-reizend.de>.
> everybody ok for:
> - name: "Artifact Resolver"
> - groupId: org.apache.maven.resolver
> - artifactId: resolver(-*)
Why not more formal like:
-name: Maven Artifact Resolver
-groupId: org.apache.maven.[artifact | resolver]
-artifactId: artifact-resolver
-- barthel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Hervé BOUTEMY <he...@free.fr>.
plan implemented in git
https://git1-us-west.apache.org/repos/asf?p=maven-aether.git;a=commit;h=27f8bd7360d1114b0e2972a49c01adfbe24da272
resulting documentation will appear soon at
http://maven.apache.org/resolver-archives/resolver-LATEST/
If something is wrong, please tell
Once this first step is ok, I'll finish the work (do other modules, create
JIRA project, rename git repo)
Regards,
Hervé
Le dimanche 28 août 2016 22:44:56 Hervé BOUTEMY a écrit :
> feedback consolidated in http://svn.apache.org/r1758149
>
> Here is the plan now:
> http://maven.apache.org/aether-archives/aether.html
>
>
> Any more changes before I implement it?
>
> Regards,
>
> Hervé
>
> Le vendredi 26 août 2016 20:45:53 Igor Fedorenko a écrit :
> > On Fri, Aug 26, 2016, at 12:51 AM, Michael Osipov wrote:
> > > Am 2016-08-25 um 23:20 schrieb Hervé BOUTEMY:
> > > > ok, we can change groupId
> > > >
> > > > everybody ok for:
> > > > - name: "Artifact Resolver"
> > >
> > > Not Maven Artifact Resolver?
> > >
> > > > - groupId: org.apache.maven.resolver
> > > > - artifactId: resolver(-*)
> > >
> > > Same here maven-resolver-...?
> >
> > I like these better, artifactId in particular.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Hervé BOUTEMY <he...@free.fr>.
feedback consolidated in http://svn.apache.org/r1758149
Here is the plan now:
http://maven.apache.org/aether-archives/aether.html
Any more changes before I implement it?
Regards,
Hervé
Le vendredi 26 août 2016 20:45:53 Igor Fedorenko a écrit :
> On Fri, Aug 26, 2016, at 12:51 AM, Michael Osipov wrote:
> > Am 2016-08-25 um 23:20 schrieb Hervé BOUTEMY:
> > > ok, we can change groupId
> > >
> > > everybody ok for:
> > > - name: "Artifact Resolver"
> >
> > Not Maven Artifact Resolver?
> >
> > > - groupId: org.apache.maven.resolver
> > > - artifactId: resolver(-*)
> >
> > Same here maven-resolver-...?
>
> I like these better, artifactId in particular.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Igor Fedorenko <ig...@ifedorenko.com>.
On Fri, Aug 26, 2016, at 12:51 AM, Michael Osipov wrote:
> Am 2016-08-25 um 23:20 schrieb Hervé BOUTEMY:
> > ok, we can change groupId
> >
> > everybody ok for:
> > - name: "Artifact Resolver"
>
> Not Maven Artifact Resolver?
>
> > - groupId: org.apache.maven.resolver
> > - artifactId: resolver(-*)
>
> Same here maven-resolver-...?
>
>
I like these better, artifactId in particular.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-08-25 um 23:20 schrieb Hervé BOUTEMY:
> ok, we can change groupId
>
> everybody ok for:
> - name: "Artifact Resolver"
Not Maven Artifact Resolver?
> - groupId: org.apache.maven.resolver
> - artifactId: resolver(-*)
Same here maven-resolver-...?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
+1
> On Aug 25, 2016, at 2:20 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>
> ok, we can change groupId
>
> everybody ok for:
> - name: "Artifact Resolver"
> - groupId: org.apache.maven.resolver
> - artifactId: resolver(-*)
>
> ?
>
> or are there any other proposal on these 3 choices?
>
> Regards,
>
> Hervé
>
> Le mercredi 3 août 2016 16:04:36 Jason van Zyl a écrit :
>> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver
>> for the package names is more consistent with the other naming in that
>> document.
>>> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>>>
>>> true: I know it sounded familiar... :)
>>>
>>> this artifact seems used by maven-remote-resources-plugin only
>>>
>>> And if you look at the content, it contains a little helper to resolve
>>> dependencies: we should probably deprecate it at the end
>>>
>>>
>>> If there is no objection, I'll update code in a few days to match
>>> http://maven.apache.org/aether-archives/aether.html
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ----- Mail original -----
>>> De: "Michael Osipov" <mi...@apache.org>
>>> À: "Maven Developers List" <de...@maven.apache.org>
>>> Envoyé: Samedi 30 Juillet 2016 00:24:08
>>> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>>>
>>> Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
>>>> I like the org.apache.maven.artifact.resolver idea added to "Maven
>>>> Artifact
>>>> Resolver API" description
>>>>
>>>> I prepared a projection based on this idea:
>>>> http://maven.apache.org/aether-archives/aether.html
>>>
>>> Attention, we already have:
>>> https://maven.apache.org/shared/maven-artifact-resolver/
>>>
>>> Though, this module has not been updates for years. We shall try to
>>> avoid confusion here.
>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>>>>> 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 with org.apache.maven.ara or
>>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>>> org.apache.maven.mara to me the m in mara is redundant because we
>>>>> already
>>>>> have the maven... so either if we want a short package name then `ara`
>>>>> is
>>>>> better... or we want an understandable package name... same goes for
>>>>> artifactIds
>>>>>
>>>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>>> 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 while working in private
>>>>>> on
>>>>>> the
>>>>>> topic:
>>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>>> artifactid
>>>>>> or in maven-mara-provider)
>>>>>>
>>>>>>
>>>>>> Does anybody have another idea?
>>>>>> Is there a preference in the community?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hervé
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Hervé BOUTEMY <he...@free.fr>.
ok, we can change groupId
everybody ok for:
- name: "Artifact Resolver"
- groupId: org.apache.maven.resolver
- artifactId: resolver(-*)
?
or are there any other proposal on these 3 choices?
Regards,
Hervé
Le mercredi 3 août 2016 16:04:36 Jason van Zyl a écrit :
> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver
> for the package names is more consistent with the other naming in that
> document.
> > On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
> >
> > true: I know it sounded familiar... :)
> >
> > this artifact seems used by maven-remote-resources-plugin only
> >
> > And if you look at the content, it contains a little helper to resolve
> > dependencies: we should probably deprecate it at the end
> >
> >
> > If there is no objection, I'll update code in a few days to match
> > http://maven.apache.org/aether-archives/aether.html
> >
> > Regards,
> >
> > Hervé
> >
> > ----- Mail original -----
> > De: "Michael Osipov" <mi...@apache.org>
> > À: "Maven Developers List" <de...@maven.apache.org>
> > Envoyé: Samedi 30 Juillet 2016 00:24:08
> > Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
> >
> > Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
> >> I like the org.apache.maven.artifact.resolver idea added to "Maven
> >> Artifact
> >> Resolver API" description
> >>
> >> I prepared a projection based on this idea:
> >> http://maven.apache.org/aether-archives/aether.html
> >
> > Attention, we already have:
> > https://maven.apache.org/shared/maven-artifact-resolver/
> >
> > Though, this module has not been updates for years. We shall try to
> > avoid confusion here.
> >
> >> Regards,
> >>
> >> Hervé
> >>
> >> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
> >>> 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 with org.apache.maven.ara or
> >>> org.apache.maven.artifact.resolver.api if we compare with
> >>> org.apache.maven.mara to me the m in mara is redundant because we
> >>> already
> >>> have the maven... so either if we want a short package name then `ara`
> >>> is
> >>> better... or we want an understandable package name... same goes for
> >>> artifactIds
> >>>
> >>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
> >>>> 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 while working in private
> >>>> on
> >>>> the
> >>>> topic:
> >>>> - Akasha https://en.wikipedia.org/wiki/Akasha
> >>>> - Maven Artifact Resolver API ("mara" when used as package name or
> >>>> artifactid
> >>>> or in maven-mara-provider)
> >>>>
> >>>>
> >>>> Does anybody have another idea?
> >>>> Is there a preference in the community?
> >>>>
> >>>> Regards,
> >>>>
> >>>> Hervé
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by he...@free.fr.
if I let apart the confusion with java jars...
it's not a specification: the specification of the repository is in maven-aether-provider dependencies
Regards,
Hervé
----- Mail original -----
De: "Christian Schulte" <cs...@schulte.it>
À: "Maven Developers List" <de...@maven.apache.org>
Envoyé: Jeudi 4 Août 2016 01:29:17
Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
It's really all about JARs...
"Java Artifact Repository Specification"
JARS
Happenstance.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Stephen Connolly <st...@gmail.com>.
+1
On 5 August 2016 at 14:34, Tamás Cservenák <ta...@cservenak.net> wrote:
> ... Mercury....
>
> On Thu, Aug 4, 2016 at 11:09 PM Jason van Zyl <ja...@takari.io> wrote:
>
> > When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and
> > Tycho. None of them very useful for people to understand what they
> actually
> > do. I think I’m done with catchy names. I’m old.
> >
> >
>
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
These will both confuse people. Mercury is a failed project from the past here and no one will know what the project is from the name Caduceus. Please, let’s use a real word that best represents (yes, maybe not ideal) what the library will do.
> On Aug 8, 2016, at 4:22 PM, Robert Scholte <rf...@apache.org> wrote:
>
> Mercury2? ... Caduceus (Hypothetical moon of Mercury)
>
> On Fri, 05 Aug 2016 15:34:04 +0200, Tamás Cservenák <ta...@cservenak.net> wrote:
>
>> ... Mercury....
>>
>> On Thu, Aug 4, 2016 at 11:09 PM Jason van Zyl <ja...@takari.io> wrote:
>>
>>> When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and
>>> Tycho. None of them very useful for people to understand what they actually
>>> do. I think I’m done with catchy names. I’m old.
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Robert Scholte <rf...@apache.org>.
Mercury2? ... Caduceus (Hypothetical moon of Mercury)
On Fri, 05 Aug 2016 15:34:04 +0200, Tamás Cservenák <ta...@cservenak.net>
wrote:
> ... Mercury....
>
> On Thu, Aug 4, 2016 at 11:09 PM Jason van Zyl <ja...@takari.io> wrote:
>
>> When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and
>> Tycho. None of them very useful for people to understand what they
>> actually
>> do. I think I’m done with catchy names. I’m old.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Tamás Cservenák <ta...@cservenak.net>.
... Mercury....
On Thu, Aug 4, 2016 at 11:09 PM Jason van Zyl <ja...@takari.io> wrote:
> When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and
> Tycho. None of them very useful for people to understand what they actually
> do. I think I’m done with catchy names. I’m old.
>
>
AW: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christofer Dutz <ch...@c-ware.de>.
AIR could be something Adobe might have a problem with ...
Chris
________________________________
Von: Jörg Schaible <jo...@bpm-inspire.com>
Gesendet: Freitag, 5. August 2016 14:54:29
An: dev@maven.apache.org
Betreff: Re: [DISCUSSION] finishing Aether import: help find a new name
Uwe Barthel wrote:
> Hi,
>
>> Eclipse owns the Aether name. We cannot use the name Aether.
>
> And the Eclipse Foundation doesn't like to provide that name to the ASF
> (only the name without the eclipse namespace)?
>
> Aethel means over the AIR.
>
> WDYT about org.Apache.maven.air: _A_rtifact _I_inqui_R_e. Inquire is more
> general than resolve?
>
> -- barthel
Prepend 'M' ... ;-)
Mare
M_aven
A_rtefact
RE_solver
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jörg Schaible <jo...@bpm-inspire.com>.
Uwe Barthel wrote:
> Hi,
>
>> Eclipse owns the Aether name. We cannot use the name Aether.
>
> And the Eclipse Foundation doesn't like to provide that name to the ASF
> (only the name without the eclipse namespace)?
>
> Aethel means over the AIR.
>
> WDYT about org.Apache.maven.air: _A_rtifact _I_inqui_R_e. Inquire is more
> general than resolve?
>
> -- barthel
Prepend 'M' ... ;-)
Mare
M_aven
A_rtefact
RE_solver
- J�rg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Uwe Barthel <ba...@x-reizend.de>.
Hi,
> Eclipse owns the Aether name. We cannot use the name Aether.
And the Eclipse Foundation doesn't like to provide that name to the ASF
(only the name without the eclipse namespace)?
Aethel means over the AIR.
WDYT about org.Apache.maven.air: _A_rtifact _I_inqui_R_e. Inquire is more
general than resolve?
-- barthel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Stephen Connolly <st...@gmail.com>.
Eclipse owns the Aether name. We cannot use the name Aether.
On 5 August 2016 at 05:14, Uwe Barthel <ba...@x-reizend.de> wrote:
> Hi,
>
> I know Aether is one of the catchy non telling name.
> But, why not leave Aether with new Maven namespace like
> org.apache.maven.aether?
>
> -- barthel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Uwe Barthel <ba...@x-reizend.de>.
Hi,
I know Aether is one of the catchy non telling name.
But, why not leave Aether with new Maven namespace like org.apache.maven.aether?
-- barthel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/05/16 um 01:21 schrieb Gary Gregory:
> On Thu, Aug 4, 2016 at 3:24 PM, Christian Schulte <cs...@schulte.it> wrote:
>
>> Am 08/05/16 um 00:15 schrieb Gary Gregory:
>>> But here you would just tell the manager: "I want to use Maven" as
>> opposed
>>> to "I want to use Ant and Ivy".
>>
>> So lets rename Maven. We need a name sounding cool to management. Just
>> so that we do not need to discuss why we want to use it...something
>> implying less costs (due to speed or whatever).
>>
>
> But Maven IS a cool name :-) and it means "an expert or connoisseur", what
> could be better! I am serious to boot :-)
>
Did he just say build monkeys? :-)
Seriously. I never noticed that. Perfect demonstration of how much I do
not care about product names. Glad I've choosen the right build tool for
me not just because of its name. I thought "Maven" really is just a name.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Gary Gregory <ga...@gmail.com>.
On Thu, Aug 4, 2016 at 3:24 PM, Christian Schulte <cs...@schulte.it> wrote:
> Am 08/05/16 um 00:15 schrieb Gary Gregory:
> > But here you would just tell the manager: "I want to use Maven" as
> opposed
> > to "I want to use Ant and Ivy".
>
> So lets rename Maven. We need a name sounding cool to management. Just
> so that we do not need to discuss why we want to use it...something
> implying less costs (due to speed or whatever).
>
But Maven IS a cool name :-) and it means "an expert or connoisseur", what
could be better! I am serious to boot :-)
Gary
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/05/16 um 00:15 schrieb Gary Gregory:
> But here you would just tell the manager: "I want to use Maven" as opposed
> to "I want to use Ant and Ivy".
So lets rename Maven. We need a name sounding cool to management. Just
so that we do not need to discuss why we want to use it...something
implying less costs (due to speed or whatever).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by he...@free.fr.
yes, in the current case, this is an internal component name we're looking for: end-users will not notice
Regards,
Hervé
----- Mail original -----
De: "Gary Gregory" <ga...@gmail.com>
À: "Maven Developers List" <de...@maven.apache.org>
Envoyé: Vendredi 5 Août 2016 00:15:24
Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
On Thu, Aug 4, 2016 at 2:53 PM, Christian Schulte <cs...@schulte.it> wrote:
> Am 08/04/16 um 23:08 schrieb Jason van Zyl:
> > When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and
> Tycho. None of them very useful for people to understand what they actually
> do. I think I’m done with catchy names. I’m old.
>
> There is one quote I can make here. Working on a boring project I needed
> to generate code massively. When I told the manager I would go using
> something called Velocity he replied: "Velocity. I like that one. Go for
> it. This will speed things up." Just because the name implied I will get
> the job done quicker using it. If the same technology would have been
> called "something very error-prone templating engine" he would have
> said: Oh no. Don't do it that way...
>
But here you would just tell the manager: "I want to use Maven" as opposed
to "I want to use Ant and Ivy".
So this seems to be all about an internal name.
Gary
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Gary Gregory <ga...@gmail.com>.
On Thu, Aug 4, 2016 at 2:53 PM, Christian Schulte <cs...@schulte.it> wrote:
> Am 08/04/16 um 23:08 schrieb Jason van Zyl:
> > When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and
> Tycho. None of them very useful for people to understand what they actually
> do. I think I’m done with catchy names. I’m old.
>
> There is one quote I can make here. Working on a boring project I needed
> to generate code massively. When I told the manager I would go using
> something called Velocity he replied: "Velocity. I like that one. Go for
> it. This will speed things up." Just because the name implied I will get
> the job done quicker using it. If the same technology would have been
> called "something very error-prone templating engine" he would have
> said: Oh no. Don't do it that way...
>
But here you would just tell the manager: "I want to use Maven" as opposed
to "I want to use Ant and Ivy".
So this seems to be all about an internal name.
Gary
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/04/16 um 23:08 schrieb Jason van Zyl:
> When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and Tycho. None of them very useful for people to understand what they actually do. I think I\u2019m done with catchy names. I\u2019m old.
There is one quote I can make here. Working on a boring project I needed
to generate code massively. When I told the manager I would go using
something called Velocity he replied: "Velocity. I like that one. Go for
it. This will speed things up." Just because the name implied I will get
the job done quicker using it. If the same technology would have been
called "something very error-prone templating engine" he would have
said: Oh no. Don't do it that way...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and Tycho. None of them very useful for people to understand what they actually do. I think I’m done with catchy names. I’m old.
> On Aug 4, 2016, at 4:33 PM, Christian Schulte <cs...@schulte.it> wrote:
>
> Am 08/04/16 um 22:22 schrieb Jason van Zyl:
>> These are all discussions about abstractions we had when talking about Maven 1.x, so let me save you the circuitous route back to the fact that users don’t care about having an abstraction that lets them store artifacts as blobs in any potential systems coming from any potential source. People take artifacts from http servers and save them as files on disk. I think we would be better served evolving to the concrete thing it has actually become. To a Maven user it resolves artifacts, to someone who used Aether they resolved artifacts. What we see it as doesn’t matter, we know it does all sorts of things but apache-diritytree-selector-transformer-transporter-collector-resolver is probably not the best name.
>
> When in doubt, call it Susi. Maybe Susan. Depends.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/04/16 um 22:22 schrieb Jason van Zyl:
> These are all discussions about abstractions we had when talking about Maven 1.x, so let me save you the circuitous route back to the fact that users don\u2019t care about having an abstraction that lets them store artifacts as blobs in any potential systems coming from any potential source. People take artifacts from http servers and save them as files on disk. I think we would be better served evolving to the concrete thing it has actually become. To a Maven user it resolves artifacts, to someone who used Aether they resolved artifacts. What we see it as doesn\u2019t matter, we know it does all sorts of things but apache-diritytree-selector-transformer-transporter-collector-resolver is probably not the best name.
When in doubt, call it Susi. Maybe Susan. Depends.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
These are all discussions about abstractions we had when talking about Maven 1.x, so let me save you the circuitous route back to the fact that users don’t care about having an abstraction that lets them store artifacts as blobs in any potential systems coming from any potential source. People take artifacts from http servers and save them as files on disk. I think we would be better served evolving to the concrete thing it has actually become. To a Maven user it resolves artifacts, to someone who used Aether they resolved artifacts. What we see it as doesn’t matter, we know it does all sorts of things but apache-diritytree-selector-transformer-transporter-collector-resolver is probably not the best name.
You are thinking about this too much. I’m a user, I resolve artifacts.
> On Aug 4, 2016, at 3:44 PM, Christian Schulte <cs...@schulte.it> wrote:
>
> If I wanted to store my artifacts in a database instead of putting files
> into some well-known locations. Can I write an implementation of
> 'RepositorySystem' which allows me to do that? No. It's way too
> file-system based. A database would give me a blob. A path or a filename
> is meaningless for the way artifacts are stored/accessed. I'd need to
> convert that blob to a file locally when it needs to become part of some
> classpath, for example. Speaking about "RepositorySystem", File or URL
> is the wrong abstraction, in my opinion. A repository can be accessed
> over the network (hostname and port) using a protocol. No URL involved.
> No filesystem involved. Just thoughts.
>
> Regards,
> --
> Christian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Benson Margulies <bi...@gmail.com>.
We have this body of code. People in the world use it. Refactoring
this code to break its existing users, just to avoid an awkward name,
strike me as a poor use of time. My suggestion remains that we pick
some inoffensive descriptive string and use it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
If I wanted to store my artifacts in a database instead of putting files
into some well-known locations. Can I write an implementation of
'RepositorySystem' which allows me to do that? No. It's way too
file-system based. A database would give me a blob. A path or a filename
is meaningless for the way artifacts are stored/accessed. I'd need to
convert that blob to a file locally when it needs to become part of some
classpath, for example. Speaking about "RepositorySystem", File or URL
is the wrong abstraction, in my opinion. A repository can be accessed
over the network (hostname and port) using a protocol. No URL involved.
No filesystem involved. Just thoughts.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/04/16 um 18:44 schrieb Paul Benedict:
> In my own experience regarding the difficulty of naming something, it has
> always indicated the codebase is too big and multi-functional.
>
> Thus, there are two paths to take:
> 1) Slap a brand name on it because no descriptive name can succinctly
> capture all the provided functionality
> 2) Break down the code base so you can apply individual descriptive names
>
> So, perhaps a change of perspective could help here....
+1
> Has anyone thought about breaking apart Aether after the import?
It does a lot of different things and it overcomplicates things, in my
opinion. Maybe we should try to find a better interface than
'RepositorySystem'/split that up/review the API/improve the abstractions.
<https://git-wip-us.apache.org/repos/asf?p=maven-aether.git;a=blob;f=aether-api/src/main/java/org/eclipse/aether/RepositorySystem.java;h=8706f891afa2d76e1d90c54dc7ce8bb51c930dbd;hb=HEAD>
In my opinion the following methods do not belong there:
'install'
'collectDependencies'
'resolveDependencies'
'newLocalRepositoryManager'
'newSyncContext'
'newResolutionRepositories'
'newDeploymentRepository'
The methods to keep should be implemented differently. For example:
'resolveArtifact': Resolves the path for an artifact. The artifact will
be downloaded to the local repository if necessary.
The whole local repository logic should not be part of that. It's just a
cache to be put in front of it. Has nothing to do with a 'RepositorySystem'.
And then there is lack of features/use cases requested by users. Things
like getting the list of all available artifacts of a given group id.
Missing queries. A lot - if not all - of the methods of that interface
could be replaced by a yet to be implemented query language which can
capture all use-cases in a single place. Finding versions, finding
artifacts, finding paths. All simple queries. Deploy is the only one not
just querying but modifying the repository. That makes it 2 methods. One
for querying the repository. One for modifying the repository. You could
as well throw away Aether - just take what is needed to retain backwards
compatibility and start from scratch with something much more simple.
Leads to something like Maven Artifact Repository Query Language, for
example.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Paul Benedict <pb...@apache.org>.
In my own experience regarding the difficulty of naming something, it has
always indicated the codebase is too big and multi-functional.
Thus, there are two paths to take:
1) Slap a brand name on it because no descriptive name can succinctly
capture all the provided functionality
2) Break down the code base so you can apply individual descriptive names
So, perhaps a change of perspective could help here....
Has anyone thought about breaking apart Aether after the import?
Cheers,
Paul
On Thu, Aug 4, 2016 at 11:27 AM, Robert Scholte <rf...@apache.org>
wrote:
> It is all about Maven coordinates: groupId + artifactId + version +
> extension ( + classifier)
> This all together results in a URL to a repository. In case of remote
> repositories these work both with M1 and M2 repository layouts (yes, the
> name is confusing...)
> So it is not just about java files/artifacts, any file with a Maven
> coordinate will do.
>
> Robert
>
>
> On Thu, 04 Aug 2016 01:29:17 +0200, Christian Schulte <cs...@schulte.it>
> wrote:
>
> It's really all about JARs...
>>
>> "Java Artifact Repository Specification"
>>
>> JARS
>>
>> Happenstance.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/04/16 um 18:27 schrieb Robert Scholte:
> It is all about Maven coordinates: groupId + artifactId + version +
> extension ( + classifier)
> This all together results in a URL to a repository. In case of remote
> repositories these work both with M1 and M2 repository layouts (yes, the
> name is confusing...)
> So it is not just about java files/artifacts, any file with a Maven
> coordinate will do.
Is it really Maven coordinates or just coordinates. Let the layout be
the implementation. Like a database. All you want to do is run queries
against an artifact store and modify that.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Robert Scholte <rf...@apache.org>.
It is all about Maven coordinates: groupId + artifactId + version +
extension ( + classifier)
This all together results in a URL to a repository. In case of remote
repositories these work both with M1 and M2 repository layouts (yes, the
name is confusing...)
So it is not just about java files/artifacts, any file with a Maven
coordinate will do.
Robert
On Thu, 04 Aug 2016 01:29:17 +0200, Christian Schulte <cs...@schulte.it>
wrote:
> It's really all about JARs...
>
> "Java Artifact Repository Specification"
>
> JARS
>
> Happenstance.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Manfred Moser <ma...@simpligility.com>.
Because we otherwise end up with really long names and even wrong names for such external facing components.
E.g. we have
Maven Artifact Resolver Ant Plugin
as the new name. It would be a long name ... and it would be wrong too. Since it can also install and deploy build outputs.
Of course we might opt for something else like
Maven Repository Format Support Ant Tasks
Or just cut it all and go for
Maven Ant Tasks
and we are good again.
I guess somebody just decide and move on. Its just a name ;-)
Manfred
Benson Margulies wrote on 2016-08-04 08:42:
> I my view, we should not be inventing brand names for miscellaneous
> internal pieces of Maven. We have hundreds of such pieces. Why give
> nicknames to some?
>
> On Thu, Aug 4, 2016 at 11:40 AM, Manfred Moser <ma...@simpligility.com>
> wrote:
>> I also prefer something like a short name even if its a shortcut like Mars. In
>> fact.. I like Mars. We would have the mars-core and other artifacts and maybe
>> also the Mars Ant Task (port of Aether Ant Tasks..
>> https://maven.apache.org/components/aether-archives/aether-ant-tasks-LATEST/)
>>
>> Manfred
>>
>> Christian Schulte wrote on 2016-08-04 01:49:
>>
>>> Am 08/04/16 um 02:34 schrieb Ralph Goers:
>>>> I much prefer MARS, especially if you can come up with corresponding
>>>> wordplay
>>>> for VENUS\u2026 ;-)
>>>
>>> Better than 'resolver'.
>>>
>>>>
>>>> Seriously, the overlap with Java ARchive is bound to be confusing, and might
>>>> even make people think that the component has something to do with them.
>>>
>>> It has. But who...
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Benson Margulies <bi...@gmail.com>.
I my view, we should not be inventing brand names for miscellaneous
internal pieces of Maven. We have hundreds of such pieces. Why give
nicknames to some?
On Thu, Aug 4, 2016 at 11:40 AM, Manfred Moser <ma...@simpligility.com> wrote:
> I also prefer something like a short name even if its a shortcut like Mars. In fact.. I like Mars. We would have the mars-core and other artifacts and maybe also the Mars Ant Task (port of Aether Ant Tasks.. https://maven.apache.org/components/aether-archives/aether-ant-tasks-LATEST/)
>
> Manfred
>
> Christian Schulte wrote on 2016-08-04 01:49:
>
>> Am 08/04/16 um 02:34 schrieb Ralph Goers:
>>> I much prefer MARS, especially if you can come up with corresponding wordplay
>>> for VENUS… ;-)
>>
>> Better than 'resolver'.
>>
>>>
>>> Seriously, the overlap with Java ARchive is bound to be confusing, and might
>>> even make people think that the component has something to do with them.
>>
>> It has. But who...
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Manfred Moser <ma...@simpligility.com>.
I also prefer something like a short name even if its a shortcut like Mars. In fact.. I like Mars. We would have the mars-core and other artifacts and maybe also the Mars Ant Task (port of Aether Ant Tasks.. https://maven.apache.org/components/aether-archives/aether-ant-tasks-LATEST/)
Manfred
Christian Schulte wrote on 2016-08-04 01:49:
> Am 08/04/16 um 02:34 schrieb Ralph Goers:
>> I much prefer MARS, especially if you can come up with corresponding wordplay
>> for VENUS\u2026 ;-)
>
> Better than 'resolver'.
>
>>
>> Seriously, the overlap with Java ARchive is bound to be confusing, and might
>> even make people think that the component has something to do with them.
>
> It has. But who...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/04/16 um 02:34 schrieb Ralph Goers:
> I much prefer MARS, especially if you can come up with corresponding wordplay for VENUS\u2026 ;-)
Better than 'resolver'.
>
> Seriously, the overlap with Java ARchive is bound to be confusing, and might even make people think that the component has something to do with them.
It has. But who...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Ralph Goers <ra...@dslextreme.com>.
I much prefer MARS, especially if you can come up with corresponding wordplay for VENUS… ;-)
Seriously, the overlap with Java ARchive is bound to be confusing, and might even make people think that the component has something to do with them.
Ralph
> On Aug 3, 2016, at 4:29 PM, Christian Schulte <cs...@schulte.it> wrote:
>
> It's really all about JARs...
>
> "Java Artifact Repository Specification"
>
> JARS
>
> Happenstance.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
It's really all about JARs...
"Java Artifact Repository Specification"
JARS
Happenstance.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Guys. Just because it fits perfectly the Java universe. "Java Artifact
Repository Specification".
JARS
Regards,
--
Christian
Am 04.08.2016 um 00:21 schrieb Christian Schulte:
> Am 08/03/16 um 23:47 schrieb Michael Osipov:
>> I proposed Maven Artifact Universe, but received no response.
> Pretty close. In the Java universe we got used to talk about JSRs and
> JEPs and things like that. I am all for something along "Maven Artifact
> Repository Specification" and corresponding "Reference Implementation".
> Or "Artifact Repository Specification". We should really try to produce
> something, which could carry a package name like 'javax.*' or even
> 'java.*'. Everything else is heading into the wrong direction. Just my
> personal opinion.
>
> Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
Am 08/03/16 um 23:47 schrieb Michael Osipov:
> I proposed Maven Artifact Universe, but received no response.
Pretty close. In the Java universe we got used to talk about JSRs and
JEPs and things like that. I am all for something along "Maven Artifact
Repository Specification" and corresponding "Reference Implementation".
Or "Artifact Repository Specification". We should really try to produce
something, which could carry a package name like 'javax.*' or even
'java.*'. Everything else is heading into the wrong direction. Just my
personal opinion.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by he...@free.fr.
sorry, I find it somewhat abstract: it does not tell anything about the interactions
Even if I agree that resolver does not tell everything, just the majority and most complex
Regards,
Hervé
(sorry, on holidays with unusual email access: tracking such thread is not easy...)
----- Mail original -----
De: "Michael Osipov" <mi...@apache.org>
À: "Maven Developers List" <de...@maven.apache.org>
Envoyé: Mercredi 3 Août 2016 23:47:41
Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
I proposed Maven Artifact Universe, but received no response.
Am 2016-08-03 um 23:32 schrieb Christian Schulte:
> It's just a name - I know. Personally, I disagree with 'resolver'. It's
> so much more. It also abstracts the transfers/transports etc. It is an
> abstraction to manage and access a repository (whatever that may mean)
> of artifacts (whatever that may mean) by employing a special directory
> structure and file naming convention we may want to call "Maven Artifact
> Repository Specification". Please. Do not call it "resolver". That's
> just one tiny part of all of this. Just in case:
>
> +1 for calling it "resolver", although in my opinion that is a really
> misleading name to use.
>
>
> Am 08/03/16 um 22:48 schrieb Michael Osipov:
>> Am 2016-08-03 um 22:04 schrieb Jason van Zyl:
>>> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document.
>>
>> Maves sense, probably this project should be named
>> maven.a.o/artifact-resolver
>>
>> maven-artifact-resolver.git and org.apache.maven.artifact.resolver
>>
>> It would make it consistent.
>>
>>>> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>>>>
>>>> true: I know it sounded familiar... :)
>>>>
>>>> this artifact seems used by maven-remote-resources-plugin only
>>>>
>>>> And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
>>>>
>>>>
>>>> If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> ----- Mail original -----
>>>> De: "Michael Osipov" <mi...@apache.org>
>>>> À: "Maven Developers List" <de...@maven.apache.org>
>>>> Envoyé: Samedi 30 Juillet 2016 00:24:08
>>>> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>>>>
>>>> Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
>>>>> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
>>>>> Resolver API" description
>>>>>
>>>>> I prepared a projection based on this idea:
>>>>> http://maven.apache.org/aether-archives/aether.html
>>>>
>>>> Attention, we already have:
>>>> https://maven.apache.org/shared/maven-artifact-resolver/
>>>>
>>>> Though, this module has not been updates for years. We shall try to
>>>> avoid confusion here.
>>>>
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>>>>>> 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 with org.apache.maven.ara or
>>>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>>>>> have the maven... so either if we want a short package name then `ara` is
>>>>>> better... or we want an understandable package name... same goes for
>>>>>> artifactIds
>>>>>>
>>>>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>>>> 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 while working in private on
>>>>>>> the
>>>>>>> topic:
>>>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>>>> artifactid
>>>>>>> or in maven-mara-provider)
>>>>>>>
>>>>>>>
>>>>>>> Does anybody have another idea?
>>>>>>> Is there a preference in the community?
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Hervé
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Takari and Apache Maven
>>> http://twitter.com/jvanzyl
>>> http://twitter.com/takari_io
>>> ---------------------------------------------------------
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Michael Osipov <mi...@apache.org>.
I proposed Maven Artifact Universe, but received no response.
Am 2016-08-03 um 23:32 schrieb Christian Schulte:
> It's just a name - I know. Personally, I disagree with 'resolver'. It's
> so much more. It also abstracts the transfers/transports etc. It is an
> abstraction to manage and access a repository (whatever that may mean)
> of artifacts (whatever that may mean) by employing a special directory
> structure and file naming convention we may want to call "Maven Artifact
> Repository Specification". Please. Do not call it "resolver". That's
> just one tiny part of all of this. Just in case:
>
> +1 for calling it "resolver", although in my opinion that is a really
> misleading name to use.
>
>
> Am 08/03/16 um 22:48 schrieb Michael Osipov:
>> Am 2016-08-03 um 22:04 schrieb Jason van Zyl:
>>> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document.
>>
>> Maves sense, probably this project should be named
>> maven.a.o/artifact-resolver
>>
>> maven-artifact-resolver.git and org.apache.maven.artifact.resolver
>>
>> It would make it consistent.
>>
>>>> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>>>>
>>>> true: I know it sounded familiar... :)
>>>>
>>>> this artifact seems used by maven-remote-resources-plugin only
>>>>
>>>> And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
>>>>
>>>>
>>>> If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> ----- Mail original -----
>>>> De: "Michael Osipov" <mi...@apache.org>
>>>> À: "Maven Developers List" <de...@maven.apache.org>
>>>> Envoyé: Samedi 30 Juillet 2016 00:24:08
>>>> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>>>>
>>>> Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
>>>>> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
>>>>> Resolver API" description
>>>>>
>>>>> I prepared a projection based on this idea:
>>>>> http://maven.apache.org/aether-archives/aether.html
>>>>
>>>> Attention, we already have:
>>>> https://maven.apache.org/shared/maven-artifact-resolver/
>>>>
>>>> Though, this module has not been updates for years. We shall try to
>>>> avoid confusion here.
>>>>
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>>>>>> 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 with org.apache.maven.ara or
>>>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>>>>> have the maven... so either if we want a short package name then `ara` is
>>>>>> better... or we want an understandable package name... same goes for
>>>>>> artifactIds
>>>>>>
>>>>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>>>> 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 while working in private on
>>>>>>> the
>>>>>>> topic:
>>>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>>>> artifactid
>>>>>>> or in maven-mara-provider)
>>>>>>>
>>>>>>>
>>>>>>> Does anybody have another idea?
>>>>>>> Is there a preference in the community?
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Hervé
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Takari and Apache Maven
>>> http://twitter.com/jvanzyl
>>> http://twitter.com/takari_io
>>> ---------------------------------------------------------
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by he...@free.fr.
the whole functionality of the lib is visible in one interface: RepositorySystem
http://maven.apache.org/aether-archives/aether-LATEST/apidocs/org/eclipse/aether/RepositorySystem.html
in this interface, 6 methods are about resolution + 1 about collection (a special "sort of" resolution) + 1 to read artifact descriptor
you're right, in addition, there is intall and deploy, which are the exact opposite for the artifact
and the 4 "new*" methods are internals
resolution against repositories is the majority of interactions, and what is in general the most complex: just install and deploy would not require such a piece of software
So I completely agree that naming the lib "resolver" is not perfect, but it seems to me the most clear...
Regards,
Hervé
----- Mail original -----
De: "Christian Schulte" <cs...@schulte.it>
À: "Maven Developers List" <de...@maven.apache.org>
Envoyé: Mercredi 3 Août 2016 23:32:11
Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
It's just a name - I know. Personally, I disagree with 'resolver'. It's
so much more. It also abstracts the transfers/transports etc. It is an
abstraction to manage and access a repository (whatever that may mean)
of artifacts (whatever that may mean) by employing a special directory
structure and file naming convention we may want to call "Maven Artifact
Repository Specification". Please. Do not call it "resolver". That's
just one tiny part of all of this. Just in case:
+1 for calling it "resolver", although in my opinion that is a really
misleading name to use.
Am 08/03/16 um 22:48 schrieb Michael Osipov:
> Am 2016-08-03 um 22:04 schrieb Jason van Zyl:
>> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document.
>
> Maves sense, probably this project should be named
> maven.a.o/artifact-resolver
>
> maven-artifact-resolver.git and org.apache.maven.artifact.resolver
>
> It would make it consistent.
>
>>> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>>>
>>> true: I know it sounded familiar... :)
>>>
>>> this artifact seems used by maven-remote-resources-plugin only
>>>
>>> And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
>>>
>>>
>>> If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ----- Mail original -----
>>> De: "Michael Osipov" <mi...@apache.org>
>>> À: "Maven Developers List" <de...@maven.apache.org>
>>> Envoyé: Samedi 30 Juillet 2016 00:24:08
>>> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>>>
>>> Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
>>>> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
>>>> Resolver API" description
>>>>
>>>> I prepared a projection based on this idea:
>>>> http://maven.apache.org/aether-archives/aether.html
>>>
>>> Attention, we already have:
>>> https://maven.apache.org/shared/maven-artifact-resolver/
>>>
>>> Though, this module has not been updates for years. We shall try to
>>> avoid confusion here.
>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>>>>> 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 with org.apache.maven.ara or
>>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>>>> have the maven... so either if we want a short package name then `ara` is
>>>>> better... or we want an understandable package name... same goes for
>>>>> artifactIds
>>>>>
>>>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>>> 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 while working in private on
>>>>>> the
>>>>>> topic:
>>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>>> artifactid
>>>>>> or in maven-mara-provider)
>>>>>>
>>>>>>
>>>>>> Does anybody have another idea?
>>>>>> Is there a preference in the community?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hervé
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Christian Schulte <cs...@schulte.it>.
It's just a name - I know. Personally, I disagree with 'resolver'. It's
so much more. It also abstracts the transfers/transports etc. It is an
abstraction to manage and access a repository (whatever that may mean)
of artifacts (whatever that may mean) by employing a special directory
structure and file naming convention we may want to call "Maven Artifact
Repository Specification". Please. Do not call it "resolver". That's
just one tiny part of all of this. Just in case:
+1 for calling it "resolver", although in my opinion that is a really
misleading name to use.
Am 08/03/16 um 22:48 schrieb Michael Osipov:
> Am 2016-08-03 um 22:04 schrieb Jason van Zyl:
>> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document.
>
> Maves sense, probably this project should be named
> maven.a.o/artifact-resolver
>
> maven-artifact-resolver.git and org.apache.maven.artifact.resolver
>
> It would make it consistent.
>
>>> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>>>
>>> true: I know it sounded familiar... :)
>>>
>>> this artifact seems used by maven-remote-resources-plugin only
>>>
>>> And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
>>>
>>>
>>> If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
>>>
>>> Regards,
>>>
>>> Herv�
>>>
>>> ----- Mail original -----
>>> De: "Michael Osipov" <mi...@apache.org>
>>> �: "Maven Developers List" <de...@maven.apache.org>
>>> Envoy�: Samedi 30 Juillet 2016 00:24:08
>>> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>>>
>>> Am 2016-07-30 um 00:03 schrieb Herv� BOUTEMY:
>>>> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
>>>> Resolver API" description
>>>>
>>>> I prepared a projection based on this idea:
>>>> http://maven.apache.org/aether-archives/aether.html
>>>
>>> Attention, we already have:
>>> https://maven.apache.org/shared/maven-artifact-resolver/
>>>
>>> Though, this module has not been updates for years. We shall try to
>>> avoid confusion here.
>>>
>>>> Regards,
>>>>
>>>> Herv�
>>>>
>>>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a �crit :
>>>>> 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 with org.apache.maven.ara or
>>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>>>> have the maven... so either if we want a short package name then `ara` is
>>>>> better... or we want an understandable package name... same goes for
>>>>> artifactIds
>>>>>
>>>>> On 28 July 2016 at 08:13, Herv� BOUTEMY <he...@free.fr> wrote:
>>>>>> 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 while working in private on
>>>>>> the
>>>>>> topic:
>>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>>> artifactid
>>>>>> or in maven-mara-provider)
>>>>>>
>>>>>>
>>>>>> Does anybody have another idea?
>>>>>> Is there a preference in the community?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Herv�
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Takari and Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-08-03 um 22:04 schrieb Jason van Zyl:
> Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document.
Maves sense, probably this project should be named
maven.a.o/artifact-resolver
maven-artifact-resolver.git and org.apache.maven.artifact.resolver
It would make it consistent.
>> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>>
>> true: I know it sounded familiar... :)
>>
>> this artifact seems used by maven-remote-resources-plugin only
>>
>> And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
>>
>>
>> If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
>>
>> Regards,
>>
>> Hervé
>>
>> ----- Mail original -----
>> De: "Michael Osipov" <mi...@apache.org>
>> À: "Maven Developers List" <de...@maven.apache.org>
>> Envoyé: Samedi 30 Juillet 2016 00:24:08
>> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>>
>> Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
>>> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
>>> Resolver API" description
>>>
>>> I prepared a projection based on this idea:
>>> http://maven.apache.org/aether-archives/aether.html
>>
>> Attention, we already have:
>> https://maven.apache.org/shared/maven-artifact-resolver/
>>
>> Though, this module has not been updates for years. We shall try to
>> avoid confusion here.
>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>>>> 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 with org.apache.maven.ara or
>>>> org.apache.maven.artifact.resolver.api if we compare with
>>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>>> have the maven... so either if we want a short package name then `ara` is
>>>> better... or we want an understandable package name... same goes for
>>>> artifactIds
>>>>
>>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>>> 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 while working in private on
>>>>> the
>>>>> topic:
>>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>>> artifactid
>>>>> or in maven-mara-provider)
>>>>>
>>>>>
>>>>> Does anybody have another idea?
>>>>> Is there a preference in the community?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Jason van Zyl <ja...@takari.io>.
Using org.apache.maven.resolver instead org.apache.maven.artifact.resolver for the package names is more consistent with the other naming in that document.
> On Aug 3, 2016, at 12:30 PM, herve.boutemy@free.fr wrote:
>
> true: I know it sounded familiar... :)
>
> this artifact seems used by maven-remote-resources-plugin only
>
> And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
>
>
> If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
>
> Regards,
>
> Hervé
>
> ----- Mail original -----
> De: "Michael Osipov" <mi...@apache.org>
> À: "Maven Developers List" <de...@maven.apache.org>
> Envoyé: Samedi 30 Juillet 2016 00:24:08
> Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
>
> Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
>> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
>> Resolver API" description
>>
>> I prepared a projection based on this idea:
>> http://maven.apache.org/aether-archives/aether.html
>
> Attention, we already have:
> https://maven.apache.org/shared/maven-artifact-resolver/
>
> Though, this module has not been updates for years. We shall try to
> avoid confusion here.
>
>> Regards,
>>
>> Hervé
>>
>> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>>> 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 with org.apache.maven.ara or
>>> org.apache.maven.artifact.resolver.api if we compare with
>>> org.apache.maven.mara to me the m in mara is redundant because we already
>>> have the maven... so either if we want a short package name then `ara` is
>>> better... or we want an understandable package name... same goes for
>>> artifactIds
>>>
>>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>>> 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 while working in private on
>>>> the
>>>> topic:
>>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>>> artifactid
>>>> or in maven-mara-provider)
>>>>
>>>>
>>>> Does anybody have another idea?
>>>> Is there a preference in the community?
>>>>
>>>> Regards,
>>>>
>>>> Hervé
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Takari and Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by he...@free.fr.
true: I know it sounded familiar... :)
this artifact seems used by maven-remote-resources-plugin only
And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end
If there is no objection, I'll update code in a few days to match http://maven.apache.org/aether-archives/aether.html
Regards,
Hervé
----- Mail original -----
De: "Michael Osipov" <mi...@apache.org>
À: "Maven Developers List" <de...@maven.apache.org>
Envoyé: Samedi 30 Juillet 2016 00:24:08
Objet: Re: [DISCUSSION] finishing Aether import: help find a new name
Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
> Resolver API" description
>
> I prepared a projection based on this idea:
> http://maven.apache.org/aether-archives/aether.html
Attention, we already have:
https://maven.apache.org/shared/maven-artifact-resolver/
Though, this module has not been updates for years. We shall try to
avoid confusion here.
> Regards,
>
> Hervé
>
> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>> 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 with org.apache.maven.ara or
>> org.apache.maven.artifact.resolver.api if we compare with
>> org.apache.maven.mara to me the m in mara is redundant because we already
>> have the maven... so either if we want a short package name then `ara` is
>> better... or we want an understandable package name... same goes for
>> artifactIds
>>
>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>> 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 while working in private on
>>> the
>>> topic:
>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>> artifactid
>>> or in maven-mara-provider)
>>>
>>>
>>> Does anybody have another idea?
>>> Is there a preference in the community?
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Michael Osipov <mi...@apache.org>.
Am 2016-07-30 um 00:03 schrieb Hervé BOUTEMY:
> I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
> Resolver API" description
>
> I prepared a projection based on this idea:
> http://maven.apache.org/aether-archives/aether.html
Attention, we already have:
https://maven.apache.org/shared/maven-artifact-resolver/
Though, this module has not been updates for years. We shall try to
avoid confusion here.
> Regards,
>
> Hervé
>
> Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
>> 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 with org.apache.maven.ara or
>> org.apache.maven.artifact.resolver.api if we compare with
>> org.apache.maven.mara to me the m in mara is redundant because we already
>> have the maven... so either if we want a short package name then `ara` is
>> better... or we want an understandable package name... same goes for
>> artifactIds
>>
>> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
>>> 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 while working in private on
>>> the
>>> topic:
>>> - Akasha https://en.wikipedia.org/wiki/Akasha
>>> - Maven Artifact Resolver API ("mara" when used as package name or
>>> artifactid
>>> or in maven-mara-provider)
>>>
>>>
>>> Does anybody have another idea?
>>> Is there a preference in the community?
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Hervé BOUTEMY <he...@free.fr>.
I like the org.apache.maven.artifact.resolver idea added to "Maven Artifact
Resolver API" description
I prepared a projection based on this idea:
http://maven.apache.org/aether-archives/aether.html
WDYT?
Regards,
Hervé
Le jeudi 28 juillet 2016 09:35:08 Stephen Connolly a écrit :
> 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 with org.apache.maven.ara or
> org.apache.maven.artifact.resolver.api if we compare with
> org.apache.maven.mara to me the m in mara is redundant because we already
> have the maven... so either if we want a short package name then `ara` is
> better... or we want an understandable package name... same goes for
> artifactIds
>
> On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
> > 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 while working in private on
> > the
> > topic:
> > - Akasha https://en.wikipedia.org/wiki/Akasha
> > - Maven Artifact Resolver API ("mara" when used as package name or
> > artifactid
> > or in maven-mara-provider)
> >
> >
> > Does anybody have another idea?
> > Is there a preference in the community?
> >
> > Regards,
> >
> > Hervé
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [DISCUSSION] finishing Aether import: help find a new name
Posted by Stephen Connolly <st...@gmail.com>.
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 with org.apache.maven.ara or
org.apache.maven.artifact.resolver.api if we compare with
org.apache.maven.mara to me the m in mara is redundant because we already
have the maven... so either if we want a short package name then `ara` is
better... or we want an understandable package name... same goes for
artifactIds
On 28 July 2016 at 08:13, Hervé BOUTEMY <he...@free.fr> wrote:
> 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 while working in private on
> the
> topic:
> - Akasha https://en.wikipedia.org/wiki/Akasha
> - Maven Artifact Resolver API ("mara" when used as package name or
> artifactid
> or in maven-mara-provider)
>
>
> Does anybody have another idea?
> Is there a preference in the community?
>
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>