Here is the email I received from them about it.
Hi Jordan, … > Does anyone have any suggestions for me to resolve this or is there > another email list where this question would fit better? sadly, Aether has left Eclipse for Apache, to be developed there in closer collaboration with the Maven core. See [1] here for the details. I am not aware of an aether-users list at Apache, so I would suggest asking on [email protected] or maybe [email protected]. Neither list seems to be a perfect fit though, as you are neither end user or developer of Maven itself. Anyway, it would be great if you could reply which list ultimately answered your question, so future developers can find the answer in the archives. Hope that helps. Andreas [1] <https://projects.eclipse.org/projects/technology.aether/reviews/termination-review> -- Codetrails GmbH The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Phone: +49-6151-276-7092 Mobile: +49-170-811-3791 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 _______________________________________________ aether-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/aether-users On 7/19/16, 10:27 AM, "Jordan Lewis" <[email protected]> wrote: >Correct. However, I used that mailing list that you listed and they pointed me >to your list because you have taken the project over, correct? > >Jordan > > > > >On 7/19/16, 10:25 AM, "Ron Wheeler" <[email protected]> wrote: > >>Yes. >>It does seem that you do not have a Maven problem but have an Aether problem >>https://dev.eclipse.org/mailman/listinfo/aether-users >> >>Ron >> >>On 19/07/2016 9:54 AM, Jordan Lewis wrote: >>> Does that all make sense or do you need anything else to make it clearer? >>> >>> Thanks, >>> Jordan >>> >>> >>> >>> >>> On 7/18/16, 3:56 PM, "Jordan Lewis" <[email protected]> wrote: >>> >>>> The plug-in does have a configuration that tries to ignore the local repo, >>>> but whenever it resolves an artifact using system.resolveArtifact(..), it >>>> always checks the local repo first. >>>> >>>> What is the code to ignore the local repo? Or is there some code that >>>> could try to resolve an artifact from a specific repo? >>>> >>>> Thanks, >>>> Jordan >>>> >>>> >>>> >>>> >>>> On 7/18/16, 3:22 PM, "Ron Wheeler" <[email protected]> wrote: >>>> >>>>> Can you just patch the existing plug-in to create a new plug-in that >>>>> ignores the local repo? >>>>> Or add a configuration flag to ignore the local repo and submit your >>>>> improvement as an enhancement. >>>>> >>>>> >>>>> Ron >>>>> >>>>> On 18/07/2016 2:29 PM, Jordan Lewis wrote: >>>>>> Nexus. >>>>>> >>>>>> Our remote Nexus repository is available to others, but my local >>>>>> repository is obviously not. So whenever I generate the index file, I >>>>>> need to make sure that my local paths to the artifacts are never used >>>>>> which they are if the artifact can be resolved both locally and >>>>>> remotely. I need it to only resolve from the remote repository. >>>>>> >>>>>> Thanks, >>>>>> Jordan >>>>>> >>>>>> >>>>>> >>>>>> On 7/18/16, 2:21 PM, "Ron Wheeler" <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> What repo are you using locally - Nexus, Artifactory,....? >>>>>>> Why is it not available to others? >>>>>>> >>>>>>> Ron >>>>>>> >>>>>>> On 18/07/2016 2:04 PM, Jordan Lewis wrote: >>>>>>>> Is this question in the wrong mailing list? Is there a specific Aether >>>>>>>> mailing list? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Jordan >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 7/14/16, 9:41 AM, "Jordan Lewis" <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> This is a question about the Aether API. I’m working on building an >>>>>>>>> index file which will point to the resolved artifact using >>>>>>>>> bnd-indexer-maven-plugin. The indexer has an option to forbid the use >>>>>>>>> of local URIs and that works fine as long as I don’t have the >>>>>>>>> artifact in my local repository. I need the artifact to resolve to >>>>>>>>> the remote repository so that anyone can use this index file and it >>>>>>>>> won’t depend on my local repository. If the artifact is in my local >>>>>>>>> repository though, it resolves to that artifact whenever the indexer >>>>>>>>> code call system.resolveArtifact(..). I can get around this by >>>>>>>>> clearing my local repository and then the artifact will resolve to >>>>>>>>> the remote repository location just fine. I did some digging and it >>>>>>>>> appears like you are always checking the localRepositoryManager first >>>>>>>>> and then you check remote repositories. >>>>>>>>> >>>>>>>>> Is there a way to make it ignore the local repository resolution or >>>>>>>>> set a repository priority order where it would check the remote >>>>>>>>> repository before the local repository? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Jordan >>>>>>>>> >> >> >>-- >>Ron Wheeler >>President >>Artifact Software Inc >>email: [email protected] >>skype: ronaldmwheeler >>phone: 866-970-2435, ext 102 >> >> >>--------------------------------------------------------------------- >>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]
