May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21766) NPE when trying to generate mapping files on project with no console config

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21766?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21766: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > NPE when trying to generate mapping files on project with no console config > --------------------------------------------------------------------------- > > Key: JBIDE-21766 > URL: https://issues.jboss.org/browse/JBIDE-21766 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Rastislav Wagner > Assignee: Koen Aers > Fix For: 4.4.0.Alpha3 > > > {code} > java.lang.NullPointerException > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.getService(ConfigurationActor.java:127) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfiguration(ConfigurationActor.java:134) > at org.hibernate.eclipse.jdt.ui.wizards.ConfigurationActor.createConfigurations(ConfigurationActor.java:117) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.createConfigurations(NewHibernateMappingFileWizard.java:559) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.getPlaces2Gen(NewHibernateMappingFileWizard.java:316) > at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.handlePageChanging(NewHibernateMappingFileWizard.java:172) > at org.eclipse.jface.wizard.WizardDialog$10.run(WizardDialog.java:1554) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1551) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:899) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1186) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425) > 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:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > 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:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor106.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > 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:160) > 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:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21198) "Tern - Go to definition" hyperlink opens nothing

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21198?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21198: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > "Tern - Go to definition" hyperlink opens nothing > ------------------------------------------------- > > Key: JBIDE-21198 > URL: https://issues.jboss.org/browse/JBIDE-21198 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150912-1100-B100 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.0.Alpha3 > > > 1. Install AngularJS from JBoss Central (Enable Early Access) > 2. Create JSF 1.2 Kick Start project > 3. Open inputUserName.jsp in VPE > 4. Click on 'user' text within <h:inputText> tag > 5. Press F3 key > ERROR: Nothing happened. User.java file should be opened in editor > 6. Hover with mouse over the same text and push Ctrl key > ASSERT: Menu with these tree actions appeared: > * Tern - Go to definiton > * Open User.java > * Open 'User - demo' > Action Open User.java opens User.java in editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22231) Ensure OpenShift and Docker tooling support the MSA workflow

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22231?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22231: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Ensure OpenShift and Docker tooling support the MSA workflow > ------------------------------------------------------------ > > Key: JBIDE-22231 > URL: https://issues.jboss.org/browse/JBIDE-22231 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: docker, openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha3 > > > This Epic gather the issues we've identified that currently prevent [~burrsutter] to perform his MSA demo entirely from Eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18876: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.4.0.Alpha3 > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21226) JSDT Parser incorrectly reports errors on various js projects

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21226?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21226: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.3.x) (was: 4.4.0.Alpha2) > JSDT Parser incorrectly reports errors on various js projects > ------------------------------------------------------------- > > Key: JBIDE-21226 > URL: https://issues.jboss.org/browse/JBIDE-21226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.1.Beta1 > Environment: 4.3.x nightly from 2015-12-04 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: 4.4.0.Alpha3 > > Attachments: Screen Shot 2015-12-09 at 16.21.21.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20540) Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20540?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20540: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Upstream WTP bundled xsd using relative path for ejb-jar_3_1.xsd > ---------------------------------------------------------------- > > Key: JBIDE-20540 > URL: https://issues.jboss.org/browse/JBIDE-20540 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha3 > > > See bug as described here: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=476274 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22176: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.4.0.Alpha3 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21755: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Properties: "Eager-er" loading of the project properties > -------------------------------------------------------- > > Key: JBIDE-21755 > URL: https://issues.jboss.org/browse/JBIDE-21755 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha3 > > > Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20934) Create tests for the HibernateMappingExporter facade classes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20934?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20934: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Create tests for the HibernateMappingExporter facade classes > ------------------------------------------------------------ > > Key: JBIDE-20934 > URL: https://issues.jboss.org/browse/JBIDE-20934 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20753: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: regression > Fix For: 4.4.0.Alpha3 > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016