February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18769) ResourceException when generating hbm.xml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18769?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18769: --------------------------------------------- [~jpeterka] the code is listed as applied on PR and is visible in the history of 4.2.x: https://github.com/jbosstools/jbosstools-hibernate/commit/3549e0b3e220b38... So what are you basing it on it is not merged? > ResourceException when generating hbm.xml > ----------------------------------------- > > Key: JBIDE-18769 > URL: https://issues.jboss.org/browse/JBIDE-18769 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Final > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.3.Beta1 > > > {code} > org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp/org/jboss/tools/examples/model' does not exist. > at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) > at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) > at org.eclipse.core.internal.resources.File.create(File.java:115) > at org.eclipse.core.internal.resources.File.create(File.java:188) > at org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateFileChange.perform(CreateFileChange.java:165) > at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingPreviewPage.performFinish(NewHibernateMappingPreviewPage.java:299) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.performFinish(NewHibernateMappingFileWizard.java:408) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) > 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.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBDS-3273: ------------------------------------- [~fbricon] I've created: https://issues.jboss.org/browse/DEVELOPER-1248. Can you confirm that this is what you need. Also, when do you need it doing by? > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBDS-3273: ------------------------------------- {quote} That pretty much sound like what I need. My only concern is if you need to import 2 quickstarts that are not modules under a root parent. quickstart_id(s) could be a collection type {quote} [~fbricon] The Quickstarts are all in a flat hierarchy, so the quickstart ID will always be the path to the root of the QS. Does that help with your concern? > JBoss Central: Automatic upstream quickstart integration > --------------------------------------------------------- > > Key: JBDS-3273 > URL: https://issues.jboss.org/browse/JBDS-3273 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 9.0.0.Alpha2 > > > Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3359: ------------------------------------------- Thanks for testing. It was not sure it would make a difference. Now we know. > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3364) Include JBT sources in JBDS source zip

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3364?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3364: ------------------------------------------- Maven enforcer rules are something to run *Before* a build not after - thus a unit test is more appropriate. add a junit test that assert/samples that the zip contains selected stable sources (like our 17 main package names or something ?) > Include JBT sources in JBDS source zip > -------------------------------------- > > Key: JBDS-3364 > URL: https://issues.jboss.org/browse/JBDS-3364 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.2.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.1.0.Beta1, 9.0.0.Alpha2 > > > 1. Include the contents of the JBT source zip inside the JBDS one so all the sources for everything in JBDS (except third party stuff) can be seen in a single artifact. > 2. Ensure that the release guide has a step for pushing this zip to the FTP site, even for service releases. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3262: ------------------------------------------- when we release 8.1.0 we put big Deprecation section outlining what will be deprecate (just the visual part of JSF, making it clear the rest of functionality like content assist etc. are still supported) > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Labels: new_and_noteworthy > Fix For: 8.1.0.GA > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3359 at 2/27/15 5:03 AM: -------------------------------------------------------------- [~maxandersen], you mean studio/p2/director/configuration/config.ini ? Same result here: https://www.dropbox.com/s/udrlrvz0r88v73y/Screenshot%202015-02-27%2010.57... Then I tried to raise it to 500000 just in case, but still no luck. I even tried putting it to the other config.ini files I found just to be sure ;) was (Author: mmalina): [~maxandersen], you mean studio/p2/director/configuration/config.ini ? Same result here: https://www.dropbox.com/s/udrlrvz0r88v73y/Screenshot%202015-02-27%2010.57... Then I tried to raise it to 500000 just in case, but still no luck. > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3359: ------------------------------------- [~maxandersen], you mean studio/p2/director/configuration/config.ini ? Same result here: https://www.dropbox.com/s/udrlrvz0r88v73y/Screenshot%202015-02-27%2010.57... Then I tried to raise it to 500000 just in case, but still no luck. > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Anton Meller (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Anton Meller edited comment on JBIDE-19376 at 2/27/15 2:00 AM: --------------------------------------------------------------- Thank you guys for such a quick feedback! Regarding the workaround: to my luck this deadlock is not that deterministic. Even if servers view is visible it doesn't occurs at each start up. And most of the time this view is hidden behind some other tab with console or search or other view. But if the deadlock occurs I can only kill eclipse from the task manager. I can close the servers view, but it doesn't help as eclipse can't save workspace settings anyway, so I steel ending killing the java process from task manager. And most of the times there is no deadlock at next start up and I can switch to other view. was (Author: unmargin): Thank you guys for such a quick feedback! Regarding the workaround: to my luck this deadlock is not that deterministic. Even if servers view is visible it doesn't occurs at each start up. And most of the time this view is hidden behind some other tab with console or search or other view. But if the deadlock occurs I can only kill eclipse from the task manager. I can close the servers view, but it doesn't help as eclipse can't save workspace settings anyway, so I steel ending killing the java process from task manager. > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19376) Eclipse freezes at or shortly after startup

by Anton Meller (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19376?page=com.atlassian.jira.plugi... ] Anton Meller commented on JBIDE-19376: -------------------------------------- Thank you guys for such a quick feedback! Regarding the workaround: to my luck this deadlock is not that deterministic. Even if servers view is visible it doesn't occurs at each start up. And most of the time this view is hidden behind some other tab with console or search or other view. But if the deadlock occurs I can only kill eclipse from the task manager. I can close the servers view, but it doesn't help as eclipse can't save workspace settings anyway, so I steel ending killing the java process from task manager. > Eclipse freezes at or shortly after startup > ------------------------------------------- > > Key: JBIDE-19376 > URL: https://issues.jboss.org/browse/JBIDE-19376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Eclipse Luna EE. > Reporter: Anton Meller > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.3.CR1, 4.3.0.Alpha2 > > Attachments: 20150224_threaddump-1424762289905.tdump, 20150225_threaddump-1424847077811.tdump, 20150225_threaddump-1424847803263.tdump, 20150226_threaddump-1424936318015.tdump > > > Sometimes (probably once or twice a month) my eclipse freezes either right at startup or short after startup if I try to save some modified file. In Java VisualVM I can see than a deadlock in org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start() method. > Today I have updated JBoss plugins to latest version (from the update site for JBoss Tools 4.2.2.Final) and was able to reproduce the problem at every second or third startup . It looks like it occurs on larger workspaces (my current workspace has about 70 open projects (most of them are java projects and depends on each other)) and if servers view is open/visible right at startup. In a smaller workspace with only 11 projects I had no luck reproducing the deadlock. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015