June 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9284) AS7 launch configuration can not be opened

by Fred Bricon (JIRA)

AS7 launch configuration can not be opened ------------------------------------------ Key: JBIDE-9284 URL: https://issues.jboss.org/browse/JBIDE-9284 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Environment: Indigo, Nightly builds of JBoss AS plugins from trunk Reporter: Fred Bricon Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M3 You can not open the AS7 launch configuration anymore. If you click on the "Open launch configuration" link, nothing happens. But Eclipse's error log shows : {noformat}java.lang.IllegalArgumentException: Argument cannot be null at org.eclipse.swt.SWT.error(SWT.java:4263) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Text.setText(Text.java:2099) at org.jboss.ide.eclipse.as.rse.ui.RSELaunchTabProvider$RSERemoteLaunchTab.initializeFrom(RSELaunchTabProvider.java:126) at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:86) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:194) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:751) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:623) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:640) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:602) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:578) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.initializeContent(LaunchConfigurationPropertiesDialog.java:102) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.createContents(LaunchConfigurationsDialog.java:437) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.create(LaunchConfigurationsDialog.java:368) at org.eclipse.jface.window.Window.open(Window.java:790) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1132) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:203) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:629) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:606) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:588) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) 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.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386){noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9245) rename jboss 6.0 runtime to 6.x

by Rob Stryker (JIRA)

rename jboss 6.0 runtime to 6.x ------------------------------- Key: JBIDE-9245 URL: https://issues.jboss.org/browse/JBIDE-9245 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.M3 JBoss 6.0 servers and runtimes need to be renamed properly to 6.x, since changes within are very tiny and this does not deserve a new server type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9225) JBoss AS Perspective seems irrelevant now - remove ?

by Max Rydahl Andersen (JIRA)

JBoss AS Perspective seems irrelevant now - remove ? ---------------------------------------------------- Key: JBIDE-9225 URL: https://issues.jboss.org/browse/JBIDE-9225 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7666) Quick fix for "Producer method or field cannot be annotated @Inject [JSR-299 §3.3.2, §3.4.2]" error marker

by Daniel Azarov (JIRA)

Quick fix for "Producer method or field cannot be annotated @Inject [JSR-299 §3.3.2, §3.4.2]" error marker ---------------------------------------------------------------------------------------------------------- Key: JBIDE-7666 URL: https://jira.jboss.org/browse/JBIDE-7666 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.x This quick fix should offer next: 1. Delete @Inject annotation 2. Delete @Produces annotation -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9242) jboss-jsf-api deps on a project should trigger JSF

by Max Rydahl Andersen (JIRA)

jboss-jsf-api deps on a project should trigger JSF --------------------------------------------------- Key: JBIDE-9242 URL: https://issues.jboss.org/browse/JBIDE-9242 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 3.3.0.M3 jboss-as-kickstart project in as7 quickstarts has dependency on jboss-jsf-api spec jars but doesn't have JSF enabled. This might be relevant for other spec jars too since the jboss ones are complete, where as the ones in maven central are "incomplete" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9274) Touch descriptors button does not work for AS7

by Libor Zoubek (JIRA)

Touch descriptors button does not work for AS7 ---------------------------------------------- Key: JBIDE-9274 URL: https://issues.jboss.org/browse/JBIDE-9274 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Libor Zoubek Assignee: Rob Stryker Fix For: 3.3.0.M3 Finger button was used to touch web.xml and actually trigger redeployment of war/ear. This does not work on AS7 anymore (web.xml is probably touched, but redeployment works different way). What is the funcionality of this button within AS7? I think we should create .dodeploy file when this button is pressed or it should be disabled at all. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9119) helloworld_mail_testclient does not get preconfigured soa runtime

by Libor Zoubek (JIRA)

helloworld_mail_testclient does not get preconfigured soa runtime ----------------------------------------------------------------- Key: JBIDE-9119 URL: https://issues.jboss.org/browse/JBIDE-9119 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.M1 Reporter: Libor Zoubek Assignee: Snjezana Peco Fix For: 3.3.0.Final Project examples works this way: if examle requires a runtime and user has defined same runtime with different name, runtime is assigned and there is no need to fix it manually. This does not seem to work for some non-faceted projects (helloworld ESB example works fine) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8542) Display remote server log in console view

by Libor Zoubek (JIRA)

Display remote server log in console view ----------------------------------------- Key: JBIDE-8542 URL: https://issues.jboss.org/browse/JBIDE-8542 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.2.0.Final Reporter: Libor Zoubek Assignee: Rob Stryker It would be nice if we were able to redirect remote server's output to console view (same as local server does) Currently developer needs to open terminal and tail -f server's log by hand. It would also help our to run bot tests (that we now run with local servers) with remote server. These test always analyze server's log to determine successful deployment etc. My suggestions is (when server is started via tools): If server is already running: {{cat server.log}}, and than run {{tail -n0 -f server.log}} If it isn't: just {{tail -f server.log}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-1692) Runtime detector plugins are missing

by Libor Zoubek (JIRA)

Runtime detector plugins are missing ------------------------------------ Key: JBDS-1692 URL: https://issues.jboss.org/browse/JBDS-1692 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 5.0.0.M2 Reporter: Libor Zoubek Assignee: Snjezana Peco Priority: Blocker Fix For: 5.0.0.M2 Folder with runtime is searched, but nothing found. There is nothing special in .log. IMHO following features are missing: JBoss Runtime AS Detector org.jboss.tools.runtime.as.detector.feature JBoss Runtime Seam Detector org.jboss.tools.runtime.seam.detector.feature (These ones are present in my JBT 3.3.0.M2) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-8301) Not clear what Start/Stop actually does for remote servers

by Max Rydahl Andersen (JIRA)

Not clear what Start/Stop actually does for remote servers ---------------------------------------------------------- Key: JBIDE-8301 URL: https://issues.jboss.org/browse/JBIDE-8301 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.2.1 when starting/stopping remote servers its not really clear what is going on - i.e. what is the semantics when stopping a server that were already running when started ? Does it execute a command or does it just disconnect ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
15
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 June 2011