Re: Resolving an Artifact from Remote Repository instead of Local

Took a bit of circling around but it seems like a simple solution was found in the end! I am kind of surprised that no one popped up with a solution for OSGi. Not a rare technology. Did you look at the maven-bundle-plugin? http://felix.apache.org/components/bundle-plugin/index.html

Re: Resolving an Artifact from Remote Repository instead of Local

Awesome. That should work for my case. Thanks! Jordan On 7/21/16, 3:02 PM, "Ron Wheeler" wrote: >http://stackoverflow.com/questions/9123004/maven-is-it-possible-to-override-location-of-local-repository-via-the-use-of-co >Even easier - run-time argument to

Re: Resolving an Artifact from Remote Repository instead of Local

http://stackoverflow.com/questions/9123004/maven-is-it-possible-to-override-location-of-local-repository-via-the-use-of-co Even easier - run-time argument to Maven On 21/07/2016 2:49 PM, Jordan Lewis wrote: Still not sure why anyone would need an index file. What are they going to use it for?

Re: Resolving an Artifact from Remote Repository instead of Local

>Still not sure why anyone would need an index file. What are they going >to use it for? We have an OSGi runtime and use OBR to deploy our bundles. OBR needs artifacts to be indexed so it can find them to satisfy the dependencies of our bundles. That is what I’m building the index file for. If

Re: Resolving an Artifact from Remote Repository instead of Local

Still not sure why anyone would need an index file. What are they going to use it for? Is there some way to override system.resolveArtifact's understanding of where to find the local repo. Then you could give it an empty directory and your problem would be solved without touching your "real"

Re: Resolving an Artifact from Remote Repository instead of Local

>Looks like it might be easier to just delete your local repo! I know that this approach works. It’s just a bit inconvenient to have to do that. >Perhaps you might want to revisit your ultimate goal. >Describe the use that people will make of the index and see if anyone >has a different way

Re: Resolving an Artifact from Remote Repository instead of Local

Looks like it might be easier to just delete your local repo! Perhaps you might want to revisit your ultimate goal. Describe the use that people will make of the index and see if anyone has a different way to get what you want. Why is your need so different from the normal case that no one

Re: Resolving an Artifact from Remote Repository instead of Local

Is this, , still the code base? I could make a pull request that would show exactly the part I’m talking about with a possible solution. Thanks, Jordan On 7/20/16, 1:53 PM, "Jordan Lewis" wrote: >Any update on what

Re: Resolving an Artifact from Remote Repository instead of Local

Any update on what mailing list I should be using? Jordan On 7/19/16, 2:26 PM, "Jordan Lewis" wrote: >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

Re: Resolving an Artifact from Remote Repository instead of Local

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

Re: Resolving an Artifact from Remote Repository instead of Local

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" wrote: >Yes. >It does seem that you do not have a Maven problem but have

Re: Resolving an Artifact from Remote Repository instead of Local

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

Re: Resolving an Artifact from Remote Repository instead of Local

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" wrote: >The plug-in does have a configuration that tries to ignore the local repo, but >whenever it resolves an artifact using

Re: Resolving an Artifact from Remote Repository instead of Local

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

Re: Resolving an Artifact from Remote Repository instead of Local

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

Re: Resolving an Artifact from Remote Repository instead of Local

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

Re: Resolving an Artifact from Remote Repository instead of Local

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"

Re: Resolving an Artifact from Remote Repository instead of Local

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" wrote: >Hi All, > >This is a question about the Aether API. I’m working on building an index file >which will point to the

Resolving an Artifact from Remote Repository instead of Local

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