[jbosstools-issues] [JBoss JIRA] (JBIDE-9907) wrap discovery plugin in feature so it can be published but not installed / exposed; hide from update site UI

[ https://issues.jboss.org/browse/JBIDE-9907?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9907: ----------------------------------- OK, so here's what we have now: http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.0.M4/centra... -> http://download.jboss.org/jbosstools/updates/development/indigo/jbosstool... (manually placed there for now w/ manually placed jar committed to SVN) http://svn.jboss.org/repos/jbosstools/trunk/central/plugins/org.jboss.too... -> http://download.jboss.org/jbosstools/updates/nightly/trunk/jbosstools-dir... These jobs will control creation of replacement xml and jar: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--ce... https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggre... When it's time to push M4 into development/indigo folder, I just need to remember to update https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool... to point at jar included in the M4 aggregate site. -- 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