[jbosstools-issues] [JBoss JIRA] (JBIDE-9935) Make openshift server its own servertype not requiring an runtime
[
https://issues.jboss.org/browse/JBIDE-9935?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen resolved JBIDE-9935.
----------------------------------------
Resolution: Done
that problem is not related to jboss tools.
The modules.jsp is not supposed to be there and will be removed in next update of
openshift server side.
The fact you fix it by setting the server as runtime just means the dependencies become
available to your project. The proper fix for that is it make the pom.xml have that
dependency or remove the modules.jsp.
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.M5
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