[jbosstools-issues] [JBoss JIRA] (JBIDE-19162) add new plugins to openshift pom and create feature

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-19162:
---------------------------------------------

[~nickboldt] this is no different than IS having Savara in tools  but not in devstudio not that earlyaccess Angular connector installs additional plugin to non-earlyaccess angular. Same concept. we've done this before and will do so in future.

And there are no different proxywizards for Openshift v2 or v3. It just means v3 is not enabled in JBDS for now.

please remember that connector id != single features/plugins but more connector id = "plugins related to certain functionality"

what we do not want is that devstudio using a *different* connection id for the same functionality as tools - this is what was initially suggested for JBTIS connectors and *that* would screw things up.  Here we use the same connectorid and dependent on earlyacces or not, tools or devstudio what it can/will install is variable. 

> add new plugins to openshift pom and create feature
> ---------------------------------------------------
>
>                 Key: JBIDE-19162
>                 URL: https://issues.jboss.org/browse/JBIDE-19162
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Andre Dietisheim
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.3.0.Alpha1
>
>
> In JBIDE-19048 we created new plugins for the OpenShift v3 tooling and moved reusable parts to common plugins. We now need to get the maven build working (add the new modules) and create a v3 feature.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)