[jbosstools-dev] Proposed change to JBoss Central 4.40.0.Beta3-SNAPSHOT target platform: updated version of PMD & removal of duplicate content already in upstream TP

[Nick Boldt]

Here is a proposal for a change to the JBoss Central 
4.40.0.Beta3-SNAPSHOT target platform:

1. https://github.com/jbosstools/jbosstools-download.jboss.org/pull/368

2. https://github.com/jbosstools/jbosstools-discovery/pull/168

It consists in the following change:

* JBIDE-14971 Generate Abstract Syntax Tree fails - so update to PMD 4.0.3

I would also like to push this PR, which resolves missing upstream 
dependencies by merging the Central (and new Central Early Access TP) 
with the JBT TP.

https://github.com/jbosstools/jbosstools-discovery/pull/167

It consists of the following change:

* JBIDE-17560 use JBTIS style of TP merging for JBT Central and Early 
Access TPs, in order to reduce dupe entries in the TPs

--

p2diff report:

< net.sourceforge.pmd.eclipse.feature.group [4.0.2.v20131031-1124]
< net.sourceforge.pmd.eclipse.feature.jar [4.0.2.v20131031-1124]
< net.sourceforge.pmd.eclipse.plugin [4.0.2.v20131031-1124]
 > net.sourceforge.pmd.eclipse.feature.group [4.0.3.v20140427-0831]
 > net.sourceforge.pmd.eclipse.plugin [4.0.3.v20140427-0831]
 > net.sourceforge.pmd.eclipse.feature.jar [4.0.3.v20140427-0831]

--

Please review the above PR(s), as it will be applied in the next *2 days*.

(If there are no objections to the above PRs, I will push in PR 169, 
which combines both into a single merged PR.)

https://github.com/jbosstools/jbosstools-discovery/pull/169

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

Build target-platform:

   $ cd jbosstools-discovery
   $ git fetch nickboldt JBIDE-14971_merged
   $ git checkout FETCH_HEAD

To build and verify, perform these steps:

https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files

Or use this script:

https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/verifyTarget.sh

--

Once you've built the target platform you can use it as the back end to 
Central like this:

https://github.com/jbosstools/jbosstools-discovery/blob/master/README.discovery.sites.adoc

(Or you can just install from the target platform site directly into 
Eclipse / JBDS, which is much easier but the same UI experience.)

--

If you want to perform a scripted install of the entire target platform
into your local Eclipse or JBDS instance, you can now do so with this
script:

https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/verifyTarget.sh

Usage is documented in the above script, and in this README:

https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc#update-versions-of-ius-in-the-target-files


-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com