Bump tycho-version from 2.6.0 to 2.7.0

[dependabot]

Bumps tycho-version from 2.6.0 to 2.7.0.
Updates tycho-sourceref-jgit from 2.6.0 to 2.7.0

Updates tycho-buildtimestamp-jgit from 2.6.0 to 2.7.0

Updates tycho-maven-plugin from 2.6.0 to 2.7.0

Changelog

Sourced from tycho-maven-plugin's changelog.

2.7.0

Tycho-Pomless will become a tycho-core extension

Tycho pomless has started as a small experiment in tycho-extras. Over time it has grown to a fully-fledged solution to build pde-based artifacts with less effort and nearly zero additional configuration.

Neverless, the name "pomless" was always a bit misleading, as actually we have reduced the number required poms to one 'main-pom' it is still not pomless and actually allows poms to be used where suitable. Because of this, an to not limit the usage to "pomless" with this version a new core-extension is available name 'tycho-build', that effectively does what tycho-extras-pomless does but in the context of 'core' and is open to further improvements (maybe some time offering an option to not needing a pom at all).

All that needs to be done is replace the old

<extension>
	<groupId>org.eclipse.tycho.extras</groupId>
	<artifactId>tycho-pomless</artifactId>
	<version>2.7.0</version>
</extension>

with

<extension>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-build</artifactId>
	<version>2.7.0</version>
</extension>

Tycho-specific Maven GraphBuilder to support --also-make (-am) and --also-make-dependents (-amd)

The tycho-build extension (see above) was updated with a custom org.apache.maven.graph.GraphBuilder implementation.

Without this, the Maven options --also-make (-am) and --also-make-dependents (-amd) were not supported in a Tycho-based build, since only pom-dependencies were considered by Maven.

Using the custom GraphBuilder Tycho is able to perform P2 dependency resolution early-on and supply Maven with an updated set of projects required for the build.

Mixed reactor build support

previously Tycho has resolved pom considered depdencies as part of the inital maven setup (before the actual build starts). This has lead to the fact that it was not possible to mix projects that e.g. dynamically generate a manifest.

This was now changed and Tycho can now build mixed project setups see this integration test as an example: https://github.com/eclipse/tycho/tree/master/tycho-its/projects/mixed.reactor

This slightly changes some of the behaviour of previous pomDependecies=consider:

• dependecies of pom considered items has to be always been declared on the maven level (either by the project using it or the dependecy declaring it)
• pom considered items do not participate in the build-order computation as of the previous statement already ensure this
• if enabled, builds might fail later as projects are allowed to have incomplete requirements up until the intilize phase.

... (truncated)

Commits

• d5e199f Tycho 2.7.0 Release #648
• 41e943e Fix #664 delete file on exit by default
• b66db2c Fix #671 - don't overwrite tycho.mode property with pom-less extension
• 7fa521e Fix #670 - Significant target-resolution runtime regression
• 400646d Fix #681 move integration tests to the itest module.
• 2a62c5b Add a test-case for #658 (property propagation)
• abe9f2a Fix #665 Nested target fails if artifact is not already downloaded
• 057e3a3 Fix Jenkis file branch name
• 56ce9ed Fix #658 - preserve p2 artifact properties (eg PGP, maven info...)
• 2e89f62 NPE in MirrorMojo when using target platform as source
• Additional commits viewable in compare view

Updates target-platform-configuration from 2.6.0 to 2.7.0

Changelog

Sourced from target-platform-configuration's changelog.

2.7.0

Tycho-Pomless will become a tycho-core extension

Tycho pomless has started as a small experiment in tycho-extras. Over time it has grown to a fully-fledged solution to build pde-based artifacts with less effort and nearly zero additional configuration.

Neverless, the name "pomless" was always a bit misleading, as actually we have reduced the number required poms to one 'main-pom' it is still not pomless and actually allows poms to be used where suitable. Because of this, an to not limit the usage to "pomless" with this version a new core-extension is available name 'tycho-build', that effectively does what tycho-extras-pomless does but in the context of 'core' and is open to further improvements (maybe some time offering an option to not needing a pom at all).

All that needs to be done is replace the old

<extension>
	<groupId>org.eclipse.tycho.extras</groupId>
	<artifactId>tycho-pomless</artifactId>
	<version>2.7.0</version>
</extension>

with

<extension>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-build</artifactId>
	<version>2.7.0</version>
</extension>

Tycho-specific Maven GraphBuilder to support --also-make (-am) and --also-make-dependents (-amd)

The tycho-build extension (see above) was updated with a custom org.apache.maven.graph.GraphBuilder implementation.

Without this, the Maven options --also-make (-am) and --also-make-dependents (-amd) were not supported in a Tycho-based build, since only pom-dependencies were considered by Maven.

Using the custom GraphBuilder Tycho is able to perform P2 dependency resolution early-on and supply Maven with an updated set of projects required for the build.

Mixed reactor build support

previously Tycho has resolved pom considered depdencies as part of the inital maven setup (before the actual build starts). This has lead to the fact that it was not possible to mix projects that e.g. dynamically generate a manifest.

This was now changed and Tycho can now build mixed project setups see this integration test as an example: https://github.com/eclipse/tycho/tree/master/tycho-its/projects/mixed.reactor

This slightly changes some of the behaviour of previous pomDependecies=consider:

• dependecies of pom considered items has to be always been declared on the maven level (either by the project using it or the dependecy declaring it)
• pom considered items do not participate in the build-order computation as of the previous statement already ensure this
• if enabled, builds might fail later as projects are allowed to have incomplete requirements up until the intilize phase.

... (truncated)

Commits

• d5e199f Tycho 2.7.0 Release #648
• 41e943e Fix #664 delete file on exit by default
• b66db2c Fix #671 - don't overwrite tycho.mode property with pom-less extension
• 7fa521e Fix #670 - Significant target-resolution runtime regression
• 400646d Fix #681 move integration tests to the itest module.
• 2a62c5b Add a test-case for #658 (property propagation)
• abe9f2a Fix #665 Nested target fails if artifact is not already downloaded
• 057e3a3 Fix Jenkis file branch name
• 56ce9ed Fix #658 - preserve p2 artifact properties (eg PGP, maven info...)
• 2e89f62 NPE in MirrorMojo when using target platform as source
• Additional commits viewable in compare view

Updates tycho-source-plugin from 2.6.0 to 2.7.0

Changelog

Sourced from tycho-source-plugin's changelog.

2.7.0

Tycho-Pomless will become a tycho-core extension

Tycho pomless has started as a small experiment in tycho-extras. Over time it has grown to a fully-fledged solution to build pde-based artifacts with less effort and nearly zero additional configuration.

Neverless, the name "pomless" was always a bit misleading, as actually we have reduced the number required poms to one 'main-pom' it is still not pomless and actually allows poms to be used where suitable. Because of this, an to not limit the usage to "pomless" with this version a new core-extension is available name 'tycho-build', that effectively does what tycho-extras-pomless does but in the context of 'core' and is open to further improvements (maybe some time offering an option to not needing a pom at all).

All that needs to be done is replace the old

<extension>
	<groupId>org.eclipse.tycho.extras</groupId>
	<artifactId>tycho-pomless</artifactId>
	<version>2.7.0</version>
</extension>

with

<extension>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-build</artifactId>
	<version>2.7.0</version>
</extension>

Tycho-specific Maven GraphBuilder to support --also-make (-am) and --also-make-dependents (-amd)

The tycho-build extension (see above) was updated with a custom org.apache.maven.graph.GraphBuilder implementation.

Without this, the Maven options --also-make (-am) and --also-make-dependents (-amd) were not supported in a Tycho-based build, since only pom-dependencies were considered by Maven.

Using the custom GraphBuilder Tycho is able to perform P2 dependency resolution early-on and supply Maven with an updated set of projects required for the build.

Mixed reactor build support

previously Tycho has resolved pom considered depdencies as part of the inital maven setup (before the actual build starts). This has lead to the fact that it was not possible to mix projects that e.g. dynamically generate a manifest.

This was now changed and Tycho can now build mixed project setups see this integration test as an example: https://github.com/eclipse/tycho/tree/master/tycho-its/projects/mixed.reactor

This slightly changes some of the behaviour of previous pomDependecies=consider:

• dependecies of pom considered items has to be always been declared on the maven level (either by the project using it or the dependecy declaring it)
• pom considered items do not participate in the build-order computation as of the previous statement already ensure this
• if enabled, builds might fail later as projects are allowed to have incomplete requirements up until the intilize phase.

... (truncated)

Commits

• d5e199f Tycho 2.7.0 Release #648
• 41e943e Fix #664 delete file on exit by default
• b66db2c Fix #671 - don't overwrite tycho.mode property with pom-less extension
• 7fa521e Fix #670 - Significant target-resolution runtime regression
• 400646d Fix #681 move integration tests to the itest module.
• 2a62c5b Add a test-case for #658 (property propagation)
• abe9f2a Fix #665 Nested target fails if artifact is not already downloaded
• 057e3a3 Fix Jenkis file branch name
• 56ce9ed Fix #658 - preserve p2 artifact properties (eg PGP, maven info...)
• 2e89f62 NPE in MirrorMojo when using target platform as source
• Additional commits viewable in compare view

Updates tycho-packaging-plugin from 2.6.0 to 2.7.0

Changelog

Sourced from tycho-packaging-plugin's changelog.

2.7.0

Tycho-Pomless will become a tycho-core extension

Tycho pomless has started as a small experiment in tycho-extras. Over time it has grown to a fully-fledged solution to build pde-based artifacts with less effort and nearly zero additional configuration.

Neverless, the name "pomless" was always a bit misleading, as actually we have reduced the number required poms to one 'main-pom' it is still not pomless and actually allows poms to be used where suitable. Because of this, an to not limit the usage to "pomless" with this version a new core-extension is available name 'tycho-build', that effectively does what tycho-extras-pomless does but in the context of 'core' and is open to further improvements (maybe some time offering an option to not needing a pom at all).

All that needs to be done is replace the old

<extension>
	<groupId>org.eclipse.tycho.extras</groupId>
	<artifactId>tycho-pomless</artifactId>
	<version>2.7.0</version>
</extension>

with

<extension>
	<groupId>org.eclipse.tycho</groupId>
	<artifactId>tycho-build</artifactId>
	<version>2.7.0</version>
</extension>

Tycho-specific Maven GraphBuilder to support --also-make (-am) and --also-make-dependents (-amd)

The tycho-build extension (see above) was updated with a custom org.apache.maven.graph.GraphBuilder implementation.

Without this, the Maven options --also-make (-am) and --also-make-dependents (-amd) were not supported in a Tycho-based build, since only pom-dependencies were considered by Maven.

Using the custom GraphBuilder Tycho is able to perform P2 dependency resolution early-on and supply Maven with an updated set of projects required for the build.

Mixed reactor build support

previously Tycho has resolved pom considered depdencies as part of the inital maven setup (before the actual build starts). This has lead to the fact that it was not possible to mix projects that e.g. dynamically generate a manifest.

This was now changed and Tycho can now build mixed project setups see this integration test as an example: https://github.com/eclipse/tycho/tree/master/tycho-its/projects/mixed.reactor

This slightly changes some of the behaviour of previous pomDependecies=consider:

• dependecies of pom considered items has to be always been declared on the maven level (either by the project using it or the dependecy declaring it)
• pom considered items do not participate in the build-order computation as of the previous statement already ensure this
• if enabled, builds might fail later as projects are allowed to have incomplete requirements up until the intilize phase.

... (truncated)

Commits

• d5e199f Tycho 2.7.0 Release #648
• 41e943e Fix #664 delete file on exit by default
• b66db2c Fix #671 - don't overwrite tycho.mode property with pom-less extension
• 7fa521e Fix #670 - Significant target-resolution runtime regression
• 400646d Fix #681 move integration tests to the itest module.
• 2a62c5b Add a test-case for #658 (property propagation)
• abe9f2a Fix #665 Nested target fails if artifact is not already downloaded
• 057e3a3 Fix Jenkis file branch name
• 56ce9ed Fix #658 - preserve p2 artifact properties (eg PGP, maven info...)
• 2e89f62 NPE in MirrorMojo when using target platform as source
• Additional commits viewable in compare view

Updates tycho-p2-extras-plugin from 2.6.0 to 2.7.0

Updates tycho-p2-plugin from 2.6.0 to 2.7.0

Updates tycho-surefire-plugin from 2.6.0 to 2.7.0

Updates tycho-p2-director-plugin from 2.6.0 to 2.7.0

Updates tycho-p2-repository-plugin from 2.6.0 to 2.7.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[akurtakov]

@laeubi Could you help with this one? This looks like unwanted behavior change in 2.7.0.

[laeubi]

@laeubi Could you help with this one? This looks like unwanted behavior change in 2.7.0.

Can you explain what exactly has changed here?

[mickaelistria]

@laeubi it's caused by eclipse-tycho/tycho#700

[mickaelistria]

@laeubi it's caused by eclipse-tycho/tycho#700

Sorry, not relevant here. I had another bug in mind.

[laeubi]

What makes me wonder is that the CI has failing tests (do they fail with 2.6. also?) but the github flow fails. But as I know nothing about WWD this might be unrelated?

[mickaelistria]

Test failures are not related I believe. But further failure are most likely caused by some regression in Tycho 2.7.0

[ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:2.7.0:compare-version-with-baselines (compare-version-with-baseline) on project repository: Execution compare-version-with-baseline of goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:2.7.0:compare-version-with-baselines failed: Cannot set full specification for a custom profile more than once -> [Help 1]

[laeubi]

Is it possible to get a full (-X) trace? Why does it only fails on the windows workflow and not the CI workflow?

[mickaelistria]

Why does it only fails on the windows workflow and not the CI workflow?

It does fail on both the same way.

[laeubi]

Okay the test-failures have confused me ... any chance to reproduce this as a small test-case?

[laeubi]

What might be causing this is having a product and a category.xml and the <executionEnvironment>none</executionEnvironment> but that's just a guess, don't know if we have any integration test covering that case...

[mickaelistria]

Tycho bug reported at eclipse-tycho/tycho#707

[mickaelistria]

@akurtakov Should we make Wild Web Developer use Tycho 3.0.0-SNAPSHOT to get a fix for it? It's also a good opportunity to get anohter real project continuously testing snapshots.

[akurtakov]

Let's do it.

[mickaelistria]

Replaced with #795

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.