Wed Jan 15 09:17:21 EST 2020

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

Affected Versions:

jbosstools 4.14.0.AM1
devstudio  12.14.0.AM1

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

Detail / Summary:

updated: 
simrel 20191218-1000-Simrel.2019-12
orbit R20191126223242
m2e 1.14.0.20191209-1925
dtp 1.14.105.201911250848
tm 4.5.102.201911240504
jetty 9.4.25.v20191220
webtools R-3.16.0-20191210070716
docker 4.5.0.201912091550
swtbot 2.9.0.201909110845
reddeer 2.8.0
lsp4e 0.13.0
testng 7.0.0.201908240652
jgit 5.6.0.201912101111-r
cameltooling 1.0.0.202001061453

added:
wildwebdeveloper 0.7.2.201911151547
m2e-chromatic 1.0.1

removed: 

Related JIRA(s):

https://issues.redhat.com/browse/JBIDE-26972

Pull Request(s):

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

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.14.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.14.0.AM1-SNAPSHOT       -Dtpc.targetKind=multiple

For Central, fetch sources from jbosstools-discovery, then build as above.

----------