Max Rydahl Andersen wrote:
https://issues.jboss.org/browse/PLINK is picket link jira.
If the metadata is missing they must have deliberately removed this from their build.
when you open a bug add me to watch or simply paste the link here.
https://issues.jboss.org/browse/PLINK-54
>>>> …and what is special about picket box to not be
resolvable without even going to remote
jboss.org nexus repo instead
>>>> of just looking in available maven repos via the GAV ?
>>>>
>>>>
>>>>
>>> The SHA1 query works correctly for all archives I have tried, but
picketbox*.jar (I have also tested Tomcat 7.0.25 and Glassfish 3.1.1). I suppose that
there is some problem with a Nexus indexer.
>>>
>>>
>> I would really like to know which jar's are missing info to not know the
GAV's.
>>
>>
> junit, osgi, jdom, activation ...
> However, we can find GAV for all of these archives using the SHA1 query.
> The org.osgi:org.osgi.core artifact doesn't have source in the JBoss
> Maven repository. The Sonatype Repository contains it.
>
Yes and when you use EAP there won't be any repo index available to lookup in so that
won't work there either.
Thus its fine we got this SHA1 as a "backup" but I would say we should show a
dialog saying we could not find
this based on raw metadata, and ask if user is ok looking through the various known nexus
repositories.
(and provide a "Remember my choice" option)
The user already has preferences to enable/disable nexus repositories.
We could also log sha1 queries that don't return any result. m2w also
log a warning when it can find source.
That way we exposed and get to know which artifacts has issues and
can report them accordingly.
/max
> Snjeza
>
>
>> /max
>>
>>
>>
>>> Snjeza
>>>
>>>
>>>> /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
>>>>>
>>>>>
>>>>>
>>>> /max
>>>>
http://about.me/maxandersen
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>> /max
>>
http://about.me/maxandersen
>>
>>
>>
>>
>>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
/max
http://about.me/maxandersen