[jbosstools-dev] Proposed 4.13.0.AM1-SNAPSHOT target platform change(s): simrel 2019-09.M2 orbit S20190726194335 camel-lsp-client 1.0.0.201908021412 lsp4e 0.11.0.201908151340 docker 4.4.0.201908091806 webtools 3.15.0.M2 jetty 9.4.20.v20190813 mylyn-github 5.4.0.201906121030

[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.M2
orbit S20190726194335
camel-lsp-client 1.0.0.201908021412
lsp4e 0.11.0.201908151340
docker 4.4.0.201908091806
webtools 3.15.0.M2
jetty 9.4.20.v20190813
mylyn-github 5.4.0.201906121030

Related JIRA(s):

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

Pull Request(s):

(already merged - see related JIRA(s))

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.

----------