[jbosstools-issues] [JBoss JIRA] (JBIDE-22516) NoStackTrace in AbstractModuleSlotUtil.ensureInCache

[ https://issues.jboss.org/browse/JBIDE-22516?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22516: --------------------------------------- [~marcel.bruch], thanks for the reply! I was about to write to you and jbosstools-dev, so now I don't have to :) Auto actions - that's exactly what I was looking for - I didn't see it. One more question: What exactly does it mean when the auto action is set to look for Bundle namespace org.jboss.ide of some version? Does it mean that any of the bundles installed, that fits org.jboss.ide.* can trigger this? Because that wouldn't be desirable in this case. Most bundles under org.jboss.ide are 3.2 right now, but some are 3.6, that would mean that this could be reopened wrongly. {code} $ find devstudio-10.0.1-5663 -name 'org.jboss.ide*'|grep plugins devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.archives.core_3.6.101.v20160607-2122 devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.archives.core_3.6.101.v20160607-2122/META-INF/maven/org.jboss.tools.archives.plugins/org.jboss.ide.eclipse.archives.core devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.archives.jdt.integration_3.6.101.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.archives.ui_3.6.101.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.archives.webtools_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.classpath.core_3.2.1.v20160628-1916.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.classpath.ui_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.core_3.2.1.v20160705-0521.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.dmr_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.doc.user_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.jmx.integration_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.management.as7_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.management.core_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.management.wildfly9_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.rse.core_3.2.1.v20160624-1543.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.rse.ui_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.ui.mbeans_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.ui_3.2.1.v20160616-2135.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.wtp.core_3.2.1.v20160624-1543.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.as.wtp.ui_3.2.1.v20160607-2122.jar devstudio-10.0.1-5663/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.ide.eclipse.freemarker_1.5.101.v20160714-1706.jar {code} So in this case should the Bundle namespace field be set to org.jboss.ide.eclipse.as.classpath.core ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)