[jbosstools-issues] [JBoss JIRA] (JBIDE-14000) OpenShift incorrectly listed under JBoss Community in New Server wizard

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-14000:
------------------------------------------

There is a community (Origin) and an pay for version (Enterprise) of OpenShift. I'm not completely sure but afaik there's no way for us to know if we're connecting to a origin/enterprise instance and if, only when the connection is triggered (your screenshot is showing a stage before the connection's done). 
I agree that OpenShift is a Red Hat not a JBoss product and thus we should most likely do a separate cathegory.

@Max: WDYT?
                
> OpenShift incorrectly listed under JBoss Community in New Server wizard
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-14000
>                 URL: https://issues.jboss.org/browse/JBIDE-14000
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift, server
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Michelle Murray
>            Assignee: Rob Stryker
>         Attachments: OpenShift_JBossCommunity.png
>
>
> When creating a new server, OpenShift is listed under JBoss Community. Screen capture attached.
> As far as I know, OpenShift is not a JBoss product - it is marketed solely as Red Hat. And OpenShift is not community - it is maintained by Red Hat and they make money from it.
> So OpenShift doesn't fit under JBoss Community or JBoss Enterprise Middleware. I guess it needs a separate entry.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira