[jbosstools-issues] [JBoss JIRA] (JBIDE-9935) Make openshift server its own servertype not requiring an runtime

Rob Stryker (Resolved) (JIRA) jira-events at lists.jboss.org
Fri Nov 11 08:28:45 EST 2011


     [ https://issues.jboss.org/browse/JBIDE-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-9935.
--------------------------------

    Resolution: Done


The minimal fix for this has been put into place. The editor and launch configuration have limited (read: almost zero) UI features added. These UI features will be added as determined needed. 

Publish works same as before. Run as -> run on server also functions properly. 
                
> Make openshift server its own servertype not requiring an runtime
> -----------------------------------------------------------------
>
>                 Key: JBIDE-9935
>                 URL: https://issues.jboss.org/browse/JBIDE-9935
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.3.0.Beta1
>
>
> Thought it would be good to collect reasons for and against having runtime for openshift server.
> For:
> For basic openshift work I don't really need a local runtime - since I'm just editing raw source and git push will deploy. Having to download and install AS7 should be optional.
> Against:
> Being able to create projects against it as a target would be interesting (but that could just as easily be solved with a local server/runtime combination.)
> How many OpenShift server types would be needed? how do we manage them with respect to facets constraints etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list