[jbosstools-dev] Proposed changes to target platform 4.60.0.Alpha1-SNAPSHOT: Neon M3 & WTP 3.8M3 // who uses org.eclipse.core.runtime.compatibility ?

[Nick Boldt]

Additionally, we need to update m2e from 1.6.2 to 1.7.0, so I've added
one extra commit to the original PR for this change.

https://github.com/jbosstools/jbosstools-target-platforms/pull/173

Details:

* JBIDE-21106: Update to m2e 1.7 and m2e-wtp 1.3


On Mon, Nov 16, 2015 at 10:11 PM, Nick Boldt <nboldt at redhat.com> wrote:
> Yes, https://issues.jboss.org/browse/JBIDE-20976 - copied and pasted
> incorrectly.
>
> Re: PR not being able to build, I've added a couple commits (egit,
> birt, and some jetty stuff). Details in the PR and the JIRA.
>
> Still resolving JBT TP again in order to produce a clean p2diff. Will
> update JIRA when it's done.
>
> On Mon, Nov 16, 2015 at 7:56 PM, Denis Golovin <dgolovin at exadel.com> wrote:
>> Nick,
>>
>> you mean JBIDE-20976, don't you?
>>
>> I cannot build TP after this PR is applied.
>> Please, see my comments in JIRA.
>>
>> Denis
>>
>> On Mon, Nov 16, 2015 at 3:23 PM, Nick Boldt <nboldt at redhat.com> wrote:
>>>
>>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
>>> Developer Studio 4.60.0.Alpha1-SNAPSHOT target platforms (for JBT
>>> 4.4.0.Alpha1 / JBDS 10.0.0.Alpha1).
>>>
>>> https://github.com/jbosstools/jbosstools-target-platforms/pull/173
>>>
>>> It consists of the following changes:
>>>
>>> * JBIDE-19776: Neon M3 & WTP 3.8 M3
>>>
>>> p2diff report will be attached to the above JIRA when it's available;
>>> but since this is only a version change, the only noteworthy change
>>> other than upversioning from M2 will *hopefully* be this:
>>>
>>> * remove org.eclipse.core.runtime.compatibility as it's not in Neon
>>> anymore. Do we need it?
>>>
>>> ---
>>>
>>> Please review the above PR(s), as it will be applied in the next
>>> couple days. 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/173/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
>>>
>>> --
>>> Nick Boldt :: JBoss by Red Hat
>>> Productization Lead :: JBoss Tools & Dev Studio
>>> http://nick.divbyzero.com
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>> --
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>>> confidential. If you are not the intended recipient you are hereby
>>> notified
>>> that using, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly prohibited. If you have received
>>> this email in error please notify the sender and delete this email.
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This email and files attached to it are
>> confidential. If you are not the intended recipient you are hereby notified
>> that using, copying, distributing or taking any action in reliance on the
>> contents of this information is strictly prohibited. If you have received
>> this email in error please notify the sender and delete this email.
>
>
>
> --
> 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
http://nick.divbyzero.com