[
https://issues.jboss.org/browse/JBIDE-10136?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10136:
-------------------------------
Description:
Since we have taken the time to build a Jenkins job for building osgi stuff w/ maven/tycho
from GitHub sources + JBT parent pom...
why not use that to build the OpenShift Express features/plugins (the JBT component)
instead of having sources in SVN?
I would suggest that the client be one github project and the tooling be second (unless
you want them in the same repo @ github?)
Move OpenShift Express component to github
------------------------------------------
Key: JBIDE-10136
URL:
https://issues.jboss.org/browse/JBIDE-10136
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
Since we have taken the time to build a Jenkins job for building osgi stuff w/
maven/tycho from GitHub sources + JBT parent pom...
why not use that to build the OpenShift Express features/plugins (the JBT component)
instead of having sources in SVN?
I would suggest that the client be one github project and the tooling be second (unless
you want them in the same repo @ github?)
--
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