Re: [cbi-dev] Version resolution failure

[Thanh Ha <thanh.ha@xxxxxxxxxxx>]

I would verify that things that depend on it are also pulling in newer versions (as in the version you are building). I'm not sure when you made the change but if you were building today I would have expected org.eclipse.sdk.ide to pull in this feature with today's timestamp:

org.eclipse.e4.rcp.feature.group 1.3.100.v20140515-1607

According to your output the dependency change seems to be org.eclipse.sdk.ide > org.eclipse.sdk.feature > org.eclipse.platform.feature > org.eclipse.e4.rcp.feature > org.eclipse.core.jobs. I would verify that all these intermediate bundles are pulling in the newer version which includes your org.eclipse.core.jobs bundle.

In the tycho-p2-plugin step there's a baseline comparator as well which reuses older bundles if the newer bundle you created did not change. You should see output similar to this if it's using the bundle you created:

[INFO] --- tycho-p2-plugin:0.20.0:p2-metadata-default (default-p2-metadata-default) @ org.eclipse.core.jobs ---
[INFO] No baseline version MavenProject: org.eclipse.core:org.eclipse.core.jobs:3.6.0-SNAPSHOT @ /buildroot/eclipse.platform.releng.aggregator/eclipse.platform.runtime/bundles/org.eclipse.core.jobs/pom.xml


However if it detected no changes were made between the 2 bundles you may see a message like this:

[INFO] --- tycho-p2-plugin:0.20.0:p2-metadata (attached-p2-metadata) @ org.eclipse.help ---
[WARNING] MavenProject: org.eclipse.help.feature:org.eclipse.help:2.0.102-SNAPSHOT @ /buildroot/eclipse.platform.releng.aggregator/eclipse.platform.releng/features/org.eclipse.help-feature/pom.xml: baseline and build artifacts have same version but different contents
[INFO] MavenProject: org.eclipse.help.feature:org.eclipse.help:2.0.102-SNAPSHOT @ /buildroot/eclipse.platform.releng.aggregator/eclipse.platform.releng/features/org.eclipse.help-feature/pom.xml
    The main artifact has been replaced with the baseline version.
    The following attached artifacts have been replaced with the baseline version: [sources-feature]


Check your logs to make sure all the dependencies are not being replaced with the older versions of your bundles.


Hope this helps,

Thanh

On 23/05/14 10:46 AM, Terry Parker wrote:

I’m trying to rebuild the 4.4 RC1 build with some cherry picks (including the Jobs API parallelization proposed in http://bugs.eclipse.org/432049) but when I get to the final phase of building the org.eclipse.sdk.ide product I get this error:

[INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ org.eclipse.sdk.ide ---
[INFO] Cannot complete the request.  Generating details.
[INFO] Cannot complete the request.  Generating details.
[INFO] {osgi.os=linux, osgi.ws=gtk, org.eclipse.update.install.features=true, osgi.arch=x86}[ERROR] Cannot resolve project dependencies:
[ERROR]   Software being installed: org.eclipse.sdk.ide 4.4.0.qualifier
[ERROR]   Missing requirement: org.eclipse.e4.rcp.feature.group 1.3.100.v20140515-1607 requires 'org.eclipse.core.jobs [3.6.0.v20140424-0053]' but it could not be found
[ERROR]   Cannot satisfy dependency: org.eclipse.platform.feature.group 4.4.0.v20140522-1740 depends on: org.eclipse.rcp.feature.group [4.4.0.v20140522-1740]
[ERROR]   Cannot satisfy dependency: org.eclipse.rcp.feature.group 4.4.0.v20140522-1740 depends on: org.eclipse.e4.rcp.feature.group [1.3.100.v20140515-1607]
[ERROR]   Cannot satisfy dependency: org.eclipse.sdk.feature.group 4.4.0.v20140522-1740 depends on: org.eclipse.platform.feature.group [4.4.0.v20140522-1740]
[ERROR]   Cannot satisfy dependency: org.eclipse.sdk.ide 4.4.0.qualifier depends on: org.eclipse.sdk.feature.group 0.0.0

With my cherry-pick the org.eclipse.core.jobs plug-in is being built at version 3.6.0.v20140513-2053, whereas 3.6.0.v20140424-0053 seems to be coming from the baseline repository. I’ve tried turning on “-Dtycho.debug.resolver=true -X” but it isn’t giving me the details I need to debug this.

Some additional information is that this worked when I did my initial build for M7.  The sequence of events on my clone of the eclipse.platform.runtime repo is the following:
1) Create a new R4_4_google branch from the I20140501-0200 tag
2) In the R4_4_google branch, cherry pick the change for bug 432049
3) Tag and build. Success!
4) In the R4_4_google branch, merge in the changes up to tag I20140515-1230
5) Retag the head of the R4_4_google branch. Build. Fail!

With the multi-hour build turnaround times I'm having a lot of trouble debugging this. Why is the publisher plugin picking up the wrong qualifier? Does anyone have any ideas?

Thanks,
Terry