[ https://issues.jboss.org/browse/JBIDE-9907?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9907: ----------------------------------- Still waiting on upstream components to finish churning so we can get a new aggregate build. -- 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

[ https://issues.jboss.org/browse/JBIDE-9907?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9907: -------------------------------------- The org.jboss.tools.central.discovery plugin isn't part of any build/distribution. It can, but doesn't have to be included in any feature, but mustn't be included in a build. It just needs to be built and saved in a location mentioned in the discovery.xml file. The discovery.xml file can contain more such plugins. I have built this plugin and saved it in the http://download.jboss.org/jbosstools/examples/org.jboss.tools.central.dis.... You can create a job to build this plugin when it is changed. If this location isn't an appropriate location, we can change it. The entry in the directory.xml file will also have to be changed. This way, we will be able to add extensions after releasing a distribution. The Eclipse OSGi engine doesn't load this plugin and its version isn't important. It doesn't need a qualifier. It is only important that its name (including its version) matches the name mentioned in the directory.xml file so that the Mylyn discovery engine can find it. JBDS can have other discovery.xml as well as other discovery plugin. We can introduce a new discovery.xml and discovery plugin when changing a release or milestone if a new release/milestone contains different features/extensions that the user could update. M2e uses this way to maintain the discovery feature. Their discovery jar is org.eclipse.m2e.discovery.oss-catalog.jar (there is no such a plugin in the m2e build). They use the Mylyn extension point, but don't use the Mylyn API. This jar is even not an OSGi plugin. STS 2.7.1/2.7.2 uses the com.springsource.sts.discovery-2.7.1.jar, com.tasktop.discovery-3.6.jar and org.eclipse.mylyn.discovery-3.6.jar plugin. No one is included in the build. They use the Mylyn API. STS 2.8.0 uses the com.springsource.sts.discovery-2.8.0.jar, com.tasktop.discovery-3.6.jar and org.eclipse.mylyn.discovery-3.6.jar plugin. They aren't included in the build. The Mylyn distribution also doesn't include their org.eclipse.mylyn.discovery plugin. This plugin doesn't contain source so that you don't need to create any source plugin for it.If you add a non-existing source folder to the build.properties file, the plugin won't be built in the PDE. -- 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

[ https://issues.jboss.org/browse/JBIDE-9907?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-9907: ------------------------------ Comment: was deleted (was: Still waiting on upstream components to finish churning so we can get a new aggregate build.) -- 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

[ 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

[ https://issues.jboss.org/browse/JBIDE-9907?page=com.atlassian.jira.plugin... ] Nick Boldt resolved JBIDE-9907. ------------------------------- Fix Version/s: 3.3.0.M4 (was: 3.3.0.Beta1) Resolution: Done Closing. -- 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