Bump tycho.version from 1.6.0 to 2.5.0 in /ddk-parent

[dependabot]

Bumps tycho.version from 1.6.0 to 2.5.0.
Updates tycho-maven-plugin from 1.6.0 to 2.5.0

Changelog

Sourced from tycho-maven-plugin's changelog.

2.5.0

Support for PGP Signatures in maven-p2 sites

The assemble-maven-repository mojo now supports embedding the PGP signature of maven artifacts to allow additional verifications and trust decisions.

Support for new m2e-pde features

Tycho supports the new m2e-pde features regarding multiple dependencies per target and specifying extra repositories in the target.

Improved cache handling

Previously Tycho failed if the remote update-site server was not available even if the file is already downloaded. Now, it uses the local file instead and issues a warning instead.

M2_REPO classpath variable support

Tycho now supports M2_REPO variable from .classpath

2.4.0

Support resolving of JUnit Classpath Container

It is now possible to resolve the JDT 'JUnit Classpath Container', for this do the following:

• add the 'JUnit Classpath Container' to the classpath of your eclipse project
• make sure you check in the .classpath file
• Now you can use the Junit classes without explcitly adding them to your bundle via require-bundle/import package

For an example take a look at the integration tests

Execute unit-tests with eclipse-plugin packaging

Before unit-tests are only executed for eclipse-test-plugin packaging types. Beside that it was only possible to execute them as part of tycho-surefire (what executes them inside an OSGi runtime) in the integration-test phase (making them actually some kind of integration test).

From now on this restriction is no longer true and one is able to execute unit-test with maven-surefire as well as integration-tests with tycho-failfast plugin. This works the following way:

• create a source-folder in your eclipse-plugin packaged project and mark them as a contains test-sources in the classpath settings:
• Create a unit-test inside that folder, either name it with any of the default-pattern maven-surefire plugin of or configure them explicitly.
• Include maven-surefire plugin configuration in your pom to select the appropriate test-providers

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-surefire-plugin</artifactId>
	<version>3.0.0-M5</version>
	<dependencies>
		<dependency>
			<groupId>org.apache.maven.surefire</groupId>
			<artifactId>surefire-junit47</artifactId>
			<version>3.0.0-M5</version>
		</dependency>
	</dependencies>
</tr></table> 

... (truncated)

Commits

• 7bd8eb0 Update versions to 2.5.0
• 34e8939 #303 M2E-core build fails with Uses-constraint-violations (#307)
• a4b9d01 Update Jenkinsfile
• 6600915 Fix #303 M2E-core build fails with Uses-constraint-violations (#304)
• 968172d Fix #261 BaselineValidator.validateAndReplace() fails with UnsupportedOperati...
• f9a8c9e Fix #292 Use POSIX longfile/bigfile mode
• 2dbbfcf Merge pull request #296 from LorenzoBettini/patch-1
• e12717c Update RELEASE_NOTES.md
• 56569de Update RELEASE_NOTES.md
• c06acab Update Releasing_Tycho.md
• Additional commits viewable in compare view

Updates target-platform-configuration from 1.6.0 to 2.5.0

Changelog

Sourced from target-platform-configuration's changelog.

2.5.0

Support for PGP Signatures in maven-p2 sites

The assemble-maven-repository mojo now supports embedding the PGP signature of maven artifacts to allow additional verifications and trust decisions.

Support for new m2e-pde features

Tycho supports the new m2e-pde features regarding multiple dependencies per target and specifying extra repositories in the target.

Improved cache handling

Previously Tycho failed if the remote update-site server was not available even if the file is already downloaded. Now, it uses the local file instead and issues a warning instead.

M2_REPO classpath variable support

Tycho now supports M2_REPO variable from .classpath

2.4.0

Support resolving of JUnit Classpath Container

It is now possible to resolve the JDT 'JUnit Classpath Container', for this do the following:

• add the 'JUnit Classpath Container' to the classpath of your eclipse project
• make sure you check in the .classpath file
• Now you can use the Junit classes without explcitly adding them to your bundle via require-bundle/import package

For an example take a look at the integration tests

Execute unit-tests with eclipse-plugin packaging

Before unit-tests are only executed for eclipse-test-plugin packaging types. Beside that it was only possible to execute them as part of tycho-surefire (what executes them inside an OSGi runtime) in the integration-test phase (making them actually some kind of integration test).

From now on this restriction is no longer true and one is able to execute unit-test with maven-surefire as well as integration-tests with tycho-failfast plugin. This works the following way:

• create a source-folder in your eclipse-plugin packaged project and mark them as a contains test-sources in the classpath settings:
• Create a unit-test inside that folder, either name it with any of the default-pattern maven-surefire plugin of or configure them explicitly.
• Include maven-surefire plugin configuration in your pom to select the appropriate test-providers

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-surefire-plugin</artifactId>
	<version>3.0.0-M5</version>
	<dependencies>
		<dependency>
			<groupId>org.apache.maven.surefire</groupId>
			<artifactId>surefire-junit47</artifactId>
			<version>3.0.0-M5</version>
		</dependency>
	</dependencies>
</tr></table> 

... (truncated)

Commits

• 7bd8eb0 Update versions to 2.5.0
• 34e8939 #303 M2E-core build fails with Uses-constraint-violations (#307)
• a4b9d01 Update Jenkinsfile
• 6600915 Fix #303 M2E-core build fails with Uses-constraint-violations (#304)
• 968172d Fix #261 BaselineValidator.validateAndReplace() fails with UnsupportedOperati...
• f9a8c9e Fix #292 Use POSIX longfile/bigfile mode
• 2dbbfcf Merge pull request #296 from LorenzoBettini/patch-1
• e12717c Update RELEASE_NOTES.md
• 56569de Update RELEASE_NOTES.md
• c06acab Update Releasing_Tycho.md
• Additional commits viewable in compare view

Updates tycho-compiler-plugin from 1.6.0 to 2.5.0

Changelog

Sourced from tycho-compiler-plugin's changelog.

2.5.0

Support for PGP Signatures in maven-p2 sites

The assemble-maven-repository mojo now supports embedding the PGP signature of maven artifacts to allow additional verifications and trust decisions.

Support for new m2e-pde features

Tycho supports the new m2e-pde features regarding multiple dependencies per target and specifying extra repositories in the target.

Improved cache handling

Previously Tycho failed if the remote update-site server was not available even if the file is already downloaded. Now, it uses the local file instead and issues a warning instead.

M2_REPO classpath variable support

Tycho now supports M2_REPO variable from .classpath

2.4.0

Support resolving of JUnit Classpath Container

It is now possible to resolve the JDT 'JUnit Classpath Container', for this do the following:

• add the 'JUnit Classpath Container' to the classpath of your eclipse project
• make sure you check in the .classpath file
• Now you can use the Junit classes without explcitly adding them to your bundle via require-bundle/import package

For an example take a look at the integration tests

Execute unit-tests with eclipse-plugin packaging

Before unit-tests are only executed for eclipse-test-plugin packaging types. Beside that it was only possible to execute them as part of tycho-surefire (what executes them inside an OSGi runtime) in the integration-test phase (making them actually some kind of integration test).

From now on this restriction is no longer true and one is able to execute unit-test with maven-surefire as well as integration-tests with tycho-failfast plugin. This works the following way:

• create a source-folder in your eclipse-plugin packaged project and mark them as a contains test-sources in the classpath settings:
• Create a unit-test inside that folder, either name it with any of the default-pattern maven-surefire plugin of or configure them explicitly.
• Include maven-surefire plugin configuration in your pom to select the appropriate test-providers

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-surefire-plugin</artifactId>
	<version>3.0.0-M5</version>
	<dependencies>
		<dependency>
			<groupId>org.apache.maven.surefire</groupId>
			<artifactId>surefire-junit47</artifactId>
			<version>3.0.0-M5</version>
		</dependency>
	</dependencies>
</tr></table> 

... (truncated)

Commits

• 7bd8eb0 Update versions to 2.5.0
• 34e8939 #303 M2E-core build fails with Uses-constraint-violations (#307)
• a4b9d01 Update Jenkinsfile
• 6600915 Fix #303 M2E-core build fails with Uses-constraint-violations (#304)
• 968172d Fix #261 BaselineValidator.validateAndReplace() fails with UnsupportedOperati...
• f9a8c9e Fix #292 Use POSIX longfile/bigfile mode
• 2dbbfcf Merge pull request #296 from LorenzoBettini/patch-1
• e12717c Update RELEASE_NOTES.md
• 56569de Update RELEASE_NOTES.md
• c06acab Update Releasing_Tycho.md
• Additional commits viewable in compare view

Updates tycho-packaging-plugin from 1.6.0 to 2.5.0

Changelog

Sourced from tycho-packaging-plugin's changelog.

2.5.0

Support for PGP Signatures in maven-p2 sites

The assemble-maven-repository mojo now supports embedding the PGP signature of maven artifacts to allow additional verifications and trust decisions.

Support for new m2e-pde features

Tycho supports the new m2e-pde features regarding multiple dependencies per target and specifying extra repositories in the target.

Improved cache handling

Previously Tycho failed if the remote update-site server was not available even if the file is already downloaded. Now, it uses the local file instead and issues a warning instead.

M2_REPO classpath variable support

Tycho now supports M2_REPO variable from .classpath

2.4.0

Support resolving of JUnit Classpath Container

It is now possible to resolve the JDT 'JUnit Classpath Container', for this do the following:

• add the 'JUnit Classpath Container' to the classpath of your eclipse project
• make sure you check in the .classpath file
• Now you can use the Junit classes without explcitly adding them to your bundle via require-bundle/import package

For an example take a look at the integration tests

Execute unit-tests with eclipse-plugin packaging

Before unit-tests are only executed for eclipse-test-plugin packaging types. Beside that it was only possible to execute them as part of tycho-surefire (what executes them inside an OSGi runtime) in the integration-test phase (making them actually some kind of integration test).

From now on this restriction is no longer true and one is able to execute unit-test with maven-surefire as well as integration-tests with tycho-failfast plugin. This works the following way:

• create a source-folder in your eclipse-plugin packaged project and mark them as a contains test-sources in the classpath settings:
• Create a unit-test inside that folder, either name it with any of the default-pattern maven-surefire plugin of or configure them explicitly.
• Include maven-surefire plugin configuration in your pom to select the appropriate test-providers

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-surefire-plugin</artifactId>
	<version>3.0.0-M5</version>
	<dependencies>
		<dependency>
			<groupId>org.apache.maven.surefire</groupId>
			<artifactId>surefire-junit47</artifactId>
			<version>3.0.0-M5</version>
		</dependency>
	</dependencies>
</tr></table> 

... (truncated)

Commits

• 7bd8eb0 Update versions to 2.5.0
• 34e8939 #303 M2E-core build fails with Uses-constraint-violations (#307)
• a4b9d01 Update Jenkinsfile
• 6600915 Fix #303 M2E-core build fails with Uses-constraint-violations (#304)
• 968172d Fix #261 BaselineValidator.validateAndReplace() fails with UnsupportedOperati...
• f9a8c9e Fix #292 Use POSIX longfile/bigfile mode
• 2dbbfcf Merge pull request #296 from LorenzoBettini/patch-1
• e12717c Update RELEASE_NOTES.md
• 56569de Update RELEASE_NOTES.md
• c06acab Update Releasing_Tycho.md
• Additional commits viewable in compare view

Updates tycho-surefire-plugin from 1.6.0 to 2.5.0

Updates tycho-source-plugin from 1.6.0 to 2.5.0

Changelog

Sourced from tycho-source-plugin's changelog.

2.5.0

Support for PGP Signatures in maven-p2 sites

The assemble-maven-repository mojo now supports embedding the PGP signature of maven artifacts to allow additional verifications and trust decisions.

Support for new m2e-pde features

Tycho supports the new m2e-pde features regarding multiple dependencies per target and specifying extra repositories in the target.

Improved cache handling

Previously Tycho failed if the remote update-site server was not available even if the file is already downloaded. Now, it uses the local file instead and issues a warning instead.

M2_REPO classpath variable support

Tycho now supports M2_REPO variable from .classpath

2.4.0

Support resolving of JUnit Classpath Container

It is now possible to resolve the JDT 'JUnit Classpath Container', for this do the following:

• add the 'JUnit Classpath Container' to the classpath of your eclipse project
• make sure you check in the .classpath file
• Now you can use the Junit classes without explcitly adding them to your bundle via require-bundle/import package

For an example take a look at the integration tests

Execute unit-tests with eclipse-plugin packaging

Before unit-tests are only executed for eclipse-test-plugin packaging types. Beside that it was only possible to execute them as part of tycho-surefire (what executes them inside an OSGi runtime) in the integration-test phase (making them actually some kind of integration test).

From now on this restriction is no longer true and one is able to execute unit-test with maven-surefire as well as integration-tests with tycho-failfast plugin. This works the following way:

• create a source-folder in your eclipse-plugin packaged project and mark them as a contains test-sources in the classpath settings:
• Create a unit-test inside that folder, either name it with any of the default-pattern maven-surefire plugin of or configure them explicitly.
• Include maven-surefire plugin configuration in your pom to select the appropriate test-providers

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-surefire-plugin</artifactId>
	<version>3.0.0-M5</version>
	<dependencies>
		<dependency>
			<groupId>org.apache.maven.surefire</groupId>
			<artifactId>surefire-junit47</artifactId>
			<version>3.0.0-M5</version>
		</dependency>
	</dependencies>
</tr></table> 

... (truncated)

Commits

• 7bd8eb0 Update versions to 2.5.0
• 34e8939 #303 M2E-core build fails with Uses-constraint-violations (#307)
• a4b9d01 Update Jenkinsfile
• 6600915 Fix #303 M2E-core build fails with Uses-constraint-violations (#304)
• 968172d Fix #261 BaselineValidator.validateAndReplace() fails with UnsupportedOperati...
• f9a8c9e Fix #292 Use POSIX longfile/bigfile mode
• 2dbbfcf Merge pull request #296 from LorenzoBettini/patch-1
• e12717c Update RELEASE_NOTES.md
• 56569de Update RELEASE_NOTES.md
• c06acab Update Releasing_Tycho.md
• Additional commits viewable in compare view

Updates tycho-source-feature-plugin from 1.6.0 to 2.5.0

Updates tycho-versions-plugin from 1.6.0 to 2.5.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)

[dependabot]

Superseded by #5.