Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Tycho/Migration Howto"
< Tycho
| Line 18: | Line 18: | ||
so you can reference it using <tt>${tycho-version}</tt> anywhere in the child pom.xml files e.g. when configuring tycho plugins. | so you can reference it using <tt>${tycho-version}</tt> anywhere in the child pom.xml files e.g. when configuring tycho plugins. | ||
| + | |||
| + | In case you have deeply nested projects and used several generate-poms invocations, add a top-level parent pom.xml and reference it as parent from the intermediate parent poms. | ||
== Adding p2 repositories to resolve external dependencies == | == Adding p2 repositories to resolve external dependencies == | ||
Revision as of 07:14, 5 June 2013
This page is intended to give existing projects a jumpstart for setting up a Tycho build.
While each project is different, there are some common steps:
Contents
Scaffolding: generate pom.xml files
Maven needs pom.xml files to drive the build. See Generating POM files on how to generate an initial skeleton for these files.
Manual adjustments
In the generated top-level (parent) pom.xml, it's a good idea to globally define the tycho version to use
<properties> <tycho-version>0.18.0</tycho-version> </properties>
so you can reference it using ${tycho-version} anywhere in the child pom.xml files e.g. when configuring tycho plugins.
In case you have deeply nested projects and used several generate-poms invocations, add a top-level parent pom.xml and reference it as parent from the intermediate parent poms.