| Re: [mdt-papyrus.dev] Preparing the Tycho build for Papyrus |
|
Hello Gaël, This is exactly the objective, having PolarSys in mind. We have a HIPP instance since yesterday :) We are still in the process of installing the new build jobs on it. Regards, Laurent De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Gaël Blondelle Hi Laurent, Got to see Papyrus migrating to Tycho. Will you also get a HIPP instance and a deployment on Sonar? It would be interesting for the work we do on project maturity assessment in the context of PolarSys. Le 18 avr. 2014 à 13:55, WOUTERS Laurent <Laurent.WOUTERS@xxxxxx> a écrit :
Hello all, We are currently preparing the migration of Papyrus build process from Buckminster to Tycho. There are a few things that Papyrus developers need to know. 1) There
are now three builds in Papyrus, one for the main components, one for the extras components and the last one called ‘dev’ for the developer components. The top-level build tasks in Papyrus are the ‘releng/top-pom-*.xml’ files. 2) To
add or remove a plugin/feature from a build: a. add
it to an existing feature that is already in the build. Top features are: i. Main:
features\papyrus-main-features\org.eclipse.papyrus.sdk.feature ii. Extras:
features\papyrus-extra-features\org.eclipse.papyrus.extra.feature iii. Dev:
features\papyrus-dev-features\org.eclipse.papyrus.dev.feature b. At
the root of the Papyrus repo, run the command ‘python releng/toolkit/tycho-generator.py’. This will generate the appropriate Tycho configuration (pom.xml file) for the new bundles and update the build tasks when new bundles
are added or removed. You can modify the generated pom.xml of your bundles, they are not overwritten by the generator. For those on Linux or Cygwin you can use the ‘--color’ option to use colors in the console. Hope this helps. Laurent _______________________________________________ |
