[jbosstools-issues] [JBoss JIRA] (ERT-533) enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]

[Friendly Jira Robot (JIRA)]

Friendly Jira Robot created ERT-533:
---------------------------------------

             Summary: enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]
                 Key: ERT-533
                 URL: https://issues.jboss.org/browse/ERT-533
             Project: Eclipse Release Train
          Issue Type: Task
          Components: WTP Releng
            Reporter: Friendly Jira Robot


As mentioned on https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10522.html WTP uses some sort of versioncheck magic to ensure plugins and features are bumped appropriately.

We might want to switch to use the tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata mojos to ensure correct plugin and feature versioning, by settings stable and staging URLs as baselines.

For this to work, we need two things:

a) all components must build with Tycho 1.0
b) a staging and stable URL must be provided against which to compare versions.

The staging site could be the latest I build or else a committers build, such as one of these, built via the current wtp.releng.aggretor build:

* http://download.eclipse.org/webtools/downloads/drops/R3.10.0/I-3.10.0-20171004000115/
* http://build.eclipse.org/webtools/committers/wtp-R3.10.0-I/20171030195222/I-3.10.0-20171030195222/

It should ultimately be a composite or aggregate site built from the collection of WTP subproject builds.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)