July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26181) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.9.Final

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26181?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-26181: --------------------------------- Assignee: Koen Aers > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.9.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26181 > URL: https://issues.jboss.org/browse/JBIDE-26181 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.6.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > > This includes updating the Hibernate Core dependency to 5.1.15.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25616: ------------------------------------------ [~jkopriva] great, thx for verifying! Resolving. > [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Labels: docker_image, fis, upstream > Fix For: 4.9.0.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25616 at 7/12/18 6:16 AM: ------------------------------------------------------------------- [~jkopriva] great, thx for verifying! was (Author: adietish): [~jkopriva] great, thx for verifying! Resolving. > [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Labels: docker_image, fis, upstream > Fix For: 4.9.0.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26150) Enhance layout in the OpenShift explorer

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26150?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26150. --------------------------------- Closing. Layout is changed. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180710-1916-B2972 Build date: 20180710-1916 > Enhance layout in the OpenShift explorer > ---------------------------------------- > > Key: JBIDE-26150 > URL: https://issues.jboss.org/browse/JBIDE-26150 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.6.0.Final > > > When no OpenShift connections are defined, the OpenShift explorer display a default message. The layout of information should be improved according to. > See https://redhat.invisionapp.com/share/5YJVZE7PJNX#/screens/298348260 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Josef Kopriva edited comment on JBIDE-25504 at 7/12/18 5:21 AM: ---------------------------------------------------------------- Closing. works as expected, but I have had a little bit different workflow: 11. Project have "Utility Module" facet 13. This step is not needed [~adietish] Feel free to reopen, if it is not correct workflow. I also have not seen [~jeffmaury]'s issue. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180710-1916-B2972 Build date: 20180710-1916 was (Author: jkopriva): Closing. works as expected, but I have had a little bit different workflow: 11. Project have "Utility Module" facet 13. This step is not needed I also have not seen [~jeffmaury]'s issue. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180710-1916-B2972 Build date: 20180710-1916 > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: fedora26-screenshot-1.png, springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25504. --------------------------------- > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: fedora26-screenshot-1.png, springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-25504: --------------------------------------- Closing. works as expected, but I have had a little bit different workflow: 11. Project have "Utility Module" facet 13. This step is not needed I also have not seen [~jeffmaury]'s issue. Verified in: Red Hat Developer Studio Version: 12.0.0.GA Build id: GA-v20180710-1916-B2972 Build date: 20180710-1916 > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: fedora26-screenshot-1.png, springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26181) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.9.Final

by Koen Aers (JIRA)

Koen Aers created JBIDE-26181: --------------------------------- Summary: Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.9.Final Key: JBIDE-26181 URL: https://issues.jboss.org/browse/JBIDE-26181 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.6.0.Final Reporter: Koen Aers This includes updating the Hibernate Core dependency to 5.1.15.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26126) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26126?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-26126. ----------------------------- Resolution: Done > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-26126 > URL: https://issues.jboss.org/browse/JBIDE-26126 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [hibernate]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25616) [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-25616: --------------------------------------- [~adietish] I have retested it and I didn't have any issues with starting server adapter in debug, so I think we can close this. > [WATCHER] Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-25616 > URL: https://issues.jboss.org/browse/JBIDE-25616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884 > Reporter: Josef Kopriva > Assignee: Dmitrii Bocharov > Labels: docker_image, fis, upstream > Fix For: 4.9.0.AM1 > > Attachments: java, screenshot-1.png > > > Starting of server ends with error: > {code:java} > eclipse.buildId=11.2.0.GA-v20180122-2025-B1884 > java.version=1.8.0_151 > 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Wed Jan 24 11:21:45 CET 2018 > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 July 2018