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 Cservenák <ta...@cservenak.net> > 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 > <nicolas.del...@gmail.com>wrote: > > > Hi folks, > > > > I'm working on MDEP-269 <http://jira.codehaus.org/browse/MDEP-269> - > > convert > > a legacy lib/*.jar to maven <dependencies> > > 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 files SHA1 hash. > > The query URL is configurable, and the Xpath expression to extract data > > should also, so that a non-nexus repository manager that provides > > comparable > > feature may be user. > > > > Maybe there is more performant/portable way to do this, > > for example using repository index generated by Nexus (not sure if other > > repository manager do the same) but this one doesn't include the > artifacts > > hash yet (NEXUS-3596 <http://issues.sonatype.org/browse/NEXUS-3596>) > > > > WDYT ? > > > > Nicolas > > >
