-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[regression] tycho-buildtimestamp-jgit impact with pomDependencies=consider #1377
Comments
Why "demonstration fails using Tycho 2.7.5 with tycho-buildtimestamp-jgit 2.6.0" ? Tycho components are not supposed to mix versions. |
I initially thought it was a problem in the jgit timestamp provider itself. I knew the problem didn’t occur in Tycho 2.6.0 so I thought I’d try the 2.6.0 provider in 2.7.5 (there didn’t look to be many changes). |
- update to Tycho 2.7.5, which includes lifecycle-mapping definitions and avoids the need for the now-defunct tycho configurator - configure the c.g.c.t.e.googleapis copy-dependencies to be executed on workspace change, and avoid the need for the maven-dependency-plugin configurator - disable the use of the tycho-buildtimestamp-jgit provider specifically for features/c.g.c.t.e.3rdparty.feature to work around eclipse-tycho/tycho#1377
@briandealwis thanks for the example, do you think you can transform this into an integration-test to demonstrate the issue and propose a PR for the new test-case? |
I used git bisect and found the problem commit is 1609a1a (PR #470). Unfortunately this is beyond my knowledge of Tycho. I've turned the problem project into an integration test at https://github.com/briandealwis/tycho/tree/jgit-buildtimestamp-bug/ |
Can you rebase this on current master and then open a Pullrequest? |
* chore: enable building in latest Eclipse - update to Tycho 2.7.5, which includes lifecycle-mapping definitions and avoids the need for the now-defunct tycho configurator - configure the c.g.c.t.e.googleapis copy-dependencies to be executed on workspace change, and avoid the need for the maven-dependency-plugin configurator - disable the use of the tycho-buildtimestamp-jgit provider specifically for features/c.g.c.t.e.3rdparty.feature to work around eclipse-tycho/tycho#1377 * Use Tycho 2.7.x only when loading into Eclipse Use the `m2e.version` property, set by m2eclipse, to determine when being used within Eclpse. Tycho 2.7.4+ includes lifecycle mapping metadata for the Tycho plugins such that we no longer need to use the Tycho configurator. But we continue to use Tycho 2.6.0 for builds.
The issue is that the (full) target platform is (not yet) computed at this phase, but the error only occurs with a custom build-timestamp provider, that's why this was not detected earlier. |
I've hit a subtle bug in Tycho that was introduced in 2.7.0 and is present in 3.0.0-SNAPSHOT.
Basically a project that:
pomDependencies=consider
,will fail with a resolving error on the Maven dependency.
I've created an demonstration project in https://github.com/briandealwis/tycho/tree/jgit-buildtimestamp-bug/tycho-its/projects/pomDependencyConsider.buildtimestamp.jgit
The text was updated successfully, but these errors were encountered: