October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18535: --------------------------------------------- notice how in screnshot-1.png you can see AND use the cheatsheet. in screenshot-2.png you can see the cheastsheet (if you have big enough screen) but cannot use the screensheet (can't scroll, can't reread, can mark the actions done etc.) > Opening of wizards from forge cheatsheet does not result in "attached cheatsheet" > --------------------------------------------------------------------------------- > > Key: JBIDE-18535 > URL: https://issues.jboss.org/browse/JBIDE-18535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, project-examples > Reporter: Max Rydahl Andersen > Attachments: screenshot-1.png, screenshot-2.png > > > I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective. > But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18535: ---------------------------------------- Attachment: screenshot-2.png > Opening of wizards from forge cheatsheet does not result in "attached cheatsheet" > --------------------------------------------------------------------------------- > > Key: JBIDE-18535 > URL: https://issues.jboss.org/browse/JBIDE-18535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, project-examples > Reporter: Max Rydahl Andersen > Attachments: screenshot-1.png, screenshot-2.png > > > I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective. > But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18535: ---------------------------------------- Attachment: screenshot-1.png > Opening of wizards from forge cheatsheet does not result in "attached cheatsheet" > --------------------------------------------------------------------------------- > > Key: JBIDE-18535 > URL: https://issues.jboss.org/browse/JBIDE-18535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, project-examples > Reporter: Max Rydahl Andersen > Attachments: screenshot-1.png > > > I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective. > But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18288) Quick Fix for NameBinding without Target annotation is disabled

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18288?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18288: ---------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.0.CR2) Setting {{fixVersion}} to {{4.2.1.Final}} since this is not a blocker for {{4.2.0.Final}} > Quick Fix for NameBinding without Target annotation is disabled > --------------------------------------------------------------- > > Key: JBIDE-18288 > URL: https://issues.jboss.org/browse/JBIDE-18288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.CR1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.2.1.Final > > Attachments: Screen Shot 2014-09-10 at 15.30.42.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18498) Display the "development release" alert on all alpha/beta/cr versions

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18498?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18498: ---------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.0.Final) > Display the "development release" alert on all alpha/beta/cr versions > --------------------------------------------------------------------- > > Key: JBIDE-18498 > URL: https://issues.jboss.org/browse/JBIDE-18498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18498) Display the "development release" alert on all alpha/beta/cr versions

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18498?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-18498: ---------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.1.Final) > Display the "development release" alert on all alpha/beta/cr versions > --------------------------------------------------------------------- > > Key: JBIDE-18498 > URL: https://issues.jboss.org/browse/JBIDE-18498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17990. ------------------------------------ I was not able to reproduce either. Closing. > Organize imports does not work for Maven dependencies > ----------------------------------------------------- > > Key: JBIDE-17990 > URL: https://issues.jboss.org/browse/JBIDE-17990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Beta3 > Environment: Oracle JDK 1.8.0_05, Eclipse Luna > Reporter: Harald Wellmann > Assignee: Snjezana Peco > Fix For: 4.2.0.CR2 > > > After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN. > The corresponding Quick Fix is also broken. > It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository. > This is even worse than JBIDE-17724, I'll have to revert to Beta2. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-18535: ------------------------------------------- Summary: Opening of wizards from forge cheatsheet does not result in "attached cheatsheet" Key: JBIDE-18535 URL: https://issues.jboss.org/browse/JBIDE-18535 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge, project-examples Reporter: Max Rydahl Andersen I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective. But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18528) Forge Cheatsheet shows up in wrong location

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18528?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18528: --------------------------------------------- You are seeing the effect of the fix to JBDS-3152 to avoid cheatsheets to crash. And this new location *is* the right place. Putting cheatsheets *on top* of the outline makes it impossible for you to actually use the outline while reading/following the cheatsheet. Thus cheatsheets are by default supposed to be "attached" to the UI, not *on top* of the UI. Similar when you have a cheatsheet running it will attach it self to wizards on the right. I just noticed that Forge wizards are not recognized as wizards so it is not happening for them - i'll open separate bug for that. With respect to your other error your screenshot tells you there is an actual error in error log - please get that info and open *separate* bug please. > Forge Cheatsheet shows up in wrong location > ------------------------------------------- > > Key: JBIDE-18528 > URL: https://issues.jboss.org/browse/JBIDE-18528 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Burr Sutter > > http://screencast.com/t/PpqcupuG > Build id: CR2-v20141006-0415-B286 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3152) Cheatsheet crashes silently when they need to open files

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3152?page=com.atlassian.jira.plugin.... ] Radim Hopp commented on JBDS-3152: ---------------------------------- Hi [~sgilda]! How did you import those projects? If as general maven projects, then I don't think cheatsheet should be opened automatically. Try to import them from JBoss Central. After successfull import from JBoss Central you should be prompted whether you want the cheatsheet to be opened or not. > Cheatsheet crashes silently when they need to open files > -------------------------------------------------------- > > Key: JBDS-3152 > URL: https://issues.jboss.org/browse/JBDS-3152 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS 8.0.0.CR1b, OSX 10.9.4 > Reporter: Fred Bricon > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 8.0.0.CR2 > > > After creating a AngularJS Forge project, the cheatsheet opens, then, after clicking a couple times on the continue buttons, persistence.xml opens but the cheatsheet closes silently. The log shows : > {quote} > org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.SWT.error(SWT.java:4327) > at org.eclipse.swt.widgets.Widget.error(Widget.java:783) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573) > at org.eclipse.swt.widgets.Control.setCursor(Control.java:3659) > at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.runSubItemPerformExecutable(CheatSheetViewer.java:1096) > at org.eclipse.ui.internal.cheatsheets.views.CoreItem$4.linkActivated(CoreItem.java:198) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) > at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) > at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) > at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > {quote} > It used to work at some point, last week. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014