December 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25262) CDK server adapter: after removing ~/.minishift, server adapter can only be stopped via "Restart", "Stop" keeps it running

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25262?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25262. --------------------------------- Verified in devstudio 11.2.0.AM2-v20171207-1702-B1735. > CDK server adapter: after removing ~/.minishift, server adapter can only be stopped via "Restart", "Stop" keeps it running > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25262 > URL: https://issues.jboss.org/browse/JBIDE-25262 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.2.AM2 > > Attachments: image-2017-10-17-11-05-22-885.png > > > steps: > # EXEC: in cmd line: setup cdk 3.2.alpha1 with a profile (ex. minishift setup-cdk --profile test42) > # EXEC: in "Servers" view: create a server adapter for this cdk with the profile and start it. > # EXEC: in cmd line: kill the ~/.minishift > # EXEC: in "Servers" view: select your server adapter and pick "Stop" > # ASSERT: "Console" view shows up pasting > {code} > You need to run 'minishift setup-cdk' first to install required CDK components. > {code} > And the following error dialog appears: > !image-2017-10-17-11-05-22-885.png! > # ASSERT: the server adapter is still **[Started]** > # EXEC: in "Servers" view: select your server adapter and pick "Restart" > # ASSERT: the same console (see above) output is shown, the same error dialog appears. You see the server adapter trying to start again but it fails, too > Result: > The server adapter is now in **[Stopped]** > Expected result: > I should be able to stop the adapter, not just work around it by restarting it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25447) Use highest available version of the Hibernate runtime in 'org.hibernate.eclipse.launch.CodeGenXMLFactory' if not specified in console configuration preferences

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25447?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-25447. ------------------------------------ > Use highest available version of the Hibernate runtime in 'org.hibernate.eclipse.launch.CodeGenXMLFactory' if not specified in console configuration preferences > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25447 > URL: https://issues.jboss.org/browse/JBIDE-25447 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.5.2.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25451) Fill the 'metadata' field of 'AbstractExporter' in 'org.jboss.tools.hibernate.runtime.v_5_2.internal.ServiceImpl#newHibernateMappingExporter(IConfiguration, File)'

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25451?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-25451. ------------------------------------ > Fill the 'metadata' field of 'AbstractExporter' in 'org.jboss.tools.hibernate.runtime.v_5_2.internal.ServiceImpl#newHibernateMappingExporter(IConfiguration,File)' > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25451 > URL: https://issues.jboss.org/browse/JBIDE-25451 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.5.2.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25350) CDK server editor's launch configuration should not offers to edit some fields

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25350?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25350. --------------------------------- Verified in devstudio 11.2.0.AM2-v20171207-1702-B1735. > CDK server editor's launch configuration should not offers to edit some fields > ------------------------------------------------------------------------------ > > Key: JBIDE-25350 > URL: https://issues.jboss.org/browse/JBIDE-25350 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.2.AM2 > > > I noticed some inconsistent behavior in launch configuration dialog. > 1. Server name change in server's editor do not result in changing of text "Name:" in launch configuration (should be, possibly a bug) and vice versa. > 2. Change of Minishift Binary in editor results in change of "Location" in launch config, but not vice versa. This is not a bug, it is just confusing the user. > I believe that it should not be possible to edit those two fields in launch configuration. First reason for this is that we already have a place where we can edit server's name and location (in cdk server editor) and other reason will be that if we will allow to edit those values, we must put validation in place. WDYT [~mmalina] [~rob.stryker] ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25303 at 12/11/17 6:43 AM: -------------------------------------------------------------------- [~jeffmaury] [~rob.stryker] [~aurelien.pupier] * No. 1 aka DEV_MODE seems resolved, the image now has a label that advertises JAVA_DEBUG to enable the "DEVMODE" which works. * No. 2 aka deployment was agreed upon that we would not require any change in the imported project but the server adapter would publish the approriate files to <deployment-folder>/BOOT-INF/classes since BOOT-INF/classes is the structure that's *ALWAYS* used by the springboot fat-jar packaging. In regard of No 2 I noticed that if you set the publisher to publish to BOOT-INF/classes everything, source and compilation units alike. Here's what's present in the local deploy folder that then gets sent to the pod: {code} $ ls -l total 56 -rw-r--r-- 1 adietish staff 11357 Dec 11 12:41 LICENSE.md -rw-r--r-- 1 adietish staff 2267 Dec 11 12:41 README.md drwxr-xr-x 6 adietish staff 192 Dec 11 12:41 classes drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 configuration -rw-r--r-- 1 adietish staff 906 Dec 11 12:41 devtools.sh drwxr-xr-x 46 adietish staff 1472 Dec 11 12:41 lib -rw-r--r-- 1 adietish staff 6343 Dec 11 12:41 pom.xml drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 src drwxr-xr-x 4 adietish staff 128 Dec 11 12:41 target {code} [~rob.stryker] Thoughts? was (Author: adietish): [~jeffmaury] [~rob.stryker] [~aurelien.pupier] * No. 1 aka DEV_MODE seems resolved, the image now has a label that advertises JAVA_DEBUG to enable the "DEVMODE" which works. * No. 2 aka deployment was agreed upon that we would not require any change in the imported project but the server adapter would publish the approriate files to <deployment-folder>/BOOT-INF/classes since BOOT-INF/classes is the structure that's *ALWAYS* used by the springboot fat-jar packaging. In regard of No 2 I noticed that if you set the publisher to publish to BOOT-INF/classes everything, source and compilation units alike. Here's what's present in the local deploy folder that then gets sent to the pod: {code} ingboot-xml/deploy  ls -l total 56 -rw-r--r-- 1 adietish staff 11357 Dec 11 12:41 LICENSE.md -rw-r--r-- 1 adietish staff 2267 Dec 11 12:41 README.md drwxr-xr-x 6 adietish staff 192 Dec 11 12:41 classes drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 configuration -rw-r--r-- 1 adietish staff 906 Dec 11 12:41 devtools.sh drwxr-xr-x 46 adietish staff 1472 Dec 11 12:41 lib -rw-r--r-- 1 adietish staff 6343 Dec 11 12:41 pom.xml drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 src drwxr-xr-x 4 adietish staff 128 Dec 11 12:41 target {code} [~rob.stryker] Thoughts? > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM3 > > Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25303: ------------------------------------------ [~jeffmaury] [~rob.stryker] [~aurelien.pupier] * No. 1 aka DEV_MODE seems resolved, the image now has a label that advertises JAVA_DEBUG to enable the "DEVMODE" which works. * No. 2 aka deployment was agreed upon that we would not require any change in the imported project but the server adapter would publish the approriate files to <deployment-folder>/BOOT-INF/classes since BOOT-INF/classes is the structure that's *ALWAYS* used by the springboot fat-jar packaging. In regard of No 2 I noticed that if you set the publisher to publish to BOOT-INF/classes everything, source and compilation units alike. Here's what's present in the local deploy folder that then gets sent to the pod: {code} ingboot-xml/deploy  ls -l total 56 -rw-r--r-- 1 adietish staff 11357 Dec 11 12:41 LICENSE.md -rw-r--r-- 1 adietish staff 2267 Dec 11 12:41 README.md drwxr-xr-x 6 adietish staff 192 Dec 11 12:41 classes drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 configuration -rw-r--r-- 1 adietish staff 906 Dec 11 12:41 devtools.sh drwxr-xr-x 46 adietish staff 1472 Dec 11 12:41 lib -rw-r--r-- 1 adietish staff 6343 Dec 11 12:41 pom.xml drwxr-xr-x 3 adietish staff 96 Dec 11 12:41 src drwxr-xr-x 4 adietish staff 128 Dec 11 12:41 target {code} [~rob.stryker] Thoughts? > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM3 > > Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25450) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_2 to version 5.2.8.Final

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25450?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-25450. ------------------------------------ > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_2 to version 5.2.8.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-25450 > URL: https://issues.jboss.org/browse/JBIDE-25450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25395) Remove unneeded method 'IService#newPrimaryKey()'

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25395?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-25395. ------------------------------------ > Remove unneeded method 'IService#newPrimaryKey()' > ------------------------------------------------- > > Key: JBIDE-25395 > URL: https://issues.jboss.org/browse/JBIDE-25395 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.5.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25303 at 12/11/17 6:02 AM: -------------------------------------------------------------------- here's a screencast showing hot code replace working with the fuse-on-openshift demo app that's attached to this jira: https://youtu.be/YJXKtR1DcGI So there are 2 issues left here: # It looks as if the DEV_MODE env var isnt used, only DEBUG is (see my question in [OSFUSE-548|https://issues.jboss.org/browse/OSFUSE-548?focusedCommentId=13...]) # the packaging is still done via "Deployment Assembly" in the project preferences. We need to decide how to deal that. was (Author: adietish): here's a screencast showing hot code replace working with the fuse-on-openshift demo app that's attached to this jira: https://youtu.be/YJXKtR1DcGI So there are 2 issues left here: # It looks as if the DEV_MODE env var isnt used, only DEBUG is (see my question in [OSFUSE-548|https://issues.jboss.org/browse/OSFUSE-548?focusedCommentId=13...] # the packaging is still done via "Deployment Assembly" in the project preferences. We need to decide how to deal that. > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM3 > > Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20569: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.AM2) > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.5.x > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017