October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3129) Verify Eclipse Luna SR1 for JBDS 8.0.0

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3129?page=com.atlassian.jira.plugin.... ] Jiri Peterka closed JBDS-3129. ------------------------------ Verified, found this version issue - JBIDE-18539 > Verify Eclipse Luna SR1 for JBDS 8.0.0 > -------------------------------------- > > Key: JBDS-3129 > URL: https://issues.jboss.org/browse/JBDS-3129 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: upstream > Reporter: Mickael Istria > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.CR2 > > Attachments: install_1.png, install_2.png, install_3.png, install_4.png > > > Luna SR1 is to be available on Sept 26th (and ready on Sept 21st): https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR1 > We need to use if for JBDS 8.0 (cf JBIDE-18182). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18539) Eclipse Platform plugin on Luna SR1 is still marked as 4.4.0

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-18539: ------------------------------------ Summary: Eclipse Platform plugin on Luna SR1 is still marked as 4.4.0 Key: JBIDE-18539 URL: https://issues.jboss.org/browse/JBIDE-18539 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, upstream Reporter: Jiri Peterka Fix For: 4.2.1.Final I would expect that for SR1 proper version should be 4.4.1 eclipse/features/org.eclipse.platform_4.4.0.v20140925-0400/ eclipse/plugins/org.eclipse.platform_4.4.0.v20140925-0400/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-3152?page=com.atlassian.jira.plugin.... ] Rastislav Wagner commented on JBDS-3152: ---------------------------------------- [~sgilda] To open cheat sheet manually, right click on project in package or project explorer and select "Open in Cheat Sheets view" > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18461. --------------------------------- The array has been extended. Closing. > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-521) Review JIRA queries in Release Notes

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-521?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-521: ------------------------------------------ [~mmalina], [~ldimaggio] - any input on this? > Review JIRA queries in Release Notes > ------------------------------------ > > Key: TOOLSDOC-521 > URL: https://issues.jboss.org/browse/TOOLSDOC-521 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > > When reviewing RNs for JBDS 8.0.0.CR1, we came to the conclusion that the JIRA queries may need updating. > For reference, here's is discussion between me and Michelle on the subject: > {quote} > 01:23 mmalina: mmurray: I have a question about RN - resolved issues: (project in (JBDS) AND affectedVersion < "8.0.0.CR1" AND fixVersion in ("8.0.0.CR1") OR project in (JBIDE) AND affectedVersion < "4.2.0.CR1" AND fixVersion in ("4.2.0.CR1")) AND type in (Bug) AND resolution in (Done) > 01:24 mmalina: mmurray: why have the fixVersion there? any special reason? > 01:24 mmalina: mmurray: because it's 130 issues vs. 200 without it > 01:24 maxandersen: don't use the < > comparisons. they unforatunely dont work reliably ;/ > 01:26 mmalina: maxandersen: the problem here is there are many jiras without affectedVersion > 01:26 mmalina: *the main problem > 01:26 mmalina: + what you say > 01:27 maxandersen: mmalina: ah yeah. historically affectedVersion is only rarely used. > 01:27 maxandersen: mmalina: only when we got very scifci issues where its important. > 01:30 mmalina: mmurray: my only guess why you have it there is that you wanted to avoid jiras found in CR1 and fixed in CR1 - the thinking being that these would be new in CR1 and not present previously, thus you shouldn't list them in "what's fixed since the previous release". but that reasoning doesn't really work - 90 % bugs found in CR1 were already there before previously ;) any other reason to have it there? > {quote} > Michelle wrote: > {quote} > The search query is a best effort. > The affects version is as you said, to avoid picking up internally identified bugs from QE/team testing CR1respinA that were fixed in CR1respinB, say. The customer doesn't need to know or care about these. > The fixed version is a bit more complicated. The problem is that this query goes into the doc and the search results effectively have to remain static for all time - the doc could be hosted for years to come. This CR1 RNs doc should only list the bugs fixed in the CR1 release. If I leave the fixversion out then when bugs identified in <8.0.0.CR1 get resolved for CR2 or GA or even 9.1.0 they will show up in this query and that screws up the doc. The CR1 RNs doc we get replaced with a GA version so it isn't so important for this one but it is for the GA copy and it's easier to keep basically the same query as I iterate the doc towards GA. > Regards using < and >, they are working effectively from what I can see. To make the comparisons work it just needs the versions to be listed in chronological order on the JBIDE and JBDS jira project pages. > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18528?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-18528: ------------------------------------- well, it did move from CR1 to CR2 - I was just unaware of which location was more correct :-) > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-336) Error after installing JBDS-IS 7.0.3.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-336?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-336: ----------------------------------------- Note that this doesn't cause any other problems. > Error after installing JBDS-IS 7.0.3.GA > --------------------------------------- > > Key: JBTIS-336 > URL: https://issues.jboss.org/browse/JBTIS-336 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 7.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > The following error occurs after installing JBDS-IS 7.0.3.GA from > http://www.qa.jboss.com/binaries/RHDS/updates/stable/kepler/integration-s... > No repository found at file:/home/apodhrad/Projects/jbds-installer/jbds-7.1.1.GA/target/jbdevstudio/studio/configuration/org.eclipse.osgi/bundles/311/data/listener_1925729951/. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17253) Server download wizard: T&Cs failed to be accepted

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17253?page=com.atlassian.jira.plugi... ] Michelle Murray commented on JBIDE-17253: ----------------------------------------- [~dhladky] and [~rob.stryker] - i'm just please you were finally able to track down the issue! > Server download wizard: T&Cs failed to be accepted > -------------------------------------------------- > > Key: JBIDE-17253 > URL: https://issues.jboss.org/browse/JBIDE-17253 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Rob Stryker > Fix For: 4.2.0.Final > > Attachments: Server_downloadT&C.png > > > 1. In Download Runtimes wizard, on JBoss.org Terms and Conditions page. > 2. Select 'Australia'. > 3. Click 'Accept Now'. > >> Error message= Unable to accept terms and conditions: Server returned HTTP response code: 400 for URL: https://www.jboss.org/download-manager/rest/tc-accept > >> Screenshot attached > Unable to proceed any further with download wizard. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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: ---------------------------------- That's because files starting with dot are considered hidden on unix-like systems and your open file dialog is not configured to show hidden files. For example on Linux with KDE you can right click on some empty space and check "Show hidden files". > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18501) JMX Navigator never clean up Local Processes nodes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18501?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18501. --------------------------------- I have never really seen this problem myself, but I verified the fix with the given test case (both with CR1 and CR2) and it is fixed now. Verified in JBDS 8.0.0.CR2 B286. > JMX Navigator never clean up Local Processes nodes > -------------------------------------------------- > > Key: JBIDE-18501 > URL: https://issues.jboss.org/browse/JBIDE-18501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Environment: Linux, x86_64, Java 7 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: jmx-navigator.png > > > After running JBT couple days without restart JMX Navigator gets stuffed with old local processes (see attached picture [^jmx-navigator.png]. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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