I've applied the change to Spring IDE in master, but I realized we
have Spring 3.7.0.R, not 3.7.3.CI in 4.3.x so I won't change that
unless commanded to do so. :D
TP changes for 4.3.x should be all done now.
TP changes for master should also be all done... until Neon M6 comes
out in a couple weeks.
On Thu, Mar 10, 2016 at 9:01 AM, Nick Boldt <nboldt(a)redhat.com> wrote:
This change is live, and in fact has been for some time.
But we need to do a similar change [1] in the Central TP, which does two things:
* update from Mars M4 to M5
* update from a pre-release Spring IDE 3.7.3 to their final release version
Reason for the Spring update is that Neon M5 no longer includes all
the SpringIDE requirements (equinox.weaving.*) so I'm now pulling them
directly from the SpringIDE site. And I figured it was time to move up
from a nightly to a release version.
If there are no objections to this change, I'll also update Spring IDE
from 3.7.3.nightly to 3.7.3.RELEASE in JBT 4.3.1 / JBDS 9.1.0.
[1]
https://github.com/jbosstools/jbosstools-discovery/pull/328
On Tue, Mar 1, 2016 at 4:23 PM, Mickael Istria <mistria(a)redhat.com> wrote:
> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
> Developer Studio 4.60.x target platforms.
> *
https://github.com/jbosstools/jbosstools-target-platforms/pull/197
>
> It consists in the following change(s):
> * JBIDE-21386: Create and use Neon M5 target-platform (p2diff at
>
https://issues.jboss.org/browse/JBIDE-21386?focusedCommentId=13170435&...
> )
>
> Please review the above PR(s), as it will be applied next week.
>
>
> You can use the following to build & test the target-platform locally
> against your component(s).
>
> Build target-platform:
> cd /path/to/jbosstools-target-platforms/jbosstools/multiple
> git fetch origin pull/197/head && git checkout FETCH_HEAD
> mvn clean install
>
> 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.60.0.Alpha1-SNAPSHOT
> -Dtpc.targetKind=multiple
>
> If you'd like to build the "unified" target platform and repository
too:
> cd /path/to/jbosstools-target-platforms/jbosstools/multiple
> mvn clean install -Dmultiple2repo # takes looooong
> cd /path/to/jbosstools-target-platforms/jbosstools/unified
> mvn clean install
>
-DtargetRepositoryUrl=file:///path/to/jbosstools-target-platforms/jbosstools/multiple/jbosstools-multiple.target.repo/
>
> Or, to test the new "unified" target platform against your component's
> build:
> cd /path/to/your/jbosstools-component
> mvn clean verify -Dtpc.version=.60.0.Alpha1-SNAPSHOT
>
>
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio