From 988a8e2e113f89ccdbfa6f990b97f98409acdb1c Mon Sep 17 00:00:00 2001 From: Mat Booth Date: Fri, 15 Feb 2019 10:13:45 +0000 Subject: [PATCH] Regenerate with runtime dependencies --- tycho.yaml | 169 ++++++++++++++++++++++++++++++++--------------------- 1 file changed, 102 insertions(+), 67 deletions(-) diff --git a/tycho.yaml b/tycho.yaml index edaa2db..259a903 100644 --- a/tycho.yaml +++ b/tycho.yaml @@ -2,70 +2,105 @@ document: modulemd version: 2 data: - summary: >- - Plugins and extensions for building Eclipse plugins and OSGI bundles with Maven - description: >- - Tycho is a set of Maven plugins and extensions for building Eclipse plugins and - OSGI bundles with Maven. Eclipse plugins and OSGI bundles have their own metadata - for expressing dependencies, source folder locations, etc. that are normally found - in a Maven POM. Tycho uses native metadata for Eclipse plugins and OSGi bundles - and uses the POM to configure and drive the build. Tycho supports bundles, fragments, - features, update site projects and RCP applications. Tycho also knows how to run - JUnit test plugins using OSGi runtime and there is also support for sharing build - results using Maven artifact repositories. - - Tycho plugins introduce new packaging types and the corresponding lifecycle bindings - that allow Maven to use OSGi and Eclipse metadata during a Maven build. OSGi rules - are used to resolve project dependencies and package visibility restrictions are - honored by the OSGi-aware JDT-based compiler plugin. Tycho will use OSGi metadata - and OSGi rules to calculate project dependencies dynamically and injects them - into the Maven project model at build time. Tycho supports all attributes supported - by the Eclipse OSGi resolver (Require-Bundle, Import-Package, Eclipse-GenericRequire, - etc). Tycho will use proper classpath access rules during compilation. Tycho supports - all project types supported by PDE and will use PDE/JDT project metadata where - possible. One important design goal in Tycho is to make sure there is no duplication - of metadata between POM and OSGi metadata. - license: - module: - - MIT - dependencies: - - buildrequires: - javapackages-tools: [201801] - platform: [f30] - requires: - platform: [f30] - profiles: - default: - rpms: - - cbi-plugins - - tycho - - tycho-extras - api: - rpms: - - cbi-plugins - - tycho - - tycho-extras - filter: - rpms: - - cbi-plugins-javadoc - - tycho-javadoc - - tycho-extras-javadoc - buildopts: - rpms: - macros: | - %_with_bootstrap 1 - components: - rpms: - cbi-plugins: - buildorder: 10 - ref: master - rationale: Module API. - tycho: - buildorder: 10 - ref: master - rationale: Module API. - tycho-extras: - buildorder: 10 - ref: master - rationale: Module API. - + summary: Plugins and extensions for building Eclipse plugins and OSGI bundles with Maven + description: >- + Tycho is a set of Maven plugins and extensions for building Eclipse plugins and + OSGI bundles with Maven. Eclipse plugins and OSGI bundles have their own metadata + for expressing dependencies, source folder locations, etc. that are normally found + in a Maven POM. Tycho uses native metadata for Eclipse plugins and OSGi bundles + and uses the POM to configure and drive the build. Tycho supports bundles, fragments, + features, update site projects and RCP applications. Tycho also knows how to run + JUnit test plugins using OSGi runtime and there is also support for sharing build + results using Maven artifact repositories. + + Tycho plugins introduce new packaging types and the corresponding lifecycle bindings + that allow Maven to use OSGi and Eclipse metadata during a Maven build. OSGi rules + are used to resolve project dependencies and package visibility restrictions are + honored by the OSGi-aware JDT-based compiler plugin. Tycho will use OSGi metadata + and OSGi rules to calculate project dependencies dynamically and injects them + into the Maven project model at build time. Tycho supports all attributes supported + by the Eclipse OSGi resolver (Require-Bundle, Import-Package, Eclipse-GenericRequire, + etc). Tycho will use proper classpath access rules during compilation. Tycho supports + all project types supported by PDE and will use PDE/JDT project metadata where + possible. One important design goal in Tycho is to make sure there is no duplication + of metadata between POM and OSGi metadata. + license: + module: + - MIT + dependencies: + - buildrequires: + javapackages-tools: [201801] + platform: [f28] + requires: + javapackages-tools: [201801] + platform: [f28] + profiles: + default: + rpms: + - cbi-plugins + - tycho + - tycho-extras + api: + rpms: + - cbi-plugins + - tycho + - tycho-extras + filter: + rpms: + - auto + - auto-factory + - auto-javadoc + - cbi-plugins-javadoc + - decentxml-javadoc + - tesla-polyglot + - tesla-polyglot-atom + - tesla-polyglot-javadoc + - tesla-polyglot-maven-plugin + - tesla-polyglot-translate-plugin + - tesla-polyglot-xml + - tesla-polyglot-yaml + - tycho-extras-javadoc + - tycho-javadoc + buildopts: + rpms: + macros: | + %_with_jp_minimal 1 + %_without_groovy 1 + components: + rpms: + auto: + buildorder: 10 + ref: master + rationale: > + Runtime dependency of cbi-plugins. + cbi-plugins: + buildorder: 30 + ref: master + rationale: > + Module API. + decentxml: + buildorder: 10 + ref: master + rationale: > + Runtime dependency of cbi-plugins, tycho. + ecj: + buildorder: 10 + ref: master + rationale: > + Runtime dependency of tycho. + tesla-polyglot: + buildorder: 10 + ref: master + rationale: > + Runtime dependency of tycho-extras. + tycho: + buildorder: 20 + ref: master + rationale: > + Module API. + Runtime dependency of cbi-plugins, tycho-extras. + tycho-extras: + buildorder: 30 + ref: master + rationale: > + Module API.