Nick can we also add include to this one below? JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle version 3.2.300.v20120523-2004

> * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, > org.jboss.tools.maven.jbosspackaging.feature, and > org.jboss.tools.common.mylyn.feature to JBoss Central TP

-100 (this just seems very pointless based on current description)

These 6 PRs have been applied, plus a couple more to remove org.jboss.tools.vpe.cordovasim.feature, org.jboss.tools.maven.jbosspackaging.feature, and org.jboss.tools.common.mylyn.feature from JBDS in master and Beta3x. It was only ever in the update site in the "Additional Tools" or uncategorized, so no great loss moving it completely to Central where it belongs.

Updated the container JIRA for this too: https://issues.jboss.org/browse/JBDS-2869 Cheers, Nick New Beta4-SNAPSHOT TPs should be ready for testing in about an hour. > Make that 6, with Denis' additional change. > > -- > > Here is a proposal for *6* changes to the JBoss Tools > 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and > Early Access): > > https://github.com/jbosstools/jbosstools-target-platforms/pull/79 > https://github.com/jbosstools/jbosstools-discovery/pull/185 > https://github.com/jbosstools/jbosstools-discovery/pull/184 > https://github.com/jbosstools/jbosstools-target-platforms/pull/78 > https://github.com/jbosstools/jbosstools-discovery/pull/183 > https://github.com/jbosstools/jbosstools-discovery/pull/182 > > It consists of the following changes: > > * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth > 3.2.300.v20120523-2004 to JBT/JBDS TP > * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, > org.jboss.tools.maven.jbosspackaging.feature, and > org.jboss.tools.common.mylyn.feature to JBoss Central TP > * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) > * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP > * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP > * JBIDE-17742 - Remove EGit from Central Discovery > > -- > > The above PRs have not been applied (to allow time to complain / > reject / pull an even *newer* version of Tern), so you can fetch the > PRs and build the TP locally to test it out: > > Build target-platform: > > $ cd jbosstools-target-platforms > $ git fetch origin 4.40.x > $ git checkout FETCH_HEAD > $ cd jbosstools/multiple > $ mvn clean install -P \!multiple2repo > > Try with just built target-platform: > > $ cd /path/to/your/component > $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT > -Pmultiple.target > > -- > > 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/instal... > > Usage is documented in the above script, and in this README: > > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#upd... > > On 07/02/2014 06:15 PM, Denis Golovin wrote: >> Nick can we also add include to this one below? >> >> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle >> version 3.2.300.v20120523-2004 >> > > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 4 Jul 2014, at 17:30, Max Rydahl Andersen wrote: > On 4 Jul 2014, at 4:33, Nick Boldt wrote: > >> These 6 PRs have been applied, plus a couple more to remove >> org.jboss.tools.vpe.cordovasim.feature, >> org.jboss.tools.maven.jbosspackaging.feature, and >> org.jboss.tools.common.mylyn.feature from JBDS in master and Beta3x. >> It >> was only ever in the update site in the "Additional Tools" or >> uncategorized, so no great loss moving it completely to Central where >> it >> belongs. > > you are talking *ONLY* JBDS here, right ? > > I can still go to jboss tools release and nightly updatesite and install > *all* and get *all* not some > weird subset because someone insist installer = updatesite, right ? :) JBDS-3079 talks only about JBDS so jbosstools is unaffected. Good. I'm *really* not fan of this trend of updatesite content being moved back and forth because of what is in the installer. These things should not be so heavily dependent on each other. /max >> Updated the container JIRA for this too: >> >> https://issues.jboss.org/browse/JBDS-2869 >> Cheers, >> >> Nick >> >> New Beta4-SNAPSHOT TPs should be ready for testing in about an hour. >> >>> Make that 6, with Denis' additional change. >>> >>> -- >>> >>> Here is a proposal for *6* changes to the JBoss Tools >>> 4.40.0.Beta4-SNAPSHOT target platforms (for JBT, JBDS, Central, and >>> Early Access): >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/79 >>> https://github.com/jbosstools/jbosstools-discovery/pull/185 >>> https://github.com/jbosstools/jbosstools-discovery/pull/184 >>> https://github.com/jbosstools/jbosstools-target-platforms/pull/78 >>> https://github.com/jbosstools/jbosstools-discovery/pull/183 >>> https://github.com/jbosstools/jbosstools-discovery/pull/182 >>> >>> It consists of the following changes: >>> >>> * JBDS-3082 add org.eclipse.core.runtime.compatibility.auth >>> 3.2.300.v20120523-2004 to JBT/JBDS TP >>> * JBDS-3079 - add org.jboss.tools.vpe.cordovasim.feature, >>> org.jboss.tools.maven.jbosspackaging.feature, and >>> org.jboss.tools.common.mylyn.feature to JBoss Central TP >>> * JBIDE-17748 - Update Tern.java to 0.4.0.201407021311 in TP(s) >>> * JBIDE-17749 - Update AngularJS to 0.4.0.201407021517 in EA TP >>> * JBIDE-17733 - Update m2e-wro4j to 1.1.0.201406251020 in Central TP >>> * JBIDE-17742 - Remove EGit from Central Discovery >>> >>> -- >>> >>> The above PRs have not been applied (to allow time to complain / >>> reject / pull an even *newer* version of Tern), so you can fetch the >>> PRs and build the TP locally to test it out: >>> >>> Build target-platform: >>> >>> $ cd jbosstools-target-platforms >>> $ git fetch origin 4.40.x >>> $ git checkout FETCH_HEAD >>> $ cd jbosstools/multiple >>> $ mvn clean install -P \!multiple2repo >>> >>> Try with just built target-platform: >>> >>> $ cd /path/to/your/component >>> $ mvn clean verify -Dtpc.version=4.40.0.Beta4-SNAPSHOT >>> -Pmultiple.target >>> >>> -- >>> >>> 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/instal... >>> >>> >>> Usage is documented in the above script, and in this README: >>> >>> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#upd... >>> >>> >>> On 07/02/2014 06:15 PM, Denis Golovin wrote: >>>> Nick can we also add include to this one below? >>>> >>>> JBDS-3082 Include org.eclipse.core.runtime.compatibility.auth bundle >>>> version 3.2.300.v20120523-2004 >>>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools & Dev Studio >>> http://nick.divbyzero.com >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > /max > http://about.me/maxandersen > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen

On 15 Jul 2014, at 17:52, Nick Boldt wrote: > Here is a proposal for 1 change to the JBoss Tools > 4.40.0.Beta4-SNAPSHOT target platform for JBoss Central): > https://github.com/jbosstools/jbosstools-download.jboss.org/pull/383 > https://github.com/jbosstools/jbosstools-discovery/pull/196 > It consists of the following change: > > * JBDS-2956 - Update to Spring IDE 3.6 in Central > > -- > > The above PRs have not been applied (to allow time to complain / reject > / pull an even *newer* version of Tern), one of the above PR's are applied and why is this related to Tern ?

The change looks fine for me, mainly relevant for QE to verify if SpringIDE 3.6 works/fixes the issues.

I don't really see how the above relates to testing of *JBoss Central* target platform ? The above wont work since there is *no* 4.40.Beta4-SNAPSHOT for the actual jbosstools-target-platform.

Aren't you mixing up .target platforms here ?