November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13061) Freemarker ui tests are failing on JDK 1.7

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13061: ------------------------------------ Summary: Freemarker ui tests are failing on JDK 1.7 Key: JBIDE-13061 URL: https://issues.jboss.org/browse/JBIDE-13061 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 4.0.0.Beta2 Reporter: Jiri Peterka Assignee: Jiri Peterka Fix For: 4.0.0.Beta2 There is a profile wrongly set AWT toolkit in https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... -- 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

1 week, 1 day

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6878) Seam does not work with JSF 2.0 faces-config.xml

by Alexey Kazakov (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBIDE-6878 URL: https://jira.jboss.org/browse/JBIDE-6878 Project: Tools (JBoss Tools) Issue Type: Bug Components: UpStream Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x This is an issue of Seam runtime. See https://jira.jboss.org/browse/JBSEAM-4637 But let's have a duplicate it in JBT JIRA to track JBSEAM-4637 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 weeks, 6 days

3
5
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {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

1 month, 3 weeks

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Jim Tyrrell (JIRA)

Console not showing up when staritng a EAP/SOA-P Instance --------------------------------------------------------- Key: JBDS-983 URL: https://jira.jboss.org/jira/browse/JBDS-983 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.M4 Reporter: Jim Tyrrell For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 months, 1 week

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 months, 1 week

3
7
0 / 0

[JBoss JIRA] (JBIDE-11614) Non-labeled Checkboxes in property dialogs have weird selection rectangle

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11614?page=com.atlassian.jira.plugi... ] Victor Rubezhny edited comment on JBIDE-11614 at 11/30/13 2:29 PM: ------------------------------------------------------------------- I've proposed a fix for checkboxes with empty labels to SWT/GTK org.eclipse.swt.widgets.Button class. The Button class is changed to control the visibility of box, label and image widgets due to hide all the three widgets in case of empty label and image at the same time. The commit is pushed to Gerrit here: https://git.eclipse.org/r/19165 was (Author: vrubezhny): I've proposed a fix for checkboxes with empty labels to SWT/GTK org.eclipse.swt.widgets.Button class. The Button class is changed to control the visibility of box, label and image widgets due to hide all the three widgets in case of empty label and image at the same time. The commit is pushed to Gerrit here: https://git.eclipse.org/r/19165 > Non-labeled Checkboxes in property dialogs have weird selection rectangle > ------------------------------------------------------------------------- > > Key: JBIDE-11614 > URL: https://issues.jboss.org/browse/JBIDE-11614 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, upstream > Affects Versions: 3.3.0.Beta3 > Environment: Linux > Reporter: Jaroslav Jankovič > Assignee: Victor Rubezhny > Fix For: LATER > > Attachments: 01_issue.png, workaround.jpg > > > Add CDI facet for some project. Click on 'Further configuration available'. Dialog provides checking/unchecking generating beans.xml file. Next to this checkbox there is some invisible selected rectangle. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11614) Non-labeled Checkboxes in property dialogs have weird selection rectangle

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11614?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-11614: ----------------------------------------- I've proposed a fix for checkboxes with empty labels to SWT/GTK org.eclipse.swt.widgets.Button class. The Button class is changed to control the visibility of box, label and image widgets due to hide all the three widgets in case of empty label and image at the same time. The commit is pushed to Gerrit here: https://git.eclipse.org/r/19165 > Non-labeled Checkboxes in property dialogs have weird selection rectangle > ------------------------------------------------------------------------- > > Key: JBIDE-11614 > URL: https://issues.jboss.org/browse/JBIDE-11614 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, upstream > Affects Versions: 3.3.0.Beta3 > Environment: Linux > Reporter: Jaroslav Jankovič > Assignee: Victor Rubezhny > Fix For: LATER > > Attachments: 01_issue.png, workaround.jpg > > > Add CDI facet for some project. Click on 'Further configuration available'. Dialog provides checking/unchecking generating beans.xml file. Next to this checkbox there is some invisible selected rectangle. -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16032: ------------------------------ Fix Version/s: 4.1.1.Final (was: 4.1.1.CR1) > java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences > --------------------------------------------------------------------- > > Key: JBIDE-16032 > URL: https://issues.jboss.org/browse/JBIDE-16032 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Environment: Linux > Reporter: Pavol Srna > Assignee: Koen Aers > Labels: respin-a, respin-b > Fix For: 4.1.1.Final > > Attachments: forge-preferences.png > > > Stacktrace: > {code} > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171) > at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16166) Growl message does not appear or disappears prematurely

by Koen Aers (JIRA)

Koen Aers created JBIDE-16166: --------------------------------- Summary: Growl message does not appear or disappears prematurely Key: JBIDE-16166 URL: https://issues.jboss.org/browse/JBIDE-16166 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.1.1.CR1 Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.1.1.Final, 4.2.0.Alpha1 -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16161: --------------------------------------- I have added the org.eclipse.e4.rcp dependency to the arquillian tests - https://github.com/jbosstools/jbosstools-arquillian/commit/2bb677f3d4e190... Adding the org.eclipse.osgi.compatibility.state fragment isn't enough. The arquillian component now builds correctly - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... I have also tested the webservices component (JBIDE-16137). The build is very slow when the compatibility fragment isn't included. It is faster, but contains failed tests when the compatibility fragment is included. The build is fast and all the tests pass when including the o.e.e4.rcp feature. > Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna > ------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Mickael Istria > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- 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

12 years, 4 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 November 2013