Re: [MDEP-269] please review

This is out of scope for the dependency plugin. It's like the site plugin growing out of control. The dependency plugin is manipulating dependencies not finding them and doing migrations. On Jun 21, 2010, at 10:48 AM, nicolas de loof wrote: > True, > > I'll commit the REST-based code in maven-

Re: [MDEP-269] please review

True, I'll commit the REST-based code in maven-dependency-plugin, as it is easier to configure for any other repository manager, and try to prepare a contrib to nexus-maven-plugin Cheers, Nicolas 2010/6/21 Brian Fox > If you're using the nexus api, then this belongs in the > nexus-maven-plug

Re: [MDEP-269] please review

If you're using the nexus api, then this belongs in the nexus-maven-plugin, not the maven-dependency-plugin. On Mon, Jun 21, 2010 at 8:39 AM, nicolas de loof wrote: > I tried to write an alternate implementation of MDEP-269 using nexus indexer > API, based on samples found on sonatype blog. > > I

Re: [MDEP-269] please review

> > I get an error when running the indexUpdater > : java.lang.ClassNotFoundException: > org.eclipse.jetty.client.security.Authorization - I can't find a dependency > to this eclipse plugin in nexus-indexer POM.xml > > > This one is solved, I wasn't looking at the correct POM :-/ sory Nicolas

Re: [MDEP-269] please review

I tried to write an alternate implementation of MDEP-269 using nexus indexer API, based on samples found on sonatype blog. I got some few issues : I had to add sonatype forge as repository to resolve dependencies, not really pleasant as the maven plugin is expected to build using central repo. I

Re: [MDEP-269] please review

Well, we had an issue: https://issues.sonatype.org/browse/NEXUS-644 but it was fixed more then a year ago... maybe he suffered from that one? But index downloaded from central was never suffering from this issue (it is not a Nexus instance, and Central would not be a group anyway). Use the lates

Re: [MDEP-269] please review

I discussed with the author of alf-maven-osecm (that suggested me this feature) and he reported me he first tried to use the repo index but didn't find the hash in it. I've not tried by myslef. If hash is included, please close my Jira issue on Nexus and I'll double check this. 2010/6/18 Tamás Cse

Re: [MDEP-269] please review

I don't get it, what do you mean by "repository index generated by Nexus ... doesn't include the artifact hash"? What makes you think hash is not on the index? Thanks, ~t~ On Fri, Jun 18, 2010 at 11:52 AM, nicolas de loof wrote: > Hi folks, > > I'm working on MDEP-269

[MDEP-269] please review

Hi folks, I'm working on MDEP-269 - convert a legacy lib/*.jar to maven I've attached a patch to Jira as I'd like your opinion on the way to support this use case. My patch uses Nexus REST API to query the repository manager for artifacts based on local