[jbosstools-dev] Proposed 4.13.0.AM1-SNAPSHOT target platform change(s): simrel 2019-09.M1 orbit S20190709113129 cameltooling 1.0.0.201907261207 lsp4e 0.11.0.201907261639 webtools 3.15.0.M1-20190717080107 mylyn 3.25.0.v20190328-1711 m2e 1.13.0.20190716-1624 tm 4.5.102.201907301734 docker 4.4.0.201907301937 reddeer 2.7.0.M1

[jmaury at redhat.com]

Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms.

Affected Versions:

jbosstools 4.13.0.AM1
devstudio  12.13.0.AM1

jbt/ds  TPs 4.13.0.AM1-SNAPSHOT 
central TPs 4.13.0.AM1-SNAPSHOT

Detail / Summary:

simrel 2019-09.M1
orbit S20190709113129
cameltooling 1.0.0.201907261207
lsp4e 0.11.0.201907261639
webtools 3.15.0.M1-20190717080107
mylyn 3.25.0.v20190328-1711
m2e 1.13.0.20190716-1624
tm 4.5.102.201907301734
docker 4.4.0.201907301937
reddeer 2.7.0.M1


Related JIRA(s):

https://issues.jboss.org/browse/JBIDE-26715

Pull Request(s):

https://github.com/jbosstools/jbosstools-target-platforms/pull/328

p2diff Report(s):

(will attach to JIRA when available)

----------

Please review the above changes, as they have been applied and are building today.

Once the target platform is built, jobs and parent pom will be updated to point 
TARGET_PLATFORM_VERSION_MAX at the new version, 4.13.0.AM1-SNAPSHOT.

You can use the following to build & test the target platforms locally against
your component(s).

Build target-platform:

    cd /path/to/jbosstools-target-platforms
    git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
    # or, using hub for git
    git checkout <pull-request-URL>

    mvn clean install -f jbosstools/multiple/pom.xml

Then, to test the new multiple target platform against your component's build:

    cd /path/to/your/jbosstools-component

    mvn clean verify -Dtpc.version=4.13.0.AM1-SNAPSHOT       -Dtpc.targetKind=multiple
      
For Central, fetch sources from jbosstools-discovery, then build as above.

----------