Bugzilla – Full Text Bug Listing
| Summary: | [tycho] Tycho fails to resolve on latest maven snapshot builds (3.6.1-SNAPSHOT ~0be26449fb96774be126a6ad245d1a98dc71907c) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Raymond Auge <raymond.auge> |
| Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mat.booth, pascal.huerlimann, paul-eclipse, sravankumarl, titou10.titou10, torkildr |
| Version: | 4.12 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Raymond Auge
Correction on the maven sha. It's actually 0be26449fb96774be126a6ad245d1a98dc71907c In eclipse to build individual plugins(maven projects) we need to use build-individual-bundles profile. Do you see same error with this command? mvn clean install -Pbuild-individual-bundles (In reply to Sravan Kumar Lakkimsetti from comment #2) > In eclipse to build individual plugins(maven projects) we need to use > build-individual-bundles profile. Do you see same error with this command? > > mvn clean install -Pbuild-individual-bundles Nope! That didn't work, same problem. FYI, I've never had to use -Pbuild-individual-bundles in the rt.eclipse.* projects (disclosure: I'm the maintainer of org.eclipse.equinox.http.servlet). (In reply to Raymond Auge from comment #3) > (In reply to Sravan Kumar Lakkimsetti from comment #2) > > In eclipse to build individual plugins(maven projects) we need to use > > build-individual-bundles profile. Do you see same error with this command? > > > > mvn clean install -Pbuild-individual-bundles > > Nope! That didn't work, same problem. > > FYI, I've never had to use -Pbuild-individual-bundles in the rt.eclipse.* > projects (disclosure: I'm the maintainer of > org.eclipse.equinox.http.servlet). Till couple of years ago we were explicitly using build-individual-bundles profile. With some effort from Alex the profile selection is automatic now. That might be the reason why it is working for you. Can you point me a link where I can download maven 3.6.1? (In reply to Sravan Kumar Lakkimsetti from comment #4) > (In reply to Raymond Auge from comment #3) > > (In reply to Sravan Kumar Lakkimsetti from comment #2) > > > In eclipse to build individual plugins(maven projects) we need to use > > > build-individual-bundles profile. Do you see same error with this command? > > > > > > mvn clean install -Pbuild-individual-bundles > > > > Nope! That didn't work, same problem. > > > > FYI, I've never had to use -Pbuild-individual-bundles in the rt.eclipse.* > > projects (disclosure: I'm the maintainer of > > org.eclipse.equinox.http.servlet). > > Till couple of years ago we were explicitly using build-individual-bundles > profile. With some effort from Alex the profile selection is automatic now. > That might be the reason why it is working for you. > > Can you point me a link where I can download maven 3.6.1? checkout the repo [1] and follow the quick build [2] steps, takes no more than 2 minutes to complete the whole process. [1] https://github.com/apache/maven [2] https://github.com/apache/maven#quick-build Once you have a build, set your MAVEN_HOME and/or add it to your path. I see that with Maven 3.6.1 the following line is missing in the log. Adding repository http://download.eclipse.org/eclipse/updates/4.12-I-builds The dependencies are available at the above link. Since this repository was not added maven is not able to get the required dependencies The basic problem here is the eclipse I-builds repository is not getting added into maven reactor. @mat can you help us in this regard? I'm seeing the same issue with one of our product builds. After running "brew update" I ended up with Maven 3.6.1 (release) which failed to resolve dependencies. When downgrading to Maven 3.5.4 I was able to build the product again. Note that for this product build I'm not using target platform configuration, but rather a list of repositories with the "p2" layout. I have just encountered this problem after upgrading from maven 3.6.0 to 3.6.1. Building several of our projects fails after the upgrade, with maven being unable to resolve osgi dependencies. > Note that for this product build I'm not using target platform > configuration, but rather a list of repositories with the "p2" layout. This is also what we do. See https://github.com/jazz-community/jazz-plugin-base-service for an example of how we configure all our builds. Downgrading to 3.6.0 has solved the problem. Maven 3.6.1 broke dependency resolution for p2 repositories. Either wait for 3.6.2 or downgrade to 3.6.0. *** This bug has been marked as a duplicate of bug 546463 *** |