[jbosstools-dev] Proposed changes to target platform 4.60.Alpha1-SNAPSHOT: move to Neon.0.M7 plus 8 other changes

[Alexey Kazakov]

OK. This PR is about JBoss Tools TP. Not devstudio.
+1 for that.
Let's discuss devstudio + vagrant tools separately.
Sorry for this confusion.

On 05/09/2016 05:05 PM, Alexey Kazakov wrote:
> It looks like I'm late. There are so many emails this days so I keep 
> missing important ones.
> But I did reacted in JIRA and a separate email thread started by 
> Xavier - 
> https://issues.jboss.org/browse/JBIDE-21861?focusedCommentId=13201849&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13201849
> I don't think we should update our TP to include the vagrant tooling 
> until we have some clarification from Alex Kurtakov and Todd.
>
> ...OK. While I was writing this email I got a notification that Todd 
> approved this trello card - 
> https://trello.com/c/a661NfOB/135-devstudio-include-vagrant-tolling-to-devstudio
> I'm still not sure about these vagrant tooling because I didn't try it 
> and would like to chat a bit with Alex Kurtakov but it looks like the 
> PR has been already merged.
> OK let keep it in our TP and see if it's good enough.
>
> Thanks.
>
> On 05/06/2016 03:50 PM, Nick Boldt 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.Alpha2 / JBDS 10.0.0.Alpha2).
>>
>> https://github.com/jbosstools/jbosstools-target-platforms/pull/206
>>
>> Changes:
>>
>> JBIDE-22200 move up to Neon.0.M7
>> JBIDE-22257, 22256, 22273 remove e4.ui.importer and related stuff
>> JBIDE-21066 update tm.terminal
>> JBIDE-21861 update docker tools
>> JBIDE-21105 remove birt
>> JBIDE-21621 update red deer
>> JBIDE-21861 update docker tooling and add vagrant
>> JBIDE-22196 add org.eclipse.recommenders.snipmatch.rcp feature
>> JBIDE-21439 add JSON editor org.eclipse.wst.json features
>>
>>
>> p2diff reports are attached to JBIDE-22200.
>>
>> ---
>>
>> Please review the above PR(s), as they will be applied *early next
>> week* as part of Sprint 114 toward Alpha2.
>>
>> I will be on PTO May 7-15 but this PR can be applied in my absence by
>> Mickael & built here [1], with results automatically updated here
>> [2],[3].
>>
>> [1] 
>> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix/
>> [2] 
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.60.0.Alpha1-SNAPSHOT/REPO/
>> [3] 
>> https://devstudio.jboss.com/targetplatforms/jbdevstudiotarget/4.60.0.Alpha1-SNAPSHOT/REPO/
>>
>> 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/206/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
>>
>