-
Notifications
You must be signed in to change notification settings - Fork 193
Home
To use the Tycho build extension, add the following configuration in your parent POM:
<properties>
<tycho-version>2.7.3</tycho-version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-maven-plugin</artifactId>
<version>${tycho-version}</version>
<extensions>true</extensions>
</plugin>
</plugins>
</build>
See the release notes for a list of newer available Tycho versions.
If you want to use the latest development version of Tycho, update the tycho-version property accordingly and add the following Maven repository containing the Tycho snapshots in your parent POM:
<pluginRepositories>
<pluginRepository>
<id>tycho-snapshots</id>
<url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
</pluginRepository>
</pluginRepositories>
If you using the tycho-pomless extension or you want to make the Tycho development version available in all your builds, you need to add the tycho-snapshots repository in your settings.xml instead:
<settings>
<profiles>
<profile>
<id>tycho-snapshots</id>
<pluginRepositories>
<pluginRepository>
<id>tycho-snapshots</id>
<url>https://repo.eclipse.org/content/repositories/tycho-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>tycho-snapshots</activeProfile>
</activeProfiles>
</settings>
Often the best way to get a problem fixed is providing a project reproducing the problem. Even better providing it in the form of an integration test that way it is ensured that the problem do not arise any time later again. Creating an integration-test in most cases only require some simple steps:
- Fork the Tycho repository
- create a new branch (name it e.g.
issue_<number>_reproducer
) - Create a new project folder and add a test case as described in the CONTRIBUTING document
- push your changes and create a pull-request