[jbosstools-dev] Proposed 4.16.0.Final-SNAPSHOT target platform change(s): wildwebdeveloper 0.10.0 springide 3.9.13.202006180736-RELEASE docker 4.7.0.202006252201

[sbouchet 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.16.0.Final
devstudio  12.16.0.GA

jbt/ds  TPs 4.16.0.Final-SNAPSHOT 
central TPs 4.16.0.Final-SNAPSHOT

Detail / Summary:

wildwebdeveloper 0.10.0
springide 3.9.13.202006180736-RELEASE
docker 4.7.0.202006252201

Related JIRA(s):

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

Pull Request(s):

(already merged - see related JIRA(s))
https://github.com/jbosstools/jbosstools-build/pull/302
https://github.com/jbosstools/jbosstools-discovery/pull/419
https://github.com/jbosstools/jbosstools-target-platforms/pull/360
https://github.com/jbosstools/jbosstools-build-ci/pull/189
https://github.com/jbosstools/jbosstools-build/pull/302

p2diff Report(s):

attached to JIRA

----------

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.16.0.Final-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.16.0.Final-SNAPSHOT       -Dtpc.targetKind=multiple
      
For Central, fetch sources from jbosstools-discovery, then build as above.

----------