[jbosstools-issues] [JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13074138#comment-13074138 ] 

Nick Boldt commented on JBDS-3384:
----------------------------------

Your list are the same IUs that we include in our Beta1 TP. You shouldn't need to pick them from the mars mirror, but from our TP directly.

https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbosstools/multiple/jbosstools-multiple.target#L284-L300

Note that if you include connector.local, you also need org.eclipse.cdt.native.feature.group.

> Investigate how the terminal changes in Mars will/should  affect us
> -------------------------------------------------------------------
>
>                 Key: JBDS-3384
>                 URL: https://issues.jboss.org/browse/JBDS-3384
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Task
>          Components: build, forge, openshift
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 9.0.0.Beta2
>
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)