[
https://issues.jboss.org/browse/JBIDE-10068?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10068:
---------------------------------------------
Just to explain the reasons for this:
The primary reason why we were moving openshift client code to github was to make it easy
for openshift team and others who are *not* using eclipse nor osgi for their work to pick
it up maintain and use it.
Plus we did not want to spend time setting up hudson ci tycho builds which would need to
change anyway, plus this library would now need to be manually installed and having to
explain this and keeping under control for right branches/trunks just wasn't worth
doing.
And this scenario is *not* the same as teiid/modeshape - teiid/modeshape is a problem
because of the hard coupling of the internal .jar to a specific runtime. This is not the
case of the openshift library - we can and will be able to build and use this jar
independent of any runtime release. Of course if OpenShift server side breaks it breaks us
too but that is independent on where the openshift jar lives.
Thus we (Andre, Rob and me) settled on keeping the .client openshift plugin on jboss tools
side in svn and then just embed the openshift client jar inside it thus not requiring to
change every devs setup and to keep the github client jar simple (non-eclipse/tycho).
Move OpenShift Express client to github
---------------------------------------
Key: JBIDE-10068
URL:
https://issues.jboss.org/browse/JBIDE-10068
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.M4
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
Attachments: openshift-express-client.png
--
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