[
https://issues.jboss.org/browse/JBIDE-10068?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10068:
------------------------------------
uh, if people want to fetch github sources and just build the single non-osgi jar, they
TOTALLY can. The "pollution", as you call it, of having this upstream plugin
packaged up as an osgi jar, wrapped w/ a feature, wrapped with a site.xml, published to
our _composite_ site, meant we could consume it like we do any other upstream plugin.
Why is that bad? And why would you rather the overhead of manually committing embedded
jars in SVN when you can just pull them from upstream via our existing Jenkins build
infra? You've railed for years about the suck of Modeshape/Teiid having to commit
binaries into SVN, yet unless I'm mistaken, that's exactly what you're
proposing here.
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