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" <[email protected]> À: "Maven Developers List" <[email protected]> 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, [email protected] 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" <[email protected]> >>> À: "Maven Developers List" <[email protected]> >>> 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 <[email protected]> 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: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder, Takari and Apache Maven >> http://twitter.com/jvanzyl >> http://twitter.com/takari_io >> --------------------------------------------------------- >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
