[ https://issues.jboss.org/browse/JBIDE-10297?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-10297: -------------------------------------- Issue replicated on Ubuntu 11.04 64-bit -- 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-10297?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10297: --------------------------------------------- thats very weird :( -- 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-10297?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-10297: ---------------------------------------- I can reproduce this issue. Weird... -- 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-10297?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10297: --------------------------------------- The issue has been introduced by the IJBoss7ManagerService service. This service is created before the IDE opens the Workspace Launcher dialog. The service starts the as.core plugin. The as.core plugin starts the org.eclipse.core.resources plugin that sets the workspace to the default value if already isn't set to it. Since the workspace is set to the default value, the IDE doesn't open the Workspace Launcher dialog and uses the default workspace. Attached is a patch. -- 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-10297?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-10297: ----------------------------------- Component/s: JBossAS/Servers (was: common/jst/core) -- 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-10297?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-10297: --------------------------------------- Because it is a declarative service. All declarative services are being initialized by the org.eclipse.equinox.ds plugin that starts at startLevel 2 (before all except the system.bundle and org.eclipse.equinox.simpleconfigurator plugin). This issue could be solved in a several way: - make IJBoss7ManagerService doesn't depend on the core.as plugin (not sure if this is doable) - convert it to a non-declarative service and load it lazily - make a workaround as in the proposed patch IMO the third solution is the easiest one. Thread.sleep(500) only happens when the IDE opens the Workspace Launcher dialog and waits for the user to finish the dialog. I think, making it sleep for <=0.5 seconds while waiting for the user input wouldn't make a problem. That happens in a job and will postpone starting the as.core plugin which is what we want. This would also solve some other potential issues that aren't related to this service (when some other code tries to start the as.core plugin too early). -- 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-10297?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-10297. --------------------------------- Resolution: Done This has been implemented using snjezana's patch for m5, though for beta1 we should investigate different solutions to decouple the plugins. -- 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-10297?page=com.atlassian.jira.plugi... ] Rob Cernich commented on JBIDE-10297: ------------------------------------- Is there a reason the services are configured to start immediately? I hand tweaked the service declarations to remove immediate="true" and that seems to have fixed this problem. (I found my way there by way of a warning in the Eclipse log that stated there were two services with the same name. You might want to correct that while you're in there.) Hope that helps. Rob -- 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-10297?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10297: --------------------------------------------- the two services with same name was/is fixed. future fixes for this (i.e. not in M5) goes onto JBIDE-10344 and yes I agree the eager start seems unnecessary. -- 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-10297?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10297 at 12/9/11 4:33 AM: ------------------------------------------------------------------- yep, the "start immediately" options were only set when we faced problems acquiring the service (which then turned out to be caused by other issues). There's afaik no reason for them to start immediately so I'd advocate to remove that option too, since I'm pretty much convinced that this should solve the issue. was (Author: adietish): yep, the "start immediately" options were only set when we faced problems acquiring the services. There's afaik no reason for them to start immediately so I'd advocate to remove that option too, since I'm pretty much convinced that this should solve the issue. -- 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