September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12211) OpenShift wizard throws exception when using name with "/"

by Stefan Bunciak (JIRA)

13 years, 6 months

2
17
0 / 0

[JBoss JIRA] (JBIDE-12699) Archetypes in JBoss Central - Page with description and Requirements disappeared

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-12699: ---------------------------------- Summary: Archetypes in JBoss Central - Page with description and Requirements disappeared Key: JBIDE-12699 URL: https://issues.jboss.org/browse/JBIDE-12699 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, maven Affects Versions: 4.0.0.Alpha2 Reporter: Radim Hopp Assignee: Fred Bricon Priority: Critical Fix For: 4.0.0.Alpha2 Page with description and requirements is missing in Archetype based project wizard (such as "Java EE Web Project" in JBoss Central). Instead of Description & Requirements page is there page with just Output directory and Working sets, which is duplicated on next page. Also, two errors are thrown: {noformat}java.net.MalformedURLException at java.net.URL.<init>(URL.java:617) at java.net.URL.<init>(URL.java:480) at java.net.URL.<init>(URL.java:429) at org.jboss.tools.maven.project.examples.stacks.StacksManager.getStacks(StacksManager.java:42) at org.jboss.tools.maven.project.examples.wizard.NewProjectExamplesStacksRequirementsPage.<init>(NewProjectExamplesStacksRequirementsPage.java:94) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard2.createContributedPages(NewProjectExamplesWizard2.java:182) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard2.addPages(NewProjectExamplesWizard2.java:146) at org.jboss.tools.central.wizards.AbstractJBossCentralProjectWizard.addPages(AbstractJBossCentralProjectWizard.java:82) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:605) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at org.jboss.tools.central.editors.GettingStartedPage$9.linkActivated(GettingStartedPage.java:617) 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.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) 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:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) 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:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) Caused by: java.lang.NullPointerException at java.net.URL.<init>(URL.java:522) ... 53 more {noformat} and {noformat}org.eclipse.core.runtime.CoreException: Plug-in "org.jboss.tools.maven.project.examples" was unable to instantiate class "org.jboss.tools.maven.project.examples.wizard.NewProjectExamplesStacksRequirementsPage". at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:188) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard2.createContributedPages(NewProjectExamplesWizard2.java:182) at org.jboss.tools.project.examples.wizard.NewProjectExamplesWizard2.addPages(NewProjectExamplesWizard2.java:146) at org.jboss.tools.central.wizards.AbstractJBossCentralProjectWizard.addPages(AbstractJBossCentralProjectWizard.java:82) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:605) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at org.jboss.tools.central.editors.GettingStartedPage$9.linkActivated(GettingStartedPage.java:617) 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.Widget.sendEvent(Widget.java:1276) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) 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:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) 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:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) Caused by: java.lang.NoClassDefFoundError: org/jboss/jdf/stacks/client/StacksClient at org.jboss.tools.maven.project.examples.stacks.StacksManager.getStacks(StacksManager.java:58) at org.jboss.tools.maven.project.examples.wizard.NewProjectExamplesStacksRequirementsPage.<init>(NewProjectExamplesStacksRequirementsPage.java:94) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) ... 42 more {noformat} Probably related to [JBIDE-12472] -- 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

13 years, 6 months

3
2
0 / 0

[JBoss JIRA] (JBIDE-12698) stacks-client jar missing from org.jboss.tools.maven.project.examples_1.4.0.Alpha2-v20120922-1607-B38

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12698: ----------------------------------- Summary: stacks-client jar missing from org.jboss.tools.maven.project.examples_1.4.0.Alpha2-v20120922-1607-B38 Key: JBIDE-12698 URL: https://issues.jboss.org/browse/JBIDE-12698 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Alpha2 Reporter: Fred Bricon Assignee: Fred Bricon Priority: Blocker Fix For: 4.0.0.Alpha2 The custom UI for stacks based project example doesn't launch because the stacks-client jar is missing from the org.jboss.tools.maven.project.examples.jar This is caused by the build.properties missing that entry -- 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

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8963) There is no possibility to drag-and-drop into the page with empty <body>

by Vitali Yemialyanchyk (JIRA)

There is no possibility to drag-and-drop into the page with empty <body> ------------------------------------------------------------------------ Key: JBIDE-8963 URL: https://issues.jboss.org/browse/JBIDE-8963 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.1.M1 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Blocker here is example: === <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Template Page title</title> <link href="styles/some-style.css" media="screen" type="text/css" rel="stylesheet" /> </head> <body> </body> </html> === - there is no possibility to drag-and-drop <div> into the <body> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-12435) VPE Selection Bar is Black on Linux

by Denis Maliarevich (JIRA)

Denis Maliarevich created JBIDE-12435: ----------------------------------------- Summary: VPE Selection Bar is Black on Linux Key: JBIDE-12435 URL: https://issues.jboss.org/browse/JBIDE-12435 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.4.0.M1 Reporter: Denis Maliarevich Assignee: Denis Maliarevich Fix For: 3.4.0.M1 Attachments: SelBarVpe.png VPE Selection Bar is drown in black backgrounf color. Tag names are not seen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] (JBIDE-11982) When you change deployment location for as7 without undeploying projects first they exist in both new and old locations

by Martin Malina (JIRA)

Martin Malina created JBIDE-11982: ------------------------------------- Summary: When you change deployment location for as7 without undeploying projects first they exist in both new and old locations Key: JBIDE-11982 URL: https://issues.jboss.org/browse/JBIDE-11982 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: jbdevstudio-product-universal-5.0.0.v201205220143N-H1345-CR1.jar Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 I stumbled upon this while verifying JBIDE-11297. When you have an AS7/EAP6 server set up to deploy in the standard deployments directory, have a project deployed, stop the server, change the deployment settings to "Use workspace metadata..." and start the server again, it will be deployed to the metadata dir, but the project will also stay in the standard deployments dir, thus it's duplicated. If you undeploy the module before stopping the server to change the deployment settings it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
11
0 / 0

[JBoss JIRA] (JBIDE-12603) Default fileset not added for first detected runtime

by Martin Malina (JIRA)

Martin Malina created JBIDE-12603: ------------------------------------- Summary: Default fileset not added for first detected runtime Key: JBIDE-12603 URL: https://issues.jboss.org/browse/JBIDE-12603 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Affects Versions: 4.0.0.Alpha1 Environment: JBDS 6.0.0.Alpha1b H25 Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 4.0.0.Alpha2 With JBIDE-12453 in place, there now is an example fileset added for AS7.0, AS7.1 and EAP6 server adapters. However, if you have a new workspace and add one of these servers using the runtime detection, no fileset gets created. When you add another one, it will have a fileset defined. Also, if you add a server manually rather than using runtime detection, it will have a fileset as well. -- 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

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-12624) Test failures in org.jboss.tools.project.examples.test

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-12624: ------------------------------------- Summary: Test failures in org.jboss.tools.project.examples.test Key: JBIDE-12624 URL: https://issues.jboss.org/browse/JBIDE-12624 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.0.0.Alpha2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.0.0.Alpha2 See http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk.... The issue has been introduced by fixing JBIDE-12472. -- 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

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12694) WS can't install because of dependency to SSE editor

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12694: -------------------------------------- Summary: WS can't install because of dependency to SSE editor Key: JBIDE-12694 URL: https://issues.jboss.org/browse/JBIDE-12694 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform, Webservices Reporter: Mickael Istria Assignee: Nick Boldt Priority: Blocker Fix For: 4.0.0.Beta1 See this log: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk.... {quote} junit.framework.AssertionFailedError: Could not install from: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ Software being installed: org.jboss.tools.ws.jaxrs.feature.source.feature.group 1.4.0.Beta1-v20120923-1151-B49 Missing requirement: JBoss JAX-RS Tooling (Core) 1.4.0.Beta1-v20120923-1151-B49 (org.jboss.tools.ws.jaxrs.core 1.4.0.Beta1-v20120923-1151-B49) requires 'bundle org.eclipse.wst.sse.core 1.1.701' but it could not be found {quote} It seems like the jaxrs bundle depends on a specific version of wst.sse. You should consider either: * Change minimal version in jaxrs.core MANIFEST dependency to SSE to match version that is already part of target platform (1.1.700), or * Open a ticket against "target-platform" component to requrest availability of this new version. Except if this version is set on purpose to prevent from a very annoying bug or to provide a very cool feature, I recommand reducing the version of the dependency. -- 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

13 years, 6 months

4
8
0 / 0

[JBoss JIRA] (JBIDE-11847) OpenShift server: widgets not following good style

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11847: -------------------------------------- Summary: OpenShift server: widgets not following good style Key: JBIDE-11847 URL: https://issues.jboss.org/browse/JBIDE-11847 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers, openshift Affects Versions: 3.3.0.Beta3 Environment: F15 JBDS 5.0.0.Beta3a Reporter: Stefan Bunciak Assignee: Rob Stryker Attachments: widgets.png !widgets.png|thumbnail! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
13
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 September 2012