SAP / hybris-commerce-eclipse-plugin

A plugin for Eclipse IDE that makes developers more efficient when developing on SAP Hybris Commerce.
Apache License 2.0
34 stars 28 forks source link

Bump tycho-version from 2.5.0 to 2.6.0 #100

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

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

Changelog

Sourced from tycho-maven-plugin's changelog.

2.6.0

Delayed classpath computation

Previously the classpath of a project was computed in the maven-setup phase, this has several restrictions. Tycho now delays the classpath computation to a later stage (initialize phase).

If you want to perform the classpath validation in the validate phase of your build you can force classpath computation with the following snippet:

<plugin>
    <groupId>org.eclipse.tycho</groupId>
    <artifactId>tycho-compiler-plugin</artifactId>
    <version>${tycho.version}</version>
    <executions>
        <execution>
            <id>verify-classpath</id>
            <phase>validate</phase>
            <goals>
                <goal>validate-classpath</goal>
            </goals>
            <configuration>
            </configuration>
        </execution>
    </executions>
</plugin>

Support for generation of a feature from a maven target-location template

Tycho now support the m2e feature to generate a feature from a maven target location.

Support for nested targets

Tycho now supports nested target locations.

An example could be found here.

Support for pom dependencies in maven target locations

Tycho now supports pom dependencies inside maven target locations.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.8"?>
<target name="with-pom-dependency">
   <locations>
      <location includeSource="true" missingManifest="generate" type="Maven">
         <dependencies>
            <dependency>
               <groupId>com.sun.xml.ws</groupId>
               <artifactId>jaxws-ri</artifactId>
</tr></table> 

... (truncated)

Commits
  • 7a04b98 Prepare Tycho 2.6.0 release
  • cf98ee4 Fix #496 ResolutionArguments#hashcode is not stable
  • 5ca5155 - Update release notes to reflect the release on this branch
  • 1fe29d7 Update to maven-fluido-skin 1.10.0
  • a3733cb Bump doxia-module-markdown from 1.9.1 to 1.11.1
  • e1aae1d Bump maven-site-plugin from 3.9.1 to 3.10.0
  • a3d6f1e Bump plexusVersion from 2.1.0 to 2.1.1
  • 3039e08 Fix typos
  • bd3fe97 Merge pull request #446 from laeubi/adjust_for_m2e
  • e072a85 Adjust to recent m2e changes regarding DependencyDepth
  • Additional commits viewable in compare view


Updates tycho-compiler-plugin from 2.5.0 to 2.6.0

Changelog

Sourced from tycho-compiler-plugin's changelog.

2.6.0

Delayed classpath computation

Previously the classpath of a project was computed in the maven-setup phase, this has several restrictions. Tycho now delays the classpath computation to a later stage (initialize phase).

If you want to perform the classpath validation in the validate phase of your build you can force classpath computation with the following snippet:

<plugin>
    <groupId>org.eclipse.tycho</groupId>
    <artifactId>tycho-compiler-plugin</artifactId>
    <version>${tycho.version}</version>
    <executions>
        <execution>
            <id>verify-classpath</id>
            <phase>validate</phase>
            <goals>
                <goal>validate-classpath</goal>
            </goals>
            <configuration>
            </configuration>
        </execution>
    </executions>
</plugin>

Support for generation of a feature from a maven target-location template

Tycho now support the m2e feature to generate a feature from a maven target location.

Support for nested targets

Tycho now supports nested target locations.

An example could be found here.

Support for pom dependencies in maven target locations

Tycho now supports pom dependencies inside maven target locations.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.8"?>
<target name="with-pom-dependency">
   <locations>
      <location includeSource="true" missingManifest="generate" type="Maven">
         <dependencies>
            <dependency>
               <groupId>com.sun.xml.ws</groupId>
               <artifactId>jaxws-ri</artifactId>
</tr></table> 

... (truncated)

Commits
  • 7a04b98 Prepare Tycho 2.6.0 release
  • cf98ee4 Fix #496 ResolutionArguments#hashcode is not stable
  • 5ca5155 - Update release notes to reflect the release on this branch
  • 1fe29d7 Update to maven-fluido-skin 1.10.0
  • a3733cb Bump doxia-module-markdown from 1.9.1 to 1.11.1
  • e1aae1d Bump maven-site-plugin from 3.9.1 to 3.10.0
  • a3d6f1e Bump plexusVersion from 2.1.0 to 2.1.1
  • 3039e08 Fix typos
  • bd3fe97 Merge pull request #446 from laeubi/adjust_for_m2e
  • e072a85 Adjust to recent m2e changes regarding DependencyDepth
  • Additional commits viewable in compare view


Updates target-platform-configuration from 2.5.0 to 2.6.0

Changelog

Sourced from target-platform-configuration's changelog.

2.6.0

Delayed classpath computation

Previously the classpath of a project was computed in the maven-setup phase, this has several restrictions. Tycho now delays the classpath computation to a later stage (initialize phase).

If you want to perform the classpath validation in the validate phase of your build you can force classpath computation with the following snippet:

<plugin>
    <groupId>org.eclipse.tycho</groupId>
    <artifactId>tycho-compiler-plugin</artifactId>
    <version>${tycho.version}</version>
    <executions>
        <execution>
            <id>verify-classpath</id>
            <phase>validate</phase>
            <goals>
                <goal>validate-classpath</goal>
            </goals>
            <configuration>
            </configuration>
        </execution>
    </executions>
</plugin>

Support for generation of a feature from a maven target-location template

Tycho now support the m2e feature to generate a feature from a maven target location.

Support for nested targets

Tycho now supports nested target locations.

An example could be found here.

Support for pom dependencies in maven target locations

Tycho now supports pom dependencies inside maven target locations.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.8"?>
<target name="with-pom-dependency">
   <locations>
      <location includeSource="true" missingManifest="generate" type="Maven">
         <dependencies>
            <dependency>
               <groupId>com.sun.xml.ws</groupId>
               <artifactId>jaxws-ri</artifactId>
</tr></table> 

... (truncated)

Commits
  • 7a04b98 Prepare Tycho 2.6.0 release
  • cf98ee4 Fix #496 ResolutionArguments#hashcode is not stable
  • 5ca5155 - Update release notes to reflect the release on this branch
  • 1fe29d7 Update to maven-fluido-skin 1.10.0
  • a3733cb Bump doxia-module-markdown from 1.9.1 to 1.11.1
  • e1aae1d Bump maven-site-plugin from 3.9.1 to 3.10.0
  • a3d6f1e Bump plexusVersion from 2.1.0 to 2.1.1
  • 3039e08 Fix typos
  • bd3fe97 Merge pull request #446 from laeubi/adjust_for_m2e
  • e072a85 Adjust to recent m2e changes regarding DependencyDepth
  • Additional commits viewable in compare view


Updates tycho-surefire-plugin from 2.5.0 to 2.6.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[bot] commented 2 years ago

Superseded by #101.