Why do we require the SHA1 query to work ?
Why not use GAV first and only if no matches on that use SHA ?
…and what is special about picket box to not be resolvable without even going to remote
nexus repo instead
of just looking in available maven repos via the GAV ?
/max
On Jan 27, 2012, at 23:06, Snjezana Peco wrote:
Hello,
Now the org.jboss.jbossts:jbossjts:4.16.0.Final artifact is included in the m2e index
repository.
However, there is a problem with the org.picketbox:picketbox:4.0.6-Beta2 artifact. It
exists in the JBoss Maven repository.
The artifact is placed in the m2e indexer (see the screenshot), but a nexus sha1 query
can't find GAV for this artifact.
Test case:
- enter
https://repository.jboss.org/nexus/content/groups/public/org/picketbox/pi...
You will get sha1 for the org.picketbox:picketbox:4.0.6-Beta2 artifact
(2b969e8e524c174b510819118e283bcf9d5479e2)
- enter
https://repository.jboss.org/nexus/service/local/data_index?sha1=2b969e8e...
You will get:
<search-results>
<totalCount>0</totalCount>
<from>-1</from>
<count>-1</count>
<tooManyResults>false</tooManyResults>
<data/>
</search-results>
which is a wrong result because the artifact exists.
A GAV query returns the correct result. For instance:
https://repository.jboss.org/nexus/service/local/data_index?a=picketbox&a...
returns the correct source.
The JBoss Source Lookup plugin
(
https://community.jboss.org/community/tools/blog/2012/01/24/jboss-source-...) requires
a sha1 query.
Snjeza
Jozef Chocholáček wrote:
> I've just fired "Repair Index" command on that repository, pls check it
in few minutes. I don't see any problem in the repository's configuration, maybe
Paul could say more to the topic.
>
>
> Regards,
>
> J.Ch.
<JBossNexusPicketbox.png>_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev