[jbosstools-dev] Proposed 4.61.0.AM2-SNAPSHOT target platform change(s): Update to m2e 1.7.1.20161026-1743, m2e-wtp 1.3.2.20161026-1738, m2e-apt 1.3.0.201610261805 in both 4.60.x and 4.61.x branches for jbosstools and devstudio TPs

[nboldt at redhat.com]

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

Affected Versions:

jbosstools 4.4.2.AM3-SNAPSHOT
devstudio  10.2.0.AM3-SNAPSHOT

jbt/ds  TPs 4.61.0.AM2-SNAPSHOT 
central TPs 4.61.0.AM1-SNAPSHOT

Detail / Summary:

Update to m2e 1.7.1.20161026-1743, m2e-wtp 1.3.2.20161026-1738, m2e-apt 1.3.0.201610261805 in both 4.60.x and 4.61.x branches for jbosstools and devstudio TPs

Related JIRA(s):

https://issues.jboss.org/browse/JBDS-4136

Pull Request(s):

https://github.com/jbosstools/jbosstools-target-platforms/pull/239
https://github.com/jbosstools/jbosstools-target-platforms/pull/240

p2diff Report(s):

(will attach to JIRA when available)

----------

Please review the above changes, as they will be applied as soon as possible - 
usually within 48 hours for big changes, or 2 hours for simple version bumps.

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

----------