June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14725) Unable to invoke download-runtimes wizard when offline

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-14725: ---------------------------------- Summary: Unable to invoke download-runtimes wizard when offline Key: JBIDE-14725 URL: https://issues.jboss.org/browse/JBIDE-14725 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.1.0.Beta1 Environment: JBDS 7.0.0.Beta1b, not connected to the internet Reporter: Radim Hopp Fix For: 4.1.0.Beta2 When trying to open download-runtimes wizard (form first page of "New Project Example" wizard or from preferences) nothing happens, just info for stacks not being available and Unhandled event loop exception are being logged in error log. {noformat} java.lang.NoClassDefFoundError: org/apache/http/HttpRequest at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:196) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:638) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:613) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:574) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:492) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:465) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:224) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:464) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(Unknown Source) at org.jboss.tools.stacks.core.model.StacksManager.getStacks(StacksManager.java:67) at org.jboss.tools.as.runtimes.integration.internal.DownloadRuntimesProvider$1.getStacks(DownloadRuntimesProvider.java:127) at org.jboss.tools.as.runtimes.integration.internal.DownloadRuntimesProvider.getStacks(DownloadRuntimesProvider.java:40) at org.jboss.tools.as.runtimes.integration.internal.DownloadRuntimesProvider.loadDownloadableRuntimes(DownloadRuntimesProvider.java:54) at org.jboss.tools.as.runtimes.integration.internal.DownloadRuntimesProvider.getDownloadableRuntimes(DownloadRuntimesProvider.java:48) at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadableRuntimesFromProviders(RuntimeExtensionManager.java:424) at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.loadDownloadRuntimes(RuntimeExtensionManager.java:238) at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:189) at org.jboss.tools.runtime.core.internal.RuntimeExtensionManager.getDownloadRuntimes(RuntimeExtensionManager.java:177) at org.jboss.tools.runtime.core.RuntimeCoreActivator.getDownloadRuntimes(RuntimeCoreActivator.java:139) at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard.<init>(DownloadRuntimesWizard.java:55) at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard.<init>(DownloadRuntimesWizard.java:59) at org.jboss.tools.runtime.ui.preferences.RuntimePreferencePage$9.widgetSelected(RuntimePreferencePage.java:374) 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.jboss.tools.project.examples.wizard.NewProjectExamplesRequirementsPage$1.widgetSelected(NewProjectExamplesRequirementsPage.java:246) 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.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:666) at org.jboss.tools.central.editors.GettingStartedPage.access$11(GettingStartedPage.java:657) at org.jboss.tools.central.editors.GettingStartedPage$5.linkActivated(GettingStartedPage.java:586) 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: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:1109) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) Caused by: java.lang.ClassNotFoundException: org.apache.http.HttpRequest cannot be found by org.jboss.tools.stacks.core_1.0.0.Beta1-v20130525-0108-B68 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(Unknown Source) ... 78 more {noformat} And the more interesting part: Wizard is not working after reconnecting to the internet. It's not even working after restarting eclipse. It starts to work again with another workspace. In a nutshell, when you try to invoke runtimes-download wizard when offline, it will not work in that workspace no matter what (reconnecting to internet, restarting eclipse...) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14616) Remove <relativePath/> to parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14616?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14616: ------------------------------------- https://github.com/jbosstools/jbosstools-central/pull/116 applied in jbosstools-central/master > Remove <relativePath/> to parent pom > ------------------------------------ > > Key: JBIDE-14616 > URL: https://issues.jboss.org/browse/JBIDE-14616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Having a relativePath to parent pom in each component makes that often, on development machine, build resolves parent pom to the relative one (which my not be correctly sync'd) instead of the one which is published on Nexus. > This introduce confusion and may result in different build output between CI and local. Therefore, we should remove the <relativePath/> from all components. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14724) Fix working with HSQLDB driver

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14724?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-14724: -------------------------------------- Description: Create the HSQLDB driver definition using generic jdbc template. The reason why we shouldn't use HSQLDB template is described at TEIIDDES-1744. (was: Create the HSQLDB driver definition using generic jdbc template. The reason why we shouldn't use HSQLDB profile is described at TEIIDDES-1744.) > Fix working with HSQLDB driver > ------------------------------ > > Key: JBIDE-14724 > URL: https://issues.jboss.org/browse/JBIDE-14724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: QA > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.0.0.Alpha1-SOA > > > Create the HSQLDB driver definition using generic jdbc template. The reason why we shouldn't use HSQLDB template is described at TEIIDDES-1744. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14724) Fix working with HSQLDB driver

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBIDE-14724: ----------------------------------------- Summary: Fix working with HSQLDB driver Key: JBIDE-14724 URL: https://issues.jboss.org/browse/JBIDE-14724 Project: Tools (JBoss Tools) Issue Type: Bug Components: QA Affects Versions: 4.0.0.Alpha1-SOA Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.0.0.Alpha1-SOA Create the HSQLDB driver definition using generic jdbc template. The reason why we shouldn't use HSQLDB profile is described at TEIIDDES-1744. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-345: ------------------------------------------ Adding info for my benefit about ports: * Ports include management, web, JNDI, JMX RMI * Port offset = integer added to all ports on startup so can have multiple servers on the same machine without port conflicts; feature of newer servers * Detect from local runtime = for automatic detection of ports, typically by parsing config files and searching for XPath strings and using values found as chosen port; can override when using custom configuration * Configure = wizard for viewing and changing/adjusting the XPath information that is used to automatically detected the ports; will not change the server config file, just which information is used by JBoss Server Manager > NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools > --------------------------------------------------------------- > > Key: TOOLSDOC-345 > URL: https://issues.jboss.org/browse/TOOLSDOC-345 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - JBoss Server Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools. > The unique JBoss Server Tools features I have are: > * automatic runtime detection > * ability to download and install a JBoss runtime > * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique > * set a default server icon > * set default filesets > * set default classpath entries > * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone > What have I missed? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14609) server adapter wizard: does not switch output directory when I switch app (type)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14609?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14609: ------------------------------------- Fix Version/s: 4.1.0.Beta2 > server adapter wizard: does not switch output directory when I switch app (type) > -------------------------------------------------------------------------------- > > Key: JBIDE-14609 > URL: https://issues.jboss.org/browse/JBIDE-14609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-332) Release Notes - JBDS product rename

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-332?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-332: ------------------------------------------ JBoss graphic removal to be done at later date as required new brand from marketing. Marking JIRA as done. > Release Notes - JBDS product rename > ----------------------------------- > > Key: TOOLSDOC-332 > URL: https://issues.jboss.org/browse/TOOLSDOC-332 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > 1) Name to change in docs to 'Red Hat JBoss Developer Studio' on first use, followed by abbreviation to 'JBoss Developer Studio' on all subsequent uses. > 2) Removal of JBoss graphic from front page of docs. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-332) Release Notes - JBDS product rename

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-332?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-332. -------------------------------------- Resolution: Done > Release Notes - JBDS product rename > ----------------------------------- > > Key: TOOLSDOC-332 > URL: https://issues.jboss.org/browse/TOOLSDOC-332 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > 1) Name to change in docs to 'Red Hat JBoss Developer Studio' on first use, followed by abbreviation to 'JBoss Developer Studio' on all subsequent uses. > 2) Removal of JBoss graphic from front page of docs. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-327) Implement JBDS name & graphic change

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-327?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-327: ------------------------------------- Description: 1) Name to change in docs to 'Red Hat JBoss Developer Studio' on first use, followed by abbreviation to 'JBoss Developer Studio' on all subsequent uses. So full title will be used in: a) document title, and b) first use in first section, typically 'About Red Hat JBoss Developer Studio' (also associated chapter title of first section if appropriate). 2) Removal of JBoss graphic from front page of docs. was: 1) Name to change in docs to 'Red Hat JBoss Developer Studio' on first use, followed by abbreviation to 'JBoss Developer Studio' on all subsequent uses. 2) Removal of JBoss graphic from front page of docs. > Implement JBDS name & graphic change > ------------------------------------- > > Key: TOOLSDOC-327 > URL: https://issues.jboss.org/browse/TOOLSDOC-327 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Michelle Murray > Assignee: Michelle Murray > > 1) Name to change in docs to 'Red Hat JBoss Developer Studio' on first use, followed by abbreviation to 'JBoss Developer Studio' on all subsequent uses. So full title will be used in: > a) document title, and > b) first use in first section, typically 'About Red Hat JBoss Developer Studio' (also associated chapter title of first section if appropriate). > 2) Removal of JBoss graphic from front page of docs. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-332) Release Notes - JBDS product rename

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-332?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-332: ------------------------------------------ Doc brewing and will be available here for review: http://documentation-devel.engineering.redhat.com/docs/en-US/index.html#R... > Release Notes - JBDS product rename > ----------------------------------- > > Key: TOOLSDOC-332 > URL: https://issues.jboss.org/browse/TOOLSDOC-332 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Release Notes > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > 1) Name to change in docs to 'Red Hat JBoss Developer Studio' on first use, followed by abbreviation to 'JBoss Developer Studio' on all subsequent uses. > 2) Removal of JBoss graphic from front page of docs. -- 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, 10 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 June 2013