The JBoss.org team is now responsible for Nexus. Nexus is supposed to update the index immediately when new artifacts are deployed, but maybe this isn't working correctly. On 01/16/2012 06:35 AM, Max Rydahl Andersen wrote: >> I have been working on https://issues.jboss.org/browse/JBIDE-9309. >> The Source Lookup plugin uses the Nexus indexer to find a source file for a maven artifact. >> The problem happens when I try to debug JBoss AS 7.1 CR1 (or CR1b). >> JBoss AS 7.1.CR1 contains the jbossjts-4.16.0.Final.jar module (the org.jboss.jbossts:jbossjts:4.16.0.Final maven artifact). This artifact exists in the JBoss Maven repository (https://repository.jboss.org/nexus/content/groups/public-jboss), but the Nexus indexer includes this artifact up to version 4.16.0.Beta1. See the attached screenshot. >> There are several jars that aren't included in the indexer. It is possible that m2e doesn't read the indexer properly. >> >> How frequently does this indexer refresh? >> > Are you asking how often jboss.org refresh their index or how often m2e refresh their index? > > I assume your are asking about jboss.org's ? > > Thus i've cc'ed in Paul Gier which should know the answer to this. > > Paul - how often do we run the jboss repo indexer? > > It's used by tools to lookup artifacts thus when they aren't present then things aren't found… > > /max > http://about.me/maxandersen > > > >

Is this as simple as the index used by m2e not being up-to-date? Please try updating the index within Eclipse (Maven Repositories, locate the JBoss repository, right-click, update index or rebuild index). By default, m2e is set to update indexes on every start, so the above may not solve your problem. (I usually disable this to save time and bandwidth). Just an idea. Best, Rob ----- Original Message ----- > I am not sure if the problem is related to m2e or JBoss Nexus > Indexer. > m2e can't find the org.jboss.jbossts:jbossjts:4.16.0.Final artifact . > Does this artifact exist in the JBoss Nexus indexer? > > Snjeza > > Paul Gier wrote: > >> The JBoss.org team is now responsible for Nexus. Nexus is supposed >> to >> update the index immediately when new artifacts are deployed, but >> maybe >> this isn't working correctly. >> >> On 01/16/2012 06:35 AM, Max Rydahl Andersen wrote: >> >> >>>> I have been working on >>>> https://issues.jboss.org/browse/JBIDE-9309. >>>> The Source Lookup plugin uses the Nexus indexer to find a source >>>> file for a maven artifact. >>>> The problem happens when I try to debug JBoss AS 7.1 CR1 (or >>>> CR1b). >>>> JBoss AS 7.1.CR1 contains the jbossjts-4.16.0.Final.jar module >>>> (the org.jboss.jbossts:jbossjts:4.16.0.Final maven artifact). >>>> This artifact exists in the JBoss Maven repository >>>> (https://repository.jboss.org/nexus/content/groups/public-jboss), >>>> but the Nexus indexer includes this artifact up to version >>>> 4.16.0.Beta1. See the attached screenshot. >>>> There are several jars that aren't included in the indexer. It is >>>> possible that m2e doesn't read the indexer properly. >>>> >>>> How frequently does this indexer refresh? >>>> >>>> >>> Are you asking how often jboss.org refresh their index or how >>> often m2e refresh their index? >>> >>> I assume your are asking about jboss.org's ? >>> >>> Thus i've cc'ed in Paul Gier which should know the answer to this. >>> >>> Paul - how often do we run the jboss repo indexer? >>> >>> It's used by tools to lookup artifacts thus when they aren't >>> present then things aren't found… >>> >>> /max >>> http://about.me/maxandersen >>> >>> >>> >>> >>> > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > >

Hi Jozef, Please can you take a look at this issue with Nexus at jboss.org related to indexing. thanks, Mark On 16 Jan 2012, at 20:20, Snjezana Peco wrote: > I have updated the indexer from the Maven Repositories view, tested > the issue with a new Eclipse installation ... See the screenshot. > m2e finds org.jboss.jbossts:jbossjts:4.16.0.Beta1, but doesn't find > org.jboss.jbossts:jbossjts:4.16.0.Final. > That's why I suppose that the issue is related to the JBoss Nexus > Indexer. It might also be that there is a bug in m2e. > > Snjeza > > Rob Cernich wrote: >> Is this as simple as the index used by m2e not being up-to-date? >> Please try updating the index within Eclipse (Maven Repositories, >> locate the JBoss repository, right-click, update index or rebuild >> index). >> >> By default, m2e is set to update indexes on every start, so the >> above may not solve your problem. (I usually disable this to save >> time and bandwidth). >> >> Just an idea. >> >> Best, >> Rob >> >> ----- Original Message ----- >> >>> I am not sure if the problem is related to m2e or JBoss Nexus >>> Indexer. >>> m2e can't find the org.jboss.jbossts:jbossjts:4.16.0.Final artifact . >>> Does this artifact exist in the JBoss Nexus indexer? >>> >>> Snjeza >>> >>> Paul Gier wrote: >>> >>>> The JBoss.org team is now responsible for Nexus. Nexus is supposed >>>> to >>>> update the index immediately when new artifacts are deployed, but >>>> maybe >>>> this isn't working correctly. >>>> >>>> On 01/16/2012 06:35 AM, Max Rydahl Andersen wrote: >>>> >>>>>> I have been working on >>>>>> https://issues.jboss.org/browse/JBIDE-9309. >>>>>> The Source Lookup plugin uses the Nexus indexer to find a source >>>>>> file for a maven artifact. >>>>>> The problem happens when I try to debug JBoss AS 7.1 CR1 (or >>>>>> CR1b). >>>>>> JBoss AS 7.1.CR1 contains the jbossjts-4.16.0.Final.jar module >>>>>> (the org.jboss.jbossts:jbossjts:4.16.0.Final maven artifact). >>>>>> This artifact exists in the JBoss Maven repository >>>>>> (https://repository.jboss.org/nexus/content/groups/public-jboss), >>>>>> but the Nexus indexer includes this artifact up to version >>>>>> 4.16.0.Beta1. See the attached screenshot. >>>>>> There are several jars that aren't included in the indexer. It is >>>>>> possible that m2e doesn't read the indexer properly. >>>>>> >>>>>> How frequently does this indexer refresh? >>>>>> >>>>> Are you asking how often jboss.org refresh their index or how >>>>> often m2e refresh their index? >>>>> >>>>> I assume your are asking about jboss.org's ? >>>>> >>>>> Thus i've cc'ed in Paul Gier which should know the answer to this. >>>>> >>>>> Paul - how often do we run the jboss repo indexer? >>>>> >>>>> It's used by tools to lookup artifacts thus when they aren't >>>>> present then things aren't found… >>>>> >>>>> /max >>>>> http://about.me/maxandersen >>>>> >>>>> >>>>> >>>>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> > > <MavenRepositories.png> Mark Newton JBoss Community Lead Mobile: +41 7657 47730 Office: +41 41 760 4636 Email: mnewton(a)redhat.com

It seems JBoss Nexus is distributing a stale index. When I look at the m2e's nexus-maven-repository-index.properties for https://repository.jboss.org/nexus/content/repositories/releases/, there's a nexus.index.timestamp=20111215014501.578 +0000 so it seems it hasn't been updated for more than a month. JBoss JTS was uploaded to Nexus on the 19th of december, that explains why it's missing in m2e. Regards, Fred Bricon Le 19/01/2012 20:47, Snjezana Peco a écrit : > In the meantime, I checked the JBoss Nexus repository. The issue isn't > related to the JBoss Nexus indexer, but to m2e. Will try to make a > workaround. > > Thanks, > Snjeza > > Mark Newton wrote: >> Hi Jozef, >> >> Please can you take a look at this issue with Nexus at jboss.org >> related to indexing. >> >> thanks, >> >> Mark >> >> >> On 16 Jan 2012, at 20:20, Snjezana Peco wrote: >> >>> I have updated the indexer from the Maven Repositories view, tested >>> the issue with a new Eclipse installation ... See the screenshot. >>> m2e finds org.jboss.jbossts:jbossjts:4.16.0.Beta1, but doesn't find >>> org.jboss.jbossts:jbossjts:4.16.0.Final. >>> That's why I suppose that the issue is related to the JBoss Nexus >>> Indexer. It might also be that there is a bug in m2e. >>> >>> Snjeza >>> >>> Rob Cernich wrote: >>>> Is this as simple as the index used by m2e not being up-to-date? >>>> Please try updating the index within Eclipse (Maven Repositories, >>>> locate the JBoss repository, right-click, update index or rebuild >>>> index). >>>> >>>> By default, m2e is set to update indexes on every start, so the >>>> above may not solve your problem. (I usually disable this to save >>>> time and bandwidth). >>>> >>>> Just an idea. >>>> >>>> Best, >>>> Rob >>>> >>>> ----- Original Message ----- >>>> >>>>> I am not sure if the problem is related to m2e or JBoss Nexus >>>>> Indexer. >>>>> m2e can't find the org.jboss.jbossts:jbossjts:4.16.0.Final artifact . >>>>> Does this artifact exist in the JBoss Nexus indexer? >>>>> >>>>> Snjeza >>>>> >>>>> Paul Gier wrote: >>>>> >>>>>> The JBoss.org team is now responsible for Nexus. Nexus is supposed >>>>>> to >>>>>> update the index immediately when new artifacts are deployed, but >>>>>> maybe >>>>>> this isn't working correctly. >>>>>> >>>>>> On 01/16/2012 06:35 AM, Max Rydahl Andersen wrote: >>>>>> >>>>>>>> I have been working on >>>>>>>> https://issues.jboss.org/browse/JBIDE-9309. >>>>>>>> The Source Lookup plugin uses the Nexus indexer to find a source >>>>>>>> file for a maven artifact. >>>>>>>> The problem happens when I try to debug JBoss AS 7.1 CR1 (or >>>>>>>> CR1b). >>>>>>>> JBoss AS 7.1.CR1 contains the jbossjts-4.16.0.Final.jar module >>>>>>>> (the org.jboss.jbossts:jbossjts:4.16.0.Final maven artifact). >>>>>>>> This artifact exists in the JBoss Maven repository >>>>>>>> (https://repository.jboss.org/nexus/content/groups/public-jboss), >>>>>>>> but the Nexus indexer includes this artifact up to version >>>>>>>> 4.16.0.Beta1. See the attached screenshot. >>>>>>>> There are several jars that aren't included in the indexer. It is >>>>>>>> possible that m2e doesn't read the indexer properly. >>>>>>>> >>>>>>>> How frequently does this indexer refresh? >>>>>>>> >>>>>>> Are you asking how often jboss.org refresh their index or how >>>>>>> often m2e refresh their index? >>>>>>> >>>>>>> I assume your are asking about jboss.org's ? >>>>>>> >>>>>>> Thus i've cc'ed in Paul Gier which should know the answer to this. >>>>>>> >>>>>>> Paul - how often do we run the jboss repo indexer? >>>>>>> >>>>>>> It's used by tools to lookup artifacts thus when they aren't >>>>>>> present then things aren't found… >>>>>>> >>>>>>> /max >>>>>>> http://about.me/maxandersen >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> >>> <MavenRepositories.png> >> Mark Newton >> JBoss Community Lead >> Mobile: +41 7657 47730 >> Office: +41 41 760 4636 >> Email: mnewton(a)redhat.com >> > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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 Rydahl Andersen wrote: > Why do we require the SHA1 query to work ? > > Why not use GAV first and only if no matches on that use SHA ? We don't know GAV and have to search for it using the SHA1 query. > …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. 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 > > >

Rebuilding index doesn't help. You can try the following query: https://repository.jboss.org/nexus/service/local/data_index?sha1=2b969e8e... It should return the GAV of the org.picketbox:picketbox:4.0.6-Beta2 artifact.\

Snjeza Jozef Chocholáček wrote: > I've started index rebuild for the repository, should be fixed in few > minutes. > > J.Ch. > > On 01/30/2012 02:19 PM, Snjezana Peco wrote: >> Max Rydahl Andersen wrote: >>> Why do we require the SHA1 query to work ? >>> >>> Why not use GAV first and only if no matches on that use SHA ? >> >> We don't know GAV and have to search for it using the SHA1 query. >> >>> …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. >> >> 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 >>> >>> >>> >> > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

>> Why do we require the SHA1 query to work ? >> >> Why not use GAV first and only if no matches on that use SHA ? >> >> > We don't know GAV and have to search for it using the SHA1 query. > because picket link jar doesn't include the maven info in META-INF content ?

This isn't really critical for us to support if they don't - it's nice, but not critical. Should open bug against picket link if this is the case.

>> …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.

/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

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.

>>>> …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)

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