Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 358034

Summary: Adding maven central as repository to an aggregation does not complete
Product: [Technology] CBI Reporter: Lothar Werzinger <lothar>
Component: CBI p2 Repository AggregatorAssignee: CBI Inbox <cbi-inbox>
Status: CLOSED WONTFIX QA Contact: David Williams <david_williams>
Severity: major    
Priority: P3 CC: frederic.gurr, lists, thomas
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
the b3 aggregation file to reproduce the problem
none
screenshot showing bundle artifact in maven repo none

Description Lothar Werzinger CLA 2011-09-18 17:51:06 EDT 
Build Identifier: 

Hi,

I am trying to do an aggregation where I want to get a couple bundles from maven central.

Eclipse starts a job called "Loading maven2:http://repo1.maven.org/maven2" That does not complete in a reasonable time (left it running over night without finishing).
If it were not for some warning messages in the error log it would appear that it does not do anything at all.


Reproducible: Always

Steps to Reproduce:
1. Open maven_bug.b3aggr
Comment 1 Lothar Werzinger CLA 2011-09-18 17:52:00 EDT 
Created attachment 203561 [details]
the b3 aggregation file to reproduce the problem
Comment 2 Joerg Buchberger CLA 2012-12-14 04:22:09 EST 
Hi.

When I try to aggregate bundles from a Maven repository into a P2 repo,
then b3 gives the following output:

b3.bat aggregate --buildModel my.b3aggr
Loading all repositories
Unable to load repository http://repository.springsource.com/maven/bundles/external
Unable to load repository maven2:http://repository.springsource.com/maven/bundles/external
Build failed! Exception was org.eclipse.core.runtime.CoreException: Not all repositories could be loaded (see log for details)
Not all repositories could be loaded (see log for details)



However, there is no log output anywhere and hence also not more details about the failure.



Snippet from my b3aggr:
    <contributions label="Maven">
      <repositories location="http://repository.springsource.com/maven/bundles/external" nature="maven2" mirrorArtifacts="true">
        <bundles name="com.springsource.org.jdom" versionRange="2.0.1"/>
      </repositories>
      <mavenMappings namePattern="com.springsource.org.jdom" groupId="org.jdom" artifactId="com.springsource.org.jdom"/> <!-- removing/adding this mapping line did not change anything -->
    </contributions>
Comment 3 Joerg Buchberger CLA 2012-12-14 04:24:23 EST 
Created attachment 224719 [details]
screenshot showing bundle artifact in maven repo

attachment shows that bundle artifact really exists in the maven repo referenced in the b3aggr snippet
Comment 4 Thomas Hallgren CLA 2012-12-19 02:34:33 EST 
Did you have the "b3 and p2 - Nexus Indexer for Maven" feature when you attempted this? Without it, b3 will try and crawl the repository. In case of Maven Central, a crawl would take a very long time (days) if it's even possible.
Comment 5 David Williams CLA 2016-09-16 15:42:24 EDT 
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.]
Comment 6 Frederic Gurr CLA 2023-09-01 10:07:31 EDT 
If this issue is still relevant, please move it to https://github.com/eclipse-cbi/p2repo-aggregator/issues.