[JBoss JIRA] (JBDS-3030) Spring conflicting handler message after Spring perspective is reset
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3030?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3030:
------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.Beta3)
> Spring conflicting handler message after Spring perspective is reset
> --------------------------------------------------------------------
>
> Key: JBDS-3030
> URL: https://issues.jboss.org/browse/JBDS-3030
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 8.0.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 8.0.0.CR1
>
>
> Conflicting handlers for AUTOGEN:::org.springsource.ide.eclipse.commons.launch.actionSet/org.springsource.ide.eclipse.commons.launch.relaunch.action: {ActionDelegateHandlerProxy(null,org.springsource.ide.eclipse.commons.ui.launch.StopProcessPullDownToolbarDelegate)} vs {ActionDelegateHandlerProxy(null,org.springsource.ide.eclipse.commons.ui.launch.RelaunchProcessPullDownToolbarDelegate)}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (JBIDE-17610) In JBoss Central rename 'Enable Early Access' check box
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17610?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-17610:
-------------------------------------
So I take it we stick with 'Enable Early Access'? (without hyphen)
> In JBoss Central rename 'Enable Early Access' check box
> -------------------------------------------------------
>
> Key: JBIDE-17610
> URL: https://issues.jboss.org/browse/JBIDE-17610
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Labels: early-access
> Fix For: 4.2.0.Beta3
>
>
> The label for the 'Enable Early Access' check box (JBIDE-17392) should be changed.
> It should be labelled 'Show Early Access'.
> * This makes it consistent with the 'Show Installed' check box
> * And by selecting the check box you aren't actually _enabling_ Early Access features - you are merely showing them and still have to install them
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17696:
---------------------------------------
I was playing with it today and I did see job mentioned above taking to much time, but in my case it ended eventually without any exceptions. After that I didn't managed to get it stuck again.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Attachments: jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months