Re: [jbosstools-dev] Is there a way to tell the difference between a plug-in running in JBDS and one in JBT?

I totally agree, but this seems to be an edge case (gotta love those). The issue is that EGT requires one particular URL for .org and a different one for JBDS. For .org, the repository should show "/drools-guvnor/..." and for JBDS, it should be "/jboss-brms/...". --Fitz _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat ----- Original Message ----- From: "Andersen Max" <max.andersen(a)redhat.com&gt; To: "Brian Fitzpatrick" <bfitzpat(a)redhat.com&gt; Cc: "tools-dev" <jbosstools-dev(a)lists.jboss.org&gt;, "external-exadel-list" <external-exadel-list(a)redhat.com&gt; Sent: Wednesday, May 12, 2010 12:53:47 AM GMT -07:00 US/Canada Mountain Subject: Re: [jbosstools-dev] Is there a way to tell the difference between a plug-in running in JBDS and one in JBT? Platform.getBundle("pluginId") should help you but why would you want to do this ? You shouldn't tie functionality to if a certain osgi plugin is loaded, but to weather a certain extension point or service is available. i.e. Maven integration in jboss tools is separated out in to a separate plugin to ensure it only gets loaded when m2ecipse plugins are around and avoids having a maven dependency to the other plugins (i.e. seam core can be used with maven but doesnt depend) Another way (but should be kept to a minimum) is to use optional dependencies and do a load for the class you want inside a try/catch for NoClassDefFoundError. Then your plugin still loads even if the optional plugin is not available and only fails if you try access these extra classes which you can guard against with the try/catch. The trick here is to ensure you don't references those optional dependencies except for a very few controlled places. /max On May 11, 2010, at 18:08, Brian Fitzpatrick wrote: