[jbosstools-dev] Proposed changes to target platform 4.52.0.CR1-SNAPSHOT and 4.50.2.CR1-SNAPSHOT: Mars.2.RC4 + AERI, Docker, Easymport, m2e, m2e-apt

Max Rydahl Andersen manderse at redhat.com
Thu Feb 18 17:16:32 EST 2016


On 18 Feb 2016, at 20:41, Nick Boldt wrote:

> Another PR. This one updates the 4.50.x TP to the latest versions 
> noted below:
>
> PR to update 4.50.x TP too:
> https://github.com/jbosstools/jbosstools-target-platforms/pull/196
>
> Changes:
>
> commons.io 2.2
> m2e.apt 1.2
> m2e 1.6.3
> aeri 1.0.0.v20150617-0732 -> 1.100.0.v20160217-0435
> launchbar 1.0.1
> e4.ui.importer 0.2
> docker tools 1.2.1 RC4

I assume this relates to 
https://github.com/jbosstools/jbosstools-target-platforms/pull/195 too ?

+1 to get this into Mars asap so we can get the Aeri stuff tested asap.

Right now it can only run on my machine which is sad :)

/max

> (Also fixed the subject heading of this email.)
>
> On Thu, Feb 18, 2016 at 2:07 PM, Nick Boldt <nboldt at redhat.com> wrote:
>> *Note that the PR may be incomplete (will check for newer stuff than
>> is in Mars, m2e, m2e-atp, and WTP later) but I'm sending this out in
>> advance so people are aware of the forthcoming changes.*
>>
>> --
>>
>> Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
>> Developer Studio 4.52.0.CR1-SNAPSHOT target platforms (for JBT
>> 4.3.1.CR1 / JBDS 9.1.0.CR1).
>>
>> * https://github.com/jbosstools/jbosstools-target-platforms/pull/195
>> * https://github.com/jbosstools/jbosstools-discovery/pull/327
>>
>> It consists of the following changes:
>>
>> * https://issues.jboss.org/browse/JBIDE-21651
>>
>> : update to latest Mars.2.RC4
>> : update to WTP
>> : update to m2e 1.6.3
>> : update to m2e-apt 1.2
>> : update to Docker 1.2.1.201602162146
>> : addition of org.apache.commons.io 2.2.0 (already had 2.0.1, but now
>> need 2.2.0 too to resolve Aeri deps)
>>
>> p2diff reports will be attached to the above JIRA
>>
>> ---
>>
>> Please review the above PR(s), as they will be applied as soon as 
>> possible in
>> preparation for CR1 code freeze.
>>
>> 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/195/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.52.0.CR1-SNAPSHOT
>> -Dtpc.targetKind=multiple
>>
>> --
>> 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
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160218/0cd5c7b7/attachment-0001.html 


More information about the jbosstools-dev mailing list