Re: [DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

Konrad Windszus wrote: > > > >> Hi, > >> I think almost everything is helpful for consumers (although probably > >> needs a bit tweaking/updating). > >> The only thing I would not migrate is > >> - https://wiki.eclipse.org/Aether/New_and_Noteworthy

Re: [DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

gt; > On Wed, Apr 10, 2024 at 1:09 PM Konrad Windszus wrote: > >> Hi, >> I think almost everything is helpful for consumers (although probably >> needs a bit tweaking/updating). >> The only thing I would not migrate is >> - https://wiki.eclipse.org/Aether/New

Re: [DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

is > - https://wiki.eclipse.org/Aether/New_and_Noteworthy and > - https://wiki.eclipse.org/Aether itself > > Can we get an MD export? > Konrad > > > > > On 10. Apr 2024, at 10:21, Tamás Cservenák wrote: > > > > Howdy, > > > > We have issued https://issu

Re: [DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

Hi, I think almost everything is helpful for consumers (although probably needs a bit tweaking/updating). The only thing I would not migrate is - https://wiki.eclipse.org/Aether/New_and_Noteworthy and - https://wiki.eclipse.org/Aether itself Can we get an MD export? Konrad > On 10. Apr 2

[DISCUSS] Eclipse wiki shutting down re Aether (MRESOLVER-289)

Howdy, We have issued https://issues.apache.org/jira/browse/MRESOLVER-289 to migrate some or all of it (if we find it required). Question: WDYT? Should content on https://wiki.eclipse.org/Aether be migrated? Fully or partially? Or what exactly? For reference: "latest stable" res

[GitHub] [maven-artifact-transfer] dependabot[bot] commented on pull request #31: Bump aether-util from 1.7 to 1.13.1

dependabot[bot] commented on pull request #31: URL: https://github.com/apache/maven-artifact-transfer/pull/31#issuecomment-835426009 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR

[GitHub] [maven-artifact-transfer] asfgit closed pull request #31: Bump aether-util from 1.7 to 1.13.1

asfgit closed pull request #31: URL: https://github.com/apache/maven-artifact-transfer/pull/31 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this

[GitHub] [maven-artifact-transfer] dependabot[bot] commented on pull request #34: Bump aether-impl from 0.9.0.M2 to 1.1.0

dependabot[bot] commented on pull request #34: URL: https://github.com/apache/maven-artifact-transfer/pull/34#issuecomment-831171619 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR

[GitHub] [maven-artifact-transfer] slachiewicz closed pull request #34: Bump aether-impl from 0.9.0.M2 to 1.1.0

slachiewicz closed pull request #34: URL: https://github.com/apache/maven-artifact-transfer/pull/34 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about

[GitHub] [maven-artifact-transfer] dependabot[bot] commented on pull request #33: Bump aether-api from 1.7 to 1.13.1

dependabot[bot] commented on pull request #33: URL: https://github.com/apache/maven-artifact-transfer/pull/33#issuecomment-831171505 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR

[GitHub] [maven-artifact-transfer] slachiewicz closed pull request #33: Bump aether-api from 1.7 to 1.13.1

slachiewicz closed pull request #33: URL: https://github.com/apache/maven-artifact-transfer/pull/33 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #34: Bump aether-impl from 0.9.0.M2 to 1.1.0

dependabot[bot] opened a new pull request #34: URL: https://github.com/apache/maven-artifact-transfer/pull/34 Bumps aether-impl from 0.9.0.M2 to 1.1.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #33: Bump aether-api from 1.7 to 1.13.1

dependabot[bot] opened a new pull request #33: URL: https://github.com/apache/maven-artifact-transfer/pull/33 Bumps [aether-api](https://github.com/sonatype/sonatype-aether) from 1.7 to 1.13.1. Commits https://github.com/sonatype/sonatype-aether/commit

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #31: Bump aether-util from 1.7 to 1.13.1

dependabot[bot] opened a new pull request #31: URL: https://github.com/apache/maven-artifact-transfer/pull/31 Bumps [aether-util](https://github.com/sonatype/sonatype-aether) from 1.7 to 1.13.1. Commits https://github.com/sonatype/sonatype-aether/commit

[GitHub] [maven-artifact-transfer] asfgit closed pull request #25: Bump aether-util from 0.9.0.M2 to 1.1.0

asfgit closed pull request #25: URL: https://github.com/apache/maven-artifact-transfer/pull/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this

[GitHub] [maven-artifact-transfer] dependabot[bot] commented on pull request #25: Bump aether-util from 0.9.0.M2 to 1.1.0

dependabot[bot] commented on pull request #25: URL: https://github.com/apache/maven-artifact-transfer/pull/25#issuecomment-830804164 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR

[GitHub] [maven-artifact-transfer] dependabot[bot] commented on pull request #26: Bump aether-api from 0.9.0.M2 to 1.1.0

dependabot[bot] commented on pull request #26: URL: https://github.com/apache/maven-artifact-transfer/pull/26#issuecomment-830804047 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR

[GitHub] [maven-artifact-transfer] asfgit closed pull request #26: Bump aether-api from 0.9.0.M2 to 1.1.0

asfgit closed pull request #26: URL: https://github.com/apache/maven-artifact-transfer/pull/26 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this

[GitHub] [maven-artifact-transfer] asfgit closed pull request #29: Bump aether-impl from 1.7 to 1.13.1

asfgit closed pull request #29: URL: https://github.com/apache/maven-artifact-transfer/pull/29 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this

[GitHub] [maven-artifact-transfer] dependabot[bot] commented on pull request #29: Bump aether-impl from 1.7 to 1.13.1

dependabot[bot] commented on pull request #29: URL: https://github.com/apache/maven-artifact-transfer/pull/29#issuecomment-830803994 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #29: Bump aether-impl from 1.7 to 1.13.1

dependabot[bot] opened a new pull request #29: URL: https://github.com/apache/maven-artifact-transfer/pull/29 Bumps [aether-impl](https://github.com/sonatype/sonatype-aether) from 1.7 to 1.13.1. Commits https://github.com/sonatype/sonatype-aether/commit

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #26: Bump aether-api from 0.9.0.M2 to 1.1.0

dependabot[bot] opened a new pull request #26: URL: https://github.com/apache/maven-artifact-transfer/pull/26 Bumps aether-api from 0.9.0.M2 to 1.1.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #25: Bump aether-util from 0.9.0.M2 to 1.1.0

dependabot[bot] opened a new pull request #25: URL: https://github.com/apache/maven-artifact-transfer/pull/25 Bumps aether-util from 0.9.0.M2 to 1.1.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name

Re: Maven-enforcer-plugin's use of aether-util in transitive dependency

Hi Enrico, I see you successfully merged the pull request. Thank you for taking care of this! Regards, Tomo On Wed, May 15, 2019 at 4:29 AM Enrico Olivelli wrote: > Thanks Tomo for the heads up. > I will move the patch forward. > > > Enrico > > Il giorno mar 14 mag 2019 alle ore 22:08 Tomo

Re: Maven-enforcer-plugin's use of aether-util in transitive dependency

Thanks Tomo for the heads up. I will move the patch forward. Enrico Il giorno mar 14 mag 2019 alle ore 22:08 Tomo Suzuki ha scritto: > Hi Enrico, > > The PR https://github.com/apache/maven-enforcer/pull/52 has been approved > (Thanks!) but not merged yet. > Is this something you can take

Re: Maven-enforcer-plugin's use of aether-util in transitive dependency

Hi Enrico, The PR https://github.com/apache/maven-enforcer/pull/52 has been approved (Thanks!) but not merged yet. Is this something you can take care of, or should I take any action? Regards, Tomo *From: *Tomo Suzuki *Date: *Mon, Mar 18, 2019 at 12:15 AM *To: *Maven Developers List Enrico,

Avoiding to shade aether classes in shared/artifact-transfer

Hi! I resumed work on MSHARED-801 and I saw that for collecting dependencies I need access to many aether classes. The current strategy is to shade the necessary classes into the artifact-transfer jar file but this won't work for collecting because it will actually force to use that classes

Re: Maven-enforcer-plugin's use of aether-util in transitive dependency

Enrico, Created the PR. https://github.com/apache/maven-enforcer/pull/52 Regards, Tomo On Sun, Mar 17, 2019 at 5:17 PM Enrico Olivelli wrote: > Awesome > Let's see the PR > > Thanks > Enrico > > Il mer 13 mar 2019, 22:19 Tomo Suzuki ha > scritto: > > > Hi Maven developers, > > (following

Re: Maven-enforcer-plugin's use of aether-util in transitive dependency

Awesome Let's see the PR Thanks Enrico Il mer 13 mar 2019, 22:19 Tomo Suzuki ha scritto: > Hi Maven developers, > (following "Contributing" section of maven-enforcer-plugin > ) > > I'm thinking to raise a PR to fix an issue below, so that

Maven-enforcer-plugin's use of aether-util in transitive dependency

Hi Maven developers, (following "Contributing" section of maven-enforcer-plugin ) I'm thinking to raise a PR to fix an issue below, so that maven-enforcer-plugin can work with maven-resolver-util without explicit "exclusion" element. Let me

Re: Packaging from Aether

Found it. The type was hiding in the properties. That is, String type = artifact.getProperty(ArtifactProperties.TYPE, "jar"); On Thu, Sep 20, 2018 at 4:05 PM, Elliotte Rusty Harold wrote: > With Eclipse Aether I can read a pom and gather information in the >

Re: Packaging from Aether

ives you informations about default types. I'm not really using Maven core. I have my own Java code that does things Maven doesn't do. It relies on Aether to parse the pom.xml files. I could just parse XML directly, but Aether handles property resolution, artifact resolution, parent POMs, BOMs, fin

Re: Packaging from Aether

On Thu, Sep 20, 2018 at 10:34 PM, Lennart Jörelid wrote: > Hello Elliotte, > > I usually use the depends-maven-plugin, which collects information about > dependencies within a property file. > The data format within this property file (typically placed within >

Re: Packaging from Aether

2018 22:05:42 Objet: Packaging from Aether With Eclipse Aether I can read a pom and gather information in the form of import org.eclipse.aether.graph.Dependency and org.eclipse.aether.artifact.Artifact objects. Is there some way from these or related objects I can gather the information about the packagi

Re: Packaging from Aether

and classification can be read as the property [groupID]/[artifactID]/type and .../classification If this meet your needs, you don't need to fiddle around with Aether to get the job done. org.hamcrest/hamcrest-core/version = 1.3 org.hamcrest/hamcrest-core/type = jar org.hamcrest/hamcrest-core/scope = test

Packaging from Aether

With Eclipse Aether I can read a pom and gather information in the form of import org.eclipse.aether.graph.Dependency and org.eclipse.aether.artifact.Artifact objects. Is there some way from these or related objects I can gather the information about the packaging of the dependency

Re: What became of Aether/Ant tasks...

they are waiting for love, for somebody to really test and release I did the integration in our Maven structure (with git, site [1], CI) while I was migrating Aether to Maven Artifact Resolver, checking that the build passes: but nobody seemed interested (until now?) to test it and have

Re: What became of Aether/Ant tasks...

https://github.com/apache/maven-resolver see ant-tasks branch. On 24 August 2017 at 12:45, Mark Derricutt <m...@talios.com> wrote: > Hey all, > > Now that Aether has moved it's way back to Apache as the Maven Resolver, > what's become of the Aether/Ant taks? > > https:/

What became of Aether/Ant tasks...

Hey all, Now that Aether has moved it's way back to Apache as the Maven Resolver, what's become of the Aether/Ant taks? https://wiki.eclipse.org/Aether/Ant_Tasks Mark --- "The ease with which a change can be implemented has no relevance at all to whether it is the right change for the

Re: extensions.xml (Re: [4/7] maven git commit: [MNG-6110] Upgrade Aether to Maven Resolver 1.2)

in maven core and in plugin realm. I don't remember why we need to filter org.sonatype.aether, but that aether version cannot be used with maven core, so at very least the filter will force earlier ClassNotFoundError, which I believe is useful. [1] http://takari.io/book/91-maven-classloading.html

Re: future of aether

migration. But I dont know where they would be. Once the migration is done the Eclipse site should probably be updated or use a redirector.. Manfred domi wrote on 2016-12-12 01:44: Hi, is there any official statement about the future of Aether published somewhere? I just noticed that Spr

Re: maven-aether-provider renamed to maven-resolver-provider.

Am 2016-12-11 um 23:43 schrieb Christian Schulte: Do we want to deploy a 'maven-aether-provider' relocating to 'maven-resolver-provider'? Since we change the groupId already, why not? Michael - To unsubscribe, e-mail: dev

Re: future of aether

there any official statement about the future of Aether published > somewhere? > I just noticed that Spring plans to use it in one of there upcoming releases: > https://github.com/spring-projects/spring-boot/commit/1cd781b2426f1b63b80d990e19d7d7c6a6fd735a > <https://github.com/spr

future of aether

Hi, is there any official statement about the future of Aether published somewhere? I just noticed that Spring plans to use it in one of there upcoming releases: https://github.com/spring-projects/spring-boot/commit/1cd781b2426f1b63b80d990e19d7d7c6a6fd735a <https://github.com/spring-proje

maven-aether-provider renamed to maven-resolver-provider.

Do we want to deploy a 'maven-aether-provider' relocating to 'maven-resolver-provider'? Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

extensions.xml (Re: [4/7] maven git commit: [MNG-6110] Upgrade Aether to Maven Resolver 1.2)

llection > @@ -134,7 +134,7 @@ under the License. > org.sonatype.sisu:sisu-inject-plexus > > org.eclipse.sisu:org.eclipse.sisu.plexus > org.apache.maven:maven-artifact > - > org.apache.maven:maven-aether-provider > + > org.apache.maven:maven-resolver-provider >

[GitHub] maven pull request #95: [MNG-6110] updated Aether to Maven Resolver 1.2.0-SN...

Github user asfgit closed the pull request at: https://github.com/apache/maven/pull/95 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] maven issue #95: [MNG-6110] updated Aether to Maven Resolver 1.2.0-SNAPSHOT

Github user michael-o commented on the issue: https://github.com/apache/maven/pull/95 > Should maven-aether-provider be renamed? From my POM, yes, but in a separate ticket. --- If your project is set up for it, you can reply to this email and have your reply appear on Git

[GitHub] maven pull request #95: [MNG-6110] updated Aether to Maven Resolver 1.2.0-SN...

GitHub user hwellmann opened a pull request: https://github.com/apache/maven/pull/95 [MNG-6110] updated Aether to Maven Resolver 1.2.0-SNAPSHOT TODO: * Upgrade to 1.2.0 once it's released. * Should `maven-aether-provider` be renamed? * Update Javadoc link for Maven

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

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/aet

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

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, Mich

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

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:

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

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

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

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-...?

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

;> >>> 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

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

gt; > 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 updat

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

yl <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

lexus, 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-unsubscr...@maven.apache.org For additional commands,

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

+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.

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

... 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

AIR could be something Adobe might have a problem with ... Chris Von: Jörg Schaible <joerg.schai...@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 nam

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. > >

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

Am 08/05/16 um 01:21 schrieb Gary Gregory: > On Thu, Aug 4, 2016 at 3:24 PM, Christian Schulte 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

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

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

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

i 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 <c...@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 a

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

Eclipse owns the Aether name. We cannot use the name Aether. On 5 August 2016 at 05:14, Uwe Barthel <bart...@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.a

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

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-unsubscr...@maven.apache.org For additional

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

On Thu, Aug 4, 2016 at 3:24 PM, Christian Schulte 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

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

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

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

On Thu, Aug 4, 2016 at 2:53 PM, Christian Schulte <c...@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 >

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

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

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

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 <c...@schulte.it> wrote: > > Am 08

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

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" <c...@schulte.it> À: "Maven Developers List" <

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

original - De: "Michael Osipov" <micha...@apache.org> À: "Maven Developers List" <dev@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 r

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

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" resol

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

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

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

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

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

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.

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

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

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

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 >

Re: [DISCUSSION] finishing Aether import: help find a new 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

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

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 <rfscho...@apache.org> wrote: > It is all ab

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

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

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

en 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/) >> >> Ma

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

en 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 Sch

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

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

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

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

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

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

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-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

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

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

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

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

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

e in a few days to match http://maven.apache.org/aether-archives/aether.html Regards, Hervé - Mail original - De: "Michael Osipov" <micha...@apache.org> À: "Maven Developers List" <dev@maven.apache.org> Envoyé: Samedi 30 Juillet 2016 00:24:08 Objet: Re: [DISCUSSION] f

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

> 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 i

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

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" <micha...@apache.o

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

fact 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.ap

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

to match http://maven.apache.org/aether-archives/aether.html Regards, Hervé - Mail original - De: "Michael Osipov" <micha...@apache.org> À: "Maven Developers List" <dev@maven.apache.org> Envoyé: Samedi 30 Juillet 2016 00:24:08 Objet: Re: [DISCUSSION] finishin

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

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

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

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,

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 ha

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

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 :

  1   2   3   4   5   6   >