May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26066) Spring Boot Project configurator: "Adding child module {0} to project {1}." reported as error in log where's no error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26066?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-26066: ---------------------------------------- Assignee: Andre Dietisheim > Spring Boot Project configurator: "Adding child module {0} to project {1}." reported as error in log where's no error > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26066 > URL: https://issues.jboss.org/browse/JBIDE-26066 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, openshift > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > steps: > # EXEC: import the 2 projects that are in the zip that's attached to JBIDE-25504 > # EXEC: look into the Eclipse log > Result: > You'll find the following error > {code} > "Adding child module {0} to project {1}." > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26066) Spring Boot Project configurator: "Adding child module {0} to project {1}." reported as error in log where's no error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26066?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26066: ------------------------------------- Component/s: (was: openshift) > Spring Boot Project configurator: "Adding child module {0} to project {1}." reported as error in log where's no error > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26066 > URL: https://issues.jboss.org/browse/JBIDE-26066 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.6.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > steps: > # EXEC: import the 2 projects that are in the zip that's attached to JBIDE-25504 > # EXEC: look into the Eclipse log > Result: > You'll find the following error > {code} > "Adding child module {0} to project {1}." > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25679) New Application: OpenShift Online: wizard pops up empty if you create a project right beforehand

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25679?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25679: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.0.AM2) > New Application: OpenShift Online: wizard pops up empty if you create a project right beforehand > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-25679 > URL: https://issues.jboss.org/browse/JBIDE-25679 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.6.0.AM3 > > Attachments: OpenshiftOnlineNewProject.webm, image-2018-02-01-10-22-40-265.png > > > # ASSERT: make sure you dont have any project in OpenShift Online (https://console.starter-us-east-1.openshift.com or https://open.paas.redhat.com) > # EXEC: launch new application wizard > # ASSERT: you're prompted to provide the name for a new project that will be created > # EXEC: provide the name, hit "Finish" > Result: > !image-2018-02-01-10-22-40-265.png! > New Application wizard shows up with no project selected nor available in the project combo and thus no templates are listed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25109) Server adapter editor: provide ability to only change debug port (and not the debug port key)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25109?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25109: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.x) > Server adapter editor: provide ability to only change debug port (and not the debug port key) > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25109 > URL: https://issues.jboss.org/browse/JBIDE-25109 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter_editor > Fix For: 4.6.0.AM3 > > > Currently there's only 1 checkbox to allow the user to set the debugging key and port. If one only wants to set a custom debug port only, he cannot, he also has to provide the debug key at the same time. We should provide an additional checkbox to enable the debug port only, changing the existing one to only enable/disable the debug key. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24979: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.0.AM2) > Scale up/down/to: NPE if you have only a rc, no dc for your app > --------------------------------------------------------------- > > Key: JBIDE-24979 > URL: https://issues.jboss.org/browse/JBIDE-24979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.x > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, scale > Fix For: 4.6.0.AM3 > > Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png > > > # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller > (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json]) > # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To" > !image-2017-09-04-21-24-57-027.png! > The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing. > Result: > Nothing happens and in the log you discover the following: > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239) > 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:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) > at org.eclipse.equinox.launcher.Main.run(Main.java:1499) > at org.eclipse.equinox.launcher.Main.main(Main.java:1472) > Caused by: java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92) > at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25756) OpenShift Explorer: OpenShift connection still displays project that was deleted

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25756?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25756: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.x) > OpenShift Explorer: OpenShift connection still displays project that was deleted > -------------------------------------------------------------------------------- > > Key: JBIDE-25756 > URL: https://issues.jboss.org/browse/JBIDE-25756 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM2 > Environment: Win 10, https://console.engint.openshift.com > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Labels: explorer > Fix For: 4.6.0.AM3 > > > Refresh on OpenShift Connection in OpenShift Explorer should automatically refresh projects/applications/pods, otherwise user needs to manually refresh connection to get rid of deleted projects in OpenShift explorer. > Also error message is duplicated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25838: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.0.AM2) > Explorer: expand connection to the level that it was expanded to after editing it > --------------------------------------------------------------------------------- > > Key: JBIDE-25838 > URL: https://issues.jboss.org/browse/JBIDE-25838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: connection, explorer > Fix For: 4.6.0.AM3 > > > steps: > # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects > # EXEC: edit the connection, change the url, hit "Finish" > Result: > Connection is updated (refreshed) but collapsed, wont show the/all the projects > Expected result: > Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25916) OpenShift Server Adapter: Error in Log after "Restart in Debug"

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25916?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25916: ------------------------------- Fix Version/s: 4.6.0.AM3 (was: 4.6.0.AM2) > OpenShift Server Adapter: Error in Log after "Restart in Debug" > --------------------------------------------------------------- > > Key: JBIDE-25916 > URL: https://issues.jboss.org/browse/JBIDE-25916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.Final > Environment: F28 + Red Hat JBoss Developer Studio Build id: GA-v20180410-1152-B2341 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, server_adapter > Fix For: 4.6.0.AM3 > > Attachments: error-launching-server.png > > > An error occurs when restarting server adapter in debug: > {code:java} > eclipse.buildId=11.3.0.GA-v20180410-1152-B2341 > java.version=1.8.0_162 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Warning > Wed Apr 11 18:09:03 CEST 2018 > Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy > org.eclipse.core.runtime.CoreException: Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.handleSyncDownFailure(OpenShiftPublishController.java:92) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:61) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1340) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$1.run(OpenShiftLaunchController.java:261) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Contains: Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war > rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3] > error: exit status 23 > {code} > {code:java} > eclipse.buildId=11.3.0.GA-v20180410-1152-B2341 > java.version=1.8.0_162 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Apr 11 18:09:03 CEST 2018 > Error while publishing server eap-app (Service) at OpenShift 3 (api.engint.openshift.com). Could not sync all pods to folder /home/jkopriva/devstudio_B2341/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/oc2@eap-app/deploy > {code} > {code:java} > eclipse.buildId=11.3.0.GA-v20180410-1152-B2341 > java.version=1.8.0_162 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B2341/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Apr 11 18:09:03 CEST 2018 > Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@e159132 to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@e822802 failed: could not make way for new regular file: ROOT.war > rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [generator=3.1.3] > error: exit status 23 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25553: ------------------------------------ [~koen.aers] Ping again... 5 days later. Any update? Are you running all the tests w/ JDK 9 too? > Cannot create Hibernate Console Configuration for projects with java 9 > ---------------------------------------------------------------------- > > Key: JBIDE-25553 > URL: https://issues.jboss.org/browse/JBIDE-25553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.5.2.AM2 > Reporter: Rastislav Wagner > Assignee: Koen Aers > Priority: Critical > Fix For: 4.6.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26065) Add RH Central connector for nodeclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26065: ------------------------------- Description: Steps to perform: a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability b) add that to the 3rd party target platform used for building RH Central c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools* The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse. [1] http://www.nodeclipse.org/updates/ If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA. was: Steps to perform: a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability b) add that to the 3rd party target platform used for building RH Central c) create a connector in Central for installing Nodeclipse into devstudio and jbosstools The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse. [1] http://www.nodeclipse.org/updates/ If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA. > Add RH Central connector for nodeclipse > --------------------------------------- > > Key: JBIDE-26065 > URL: https://issues.jboss.org/browse/JBIDE-26065 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, central-update, updatesite, upstream > Affects Versions: 4.6.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.AM3 > > > Steps to perform: > a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability > b) add that to the 3rd party target platform used for building RH Central > c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools* > The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse. > > [1] http://www.nodeclipse.org/updates/ > If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2018