[ https://issues.jboss.org/browse/JBIDE-11645?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11645: ------------------------------------- Um... this seems a little strange... is there anything else you can add here? Does the workaround commit fix it? -- 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-11645?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-11645: ---------------------------------------- Fix Version/s: 3.3.0.CR1 (was: 3.3.0.Beta3) Priority: Blocker (was: Critical) This issue is same as JBIDE-10803 -- 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-11645?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-11645: ------------------------------------- The only way I can see to fully solve this problem would be to create an o.j.i.e.as.core.api plugin or something similar. In this way, clients would be able to use standard WTP api's and cast to appropriate interfaces. If the clients (in this case ws) only consumed the api client, then no implemention would be installed. So it wouldn't install any of astools except this api plugin. Everything would compile, but users would not be able to create *any* server. I'm hesitant to add yet another plugin with a poorly defined scope. The other alternative is that ws declares a full dependency on all of astools. A usage scan on ws to see what they're using in astools shows the following: 1) classpath superclasses that I've been meaning to mvoe into common after a common re-org 2) hard-coded string properties and server prefix id's (so not a dependency, just a string match) 3) Their test plugin pulls in astools, understandably. BUild Team: if the plugins themselves had no dependency on the plugin, but the tests did, I assume this would stop pulling in any astools plugins, and thus not have a half-complete astools? -- 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-11645?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11645: ---------------------------------------- {quote} Rob, are you asking if installing AS feature fixes the problem? Yes it does. {quote} WS features should specify a dependency on org.jboss.tools.runtime.as.detector.feature (or any other necessary feature that does not come directly through a classpath resolution from bundles' MANIFEST.MF). Just add the following to your feature.xml: {code} <requires> <import feature="org.jboss.tools.runtime.as.detector.feature" /> </requires> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11645?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-11645. --------------------------------- Assignee: Rob Stryker (was: Brian Fitzpatrick) Resolution: Done I've just verified this is not replicatable. My methodology is as follows: 1) download and install eclipse-testing-juno-linux-gtk-x86_64.tar.gz 2) use alpha2 update site 3) install jbt webservices and jaxrs features (including m2e integration) 4) restart eclipse 5) try to create a new server At step 5, NO servers are available. The servers view *does* load, but NO server adapters are available. Zero. I believe this is intentional and correct. One of the plugins required org.eclipse.wst.server.core, for servertools api, but neither astools nor wtp generic servers were installed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11645?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič commented on JBIDE-11645: ------------------------------------------- It seems that in 3.3.0 Beta3, there was some as dependency in ws feature, but was not sufficient - reason of the original issue. However, now in 4.0.0 Alpha2, there is no dependency on as tools at all. Weird. Definitely will ask Brian. In every case, original issue was resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira