Re: [cbi-dev] Version resolution failure

[David M Williams <david_williams@xxxxxxxxxx>]

Is anyone else getting this message mailed
over and over again? 
Doesn't seem to be going to "archives"
over and over, 
http://dev.eclipse.org/mhonarc/lists/cbi-dev/
but I get a new mail version about once
an hour. 
Could be "my" mail system,
for all I know. 




From:      
 Terry Parker <tparker@xxxxxxxxxx>
To:      
 Common-build Developers
discussion <cbi-dev@xxxxxxxxxxx>, 
Date:      
 05/29/2014 01:08 PM
Subject:    
   Re: [cbi-dev]
Version resolution failure
Sent by:    
   cbi-dev-bounces@xxxxxxxxxxx

---

On Wed, May 28, 2014 at 3:27 PM, Terry Parker <tparker@xxxxxxxxxx>
wrote:
For future reference, I got hit by https://bugs.eclipse.org/416619.
That is such a nasty bug. Wouldn't it be possible to compare the contents
of the feature.xml file before swapping in the baseline version?

Actually the issue is that the qualifier for the feature
bundle needs to be updated to reflect any changes in the locally built
feature.xml from that in the baseline repository.

--Terry


On Fri, May 23, 2014 at 5:53 PM, Terry Parker <tparker@xxxxxxxxxx>
wrote:
Thanks Thanh,

I looked at all of the feature.xml files in the target
directories for that dependency chain and all of the versions are consistent
with the logged output of the build, so the versions for those features
are all newer than that of the org.eclipse.core.jobs
plug-in.  What's more, the eclipse.platform.releng.aggregator/eclipse.platform.ui/features/org.eclipse.e4.rcp/target/feature.xml
file has the correct version="3.6.0.v20140513-2053" in its <plugin>
tag for the org.eclipse.core.jobs
plug-in.  And yet when running the publish-products phase for org.eclipse.sdk.ide
it fails with the message about not being able to find version 3.6.0.v20140424-0053
of org.eclipse.core.jobs.

As an experiment I deleted my branch in the eclipse.platform.runtime
directory, recreated it from the commit at the RC1 release, cherry picked
the Eclipse Jobs API patch, and rebuilt. That succeeded. Then I merged
in an additional commit from master into my branch and rebuilt, and that
failed. So this problem is reproducible. I suspect this is a subtle bug
in Tycho. I'll try to find time to file a bug next week.

--Terry


On Fri, May 23, 2014 at 8:59 AM, Thanh Ha <thanh.ha@xxxxxxxxxxx>
wrote:
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 


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev



_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev