February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10116?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10116: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Issues that affect AS7/EAP integration to tools > ----------------------------------------------- > > Key: JBIDE-10116 > URL: https://issues.jboss.org/browse/JBIDE-10116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: f2f2012 > Fix For: 4.2.0.Beta1 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15191) Frozen dynamic web project wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15191?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15191: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Frozen dynamic web project wizard > --------------------------------- > > Key: JBIDE-15191 > URL: https://issues.jboss.org/browse/JBIDE-15191 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.CR1 > Reporter: Jiri Peterka > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: dump.txt, frozen-wizard.png > > > IDE has frozen, when creating Dynamic web project, thread dump attached. Seeing some archives callings there. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14697) User library fileset cannot be modified

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14697?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14697: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > User library fileset cannot be modified > --------------------------------------- > > Key: JBIDE-14697 > URL: https://issues.jboss.org/browse/JBIDE-14697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Assignee: Jaroslav Jankovič > Fix For: 4.2.0.Beta1 > > > STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java -> Build Path -> User Libraries) > STEP: create project with archives support > STEP: create some archive in the project > STEP: add new user library fileset in the archive (myLib1) > STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset > STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it > FAIL: there is still myLib in archives explorer, not myLib2 as it should be -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14742) Investigate using or forking eclipse release train repo cheks

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14742?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14742: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Investigate using or forking eclipse release train repo cheks > ------------------------------------------------------------- > > Key: JBIDE-14742 > URL: https://issues.jboss.org/browse/JBIDE-14742 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.2.0.Beta1 > > > http://build.eclipse.org/simrel/kepler/reporeports/ > http://wiki.eclipse.org/SimRel/Simultaneous_Release_Reports_FAQ > Seems like very useful tool to run against and updatesite. -- 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, 2 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14725?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14725: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > 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.x, 4.2.0.Beta1 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15168) Disable outline view in FreeMarker IDE

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15168?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15168: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Disable outline view in FreeMarker IDE > -------------------------------------- > > Key: JBIDE-15168 > URL: https://issues.jboss.org/browse/JBIDE-15168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.1.0.Final > Reporter: Daniel Dekany > Fix For: 4.2.0.Beta1 > > > In the "FreeMarker IDE" Eclipse plugin, you should disable the outline view for now, as it's too broken to be useful, while it often slows template editing to crawl and is constantly flashing/redrawing as you type into the template, or even sometimes if you just move the cursor. > Regarding why it's broken: > * You show all the statements in it, which is way too much details and so it quickly becomes useless for overview and navigation. (Imagine if the Java outline did that, showing all if-s and for-s and assignments.) If should just list the macro and function declarations. > * It treats FreeMarker tags that don't end with {{/>}} as element openings, and then puts everything after that inside that element. But FreeMarker tags that start with {{#}} and can't have a body are implicitly closed. They are like {{img}} in HTML; {{<img ...>}} is the same as {{<img .../>}}. Similarly, {{<#assign x = 1>}} is the same as {{<#assign x = 1 />}}. > * It redraws the whole tree way to often. It slows things down, and the flashing it causes is annoying. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14119) look at how to handle the different jmx views/perspectives between AS and FuseSource plugins

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14119?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14119: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > look at how to handle the different jmx views/perspectives between AS and FuseSource plugins > -------------------------------------------------------------------------------------------- > > Key: JBIDE-14119 > URL: https://issues.jboss.org/browse/JBIDE-14119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > Talk with [~lhein] he knows more -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15391) Investigate having ports UI add relevant command line args to server startup

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15391?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15391: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Investigate having ports UI add relevant command line args to server startup > ---------------------------------------------------------------------------- > > Key: JBIDE-15391 > URL: https://issues.jboss.org/browse/JBIDE-15391 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > Subject seems pretty complete; forum post contains more information. Investigate how feasible it is for the editor sections to add relevant command line arguments to override standalone.xml's defaults. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15618) Add server mode for management; all tasks performed over management api

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15618?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15618: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Add server mode for management; all tasks performed over management api > ----------------------------------------------------------------------- > > Key: JBIDE-15618 > URL: https://issues.jboss.org/browse/JBIDE-15618 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > > A mode for management-specific behavior. This mode would be a third mode, similar to 'local' or 'rse'. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15383: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Server Launch Configuration loses Classpath User Entries > -------------------------------------------------------- > > Key: JBIDE-15383 > URL: https://issues.jboss.org/browse/JBIDE-15383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE_1.png, JBIDE_2.png, JBIDE_3.png > > > Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. > This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. > Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". > The attachments describe what happens: > * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. > * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). > * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. > * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. > I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. > I've been able to replicate this on two separate (similarly configured) machines. > This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new 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

12 years, 2 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 February 2014