November 2013 - jbosstools-issues

[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

2 months, 1 week

2
2
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

4 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

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

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

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

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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16132) XCode library search path is not set properly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16132?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16132: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-aerogear_... shows this was built into #58, which will be picked up in the CR2/GA respin next week. > XCode library search path is not set properly > --------------------------------------------- > > Key: JBIDE-16132 > URL: https://issues.jboss.org/browse/JBIDE-16132 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Critical > Labels: respin-b > Fix For: 4.1.1.CR1 > > > If a Cordova plugin adds a custom framework as a dependency for iOS the project fails to run and the exported XCode project does not compile. > This is because the iOS project generator does not set the library search paths properly for custom frameworks. > Aerogear Push Plugin now uses such a framework. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15999) server New and Noteworthy for 4.1.1.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15999?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-15999. --------------------------------------- Resolution: Rejected no input from [~rob.stryker] and no matches in the jira search. Assuming no changes and rejecting. > server New and Noteworthy for 4.1.1.CR1 > --------------------------------------- > > Key: JBIDE-15999 > URL: https://issues.jboss.org/browse/JBIDE-15999 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15999) server New and Noteworthy for 4.1.1.CR1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15999?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15999. ----------------------------------------- Resolution: Done > server New and Noteworthy for 4.1.1.CR1 > --------------------------------------- > > Key: JBIDE-15999 > URL: https://issues.jboss.org/browse/JBIDE-15999 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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

11 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2013