January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4663) JDK9 Certification - docker

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4663?page=com.atlassian.jira.plugin.... ] Josef Kopriva updated JBDS-4663: -------------------------------- Fix Version/s: 11.2.0.GA > JDK9 Certification - docker > --------------------------- > > Key: JBDS-4663 > URL: https://issues.jboss.org/browse/JBDS-4663 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: docker > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 11.2.0.GA > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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: ------------------------------------------ weird enough, on my mac when using the cdk 3.3 I have permission errors when syncing to the pod. The rsync tries to copy a META-INF folder into the BOOT-INF folder in the pod (because we simply copy the contents of the /target folder over to the pod). In the pod, where there's an unzipped springboot.jar the META-INF is alongside the BOOT-INF (not within in). !Image+Pasted+at+2018-1-16+10-58.png! issuing "id" in the rsh shell within the pod tells me: {code} uid=1000090000 gid=0(root) groups=0(root),1000090000 {code} Using the cdk 3.2 wont show these issues, syncing and creating the META-INF folder works just fine. [~jeffmaury] could not reproduce this issue on his windows machine. > 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.Final > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, 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, 2 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 updated JBIDE-25303: ------------------------------------- Attachment: Image+Pasted+at+2018-1-16+10-58.png > 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.Final > > Attachments: Image+Pasted+at+2018-1-16+10-58.png, 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Bob Davis commented on JBIDE-24897: ----------------------------------- Or, just to through another option out - Include it in JBT Core Tools and also build it into Devstudio, so it's just there. I want to make sure that the JBT users can get it, while keeping it easy for Devstudio users. Bob > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ] Bob Davis commented on JBIDE-24897: ----------------------------------- IMO, it should be put into JBT "core tools". It's fine as an "optional install". Bob > add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector) > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24897 > URL: https://issues.jboss.org/browse/JBIDE-24897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: fabric8 > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.Final > > Attachments: fabric8-connector.png, stack analysis.mp4 > > > Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra] > Assuming we also want to create a Central connector to advertise this optional feature. > In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala] > Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin > Affected: > * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml) > * https://github.com/jbosstools/jbosstools-build-sites (category.xml) > * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4666) Font smoothing broken in view titles

by Vsevolod Golovanov (JIRA)

Vsevolod Golovanov created JBDS-4666: ---------------------------------------- Summary: Font smoothing broken in view titles Key: JBDS-4666 URL: https://issues.jboss.org/browse/JBDS-4666 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Affects Versions: 11.1.0.GA Environment: Windows 7, Windows 10. Reporter: Vsevolod Golovanov Attachments: font_smoothing_eclipse.png, font_smoothing_jbds.png IIRC this broke in JBDS 10. Compare Eclipse Oxygen.2: !font_smoothing_eclipse.png|thumbnail! and JBDS 11.1: !font_smoothing_jbds.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25582) Add SpringBoot M2 configurator

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25582?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25582: ------------------------------------ Default install for JBT and DevStudio in CoreTools and MavenTools + 1 Central connector > Add SpringBoot M2 configurator > ------------------------------ > > Key: JBIDE-25582 > URL: https://issues.jboss.org/browse/JBIDE-25582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > > In order to support SpringBoot apps in OpenShift server adapter, we need an M2 configurator that assign the jar utility facet to JAR packaged SpringBoot apps -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25590) Explorer: connection is not refreshed if you modify it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25590?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25590: ------------------------------------- Description: # ASSERT: have a running CDK and a connection for it in OpenShift Explorer # ASSERT: have your connection unfolded showing at least 1 project and at least 1 service # EXEC: minishift delete && minishift setup-cdk && minishift start # ASSERT: cdk starts up and picks a new ip (ex. 192.168.64.20 -> 192.168.64.21) # EXEC: in Explorer: pick "Edit Connection" in the context menu # ASSERT: connection wizard shows up # EXEC: update the server url to point to the new IP address of the cdk # EXEC: hit "Finish" Result: The explorer still shows the old project and resources. You have to manually hit "Refresh" for it to replace the initially present project and it's children by the new project (which is by default "My Project", the default project) was: # ASSERT: have a running CDK and a connection for it in OpenShift Explorer # ASSERT: have your connection unfolded showing at least 1 project and at least 1 service # EXEC: minishift delete && minishift setup-cdk && minishift start # ASSERT: cdk starts up and picks a new ip (ex. 192.168.64.20 -> 192.168.64.21) # EXEC: in Explorer: pick "Edit Connection" in the context menu # ASSERT: connection wizard shows up # EXEC: update the server url to point to the new IP address of the cdk # EXEC: hit "Finish" Result: The explorer still shows the old project and resources. You have to manually hit "Refresh" for it to switch to the new content (which is by default "MyProject", the default project) > Explorer: connection is not refreshed if you modify it > ------------------------------------------------------ > > Key: JBIDE-25590 > URL: https://issues.jboss.org/browse/JBIDE-25590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: 4.5.x > > > # ASSERT: have a running CDK and a connection for it in OpenShift Explorer > # ASSERT: have your connection unfolded showing at least 1 project and at least 1 service > # EXEC: minishift delete && minishift setup-cdk && minishift start > # ASSERT: cdk starts up and picks a new ip (ex. 192.168.64.20 -> 192.168.64.21) > # EXEC: in Explorer: pick "Edit Connection" in the context menu > # ASSERT: connection wizard shows up > # EXEC: update the server url to point to the new IP address of the cdk > # EXEC: hit "Finish" > Result: > The explorer still shows the old project and resources. You have to manually hit "Refresh" for it to replace the initially present project and it's children by the new project (which is by default "My Project", the default project) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25590) Explorer: connection is not refreshed if you modify it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25590?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25590: ------------------------------------- Fix Version/s: 4.5.x > Explorer: connection is not refreshed if you modify it > ------------------------------------------------------ > > Key: JBIDE-25590 > URL: https://issues.jboss.org/browse/JBIDE-25590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: 4.5.x > > > # ASSERT: have a running CDK and a connection for it in OpenShift Explorer > # ASSERT: have your connection unfolded showing at least 1 project and at least 1 service > # EXEC: minishift delete && minishift setup-cdk && minishift start > # ASSERT: cdk starts up and picks a new ip (ex. 192.168.64.20 -> 192.168.64.21) > # EXEC: in Explorer: pick "Edit Connection" in the context menu > # ASSERT: connection wizard shows up > # EXEC: update the server url to point to the new IP address of the cdk > # EXEC: hit "Finish" > Result: > The explorer still shows the old project and resources. You have to manually hit "Refresh" for it to switch to the new content (which is by default "MyProject", the default project) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25590) Explorer: connection is not refreshed if you modify it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25590?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25590: ------------------------------------- Labels: explorer (was: ) > Explorer: connection is not refreshed if you modify it > ------------------------------------------------------ > > Key: JBIDE-25590 > URL: https://issues.jboss.org/browse/JBIDE-25590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Priority: Minor > Labels: explorer > Fix For: 4.5.x > > > # ASSERT: have a running CDK and a connection for it in OpenShift Explorer > # ASSERT: have your connection unfolded showing at least 1 project and at least 1 service > # EXEC: minishift delete && minishift setup-cdk && minishift start > # ASSERT: cdk starts up and picks a new ip (ex. 192.168.64.20 -> 192.168.64.21) > # EXEC: in Explorer: pick "Edit Connection" in the context menu > # ASSERT: connection wizard shows up > # EXEC: update the server url to point to the new IP address of the cdk > # EXEC: hit "Finish" > Result: > The explorer still shows the old project and resources. You have to manually hit "Refresh" for it to switch to the new content (which is by default "MyProject", the default project) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 January 2018