February 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ] Bob Davis commented on JBIDE-25736: ----------------------------------- Thanks everyone - [~nickboldt] - your last comment makes it pretty clear to me, and the data you show on the spreadsheet is pretty compelling (showing that these plugins just are not being used). So, I'm good with: Deprecating, remove from default installation (if applicable), & create a Central connector (if not already exist): * jbosstools-portlet * jbosstools-aerogear * jbosstools-browsersim * jbosstools-livereload 2 projects to remove, since they were deprecated some time ago: * jbosstools-freemarker * jbosstools-arquillian Bob > deprecate features from JBoss Tools with low usage / low development > -------------------------------------------------------------------- > > Key: JBIDE-25736 > URL: https://issues.jboss.org/browse/JBIDE-25736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM2 > > > This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked. > * jbosstools-portlet > * jbosstools-aerogear > * jbosstools-browsersim > * jbosstools-livereload > * {color:red}-jbosstools-webservices-{color} > * {color:red}-jbosstools-javaee-{color} > * {color:red}-jbosstools-forge-{color} > These projects could be *removed*, since they were deprecated some time ago: > * jbosstools-freemarker > * jbosstools-arquillian > For supporting arguments, see this doc (RH only, sorry): > https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25736: ------------------------------------ [~rick_wagner] Yes, if you read through the comments, the {color:red}-red strike-throughs-{color} map to comments from devs or project lead (Jeff) about keeping projects I'd previously though as candidates for deprecation. At this point my suggestion is this: *4 projects to mark deprecated, remove from default installation (if applicable), & create a Central connector (if not already exist):* * jbosstools-portlet * jbosstools-aerogear * jbosstools-browsersim * jbosstools-livereload *2 projects to remove, since they were deprecated some time ago:* * jbosstools-freemarker * jbosstools-arquillian > deprecate features from JBoss Tools with low usage / low development > -------------------------------------------------------------------- > > Key: JBIDE-25736 > URL: https://issues.jboss.org/browse/JBIDE-25736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM2 > > > This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked. > * jbosstools-portlet > * jbosstools-aerogear > * jbosstools-browsersim > * jbosstools-livereload > * {color:red}-jbosstools-webservices-{color} > * {color:red}-jbosstools-javaee-{color} > * {color:red}-jbosstools-forge-{color} > These projects could be *removed*, since they were deprecated some time ago: > * jbosstools-freemarker > * jbosstools-arquillian > For supporting arguments, see this doc (RH only, sorry): > https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development

by Rick Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ] Rick Wagner commented on JBIDE-25736: ------------------------------------- Thanks for looking for ways to clean up, [~nickboldt]. I hope the 'strike-through' red line for web services means it's been spared. I'd vote to keep that one around. (Justification: We get support cases from customers with SOAP web services. When that's the case, I regularly end up using the web services functionality in DevStudio. I'd assume the customers are doing the same.) SOAP was pretty big a while back, it's going to have a long tail (like COBOL). > deprecate features from JBoss Tools with low usage / low development > -------------------------------------------------------------------- > > Key: JBIDE-25736 > URL: https://issues.jboss.org/browse/JBIDE-25736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM2 > > > This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked. > * jbosstools-portlet > * jbosstools-aerogear > * jbosstools-browsersim > * jbosstools-livereload > * {color:red}-jbosstools-webservices-{color} > * {color:red}-jbosstools-javaee-{color} > * {color:red}-jbosstools-forge-{color} > These projects could be *removed*, since they were deprecated some time ago: > * jbosstools-freemarker > * jbosstools-arquillian > For supporting arguments, see this doc (RH only, sorry): > https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24505) Isolate usage GA specific code though a separate provider

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24505?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-24505. ------------------------------ > Isolate usage GA specific code though a separate provider > --------------------------------------------------------- > > Key: JBIDE-24505 > URL: https://issues.jboss.org/browse/JBIDE-24505 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: usage > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > > In order to prepare to the switch from GA to segment.io, make the code more evolutive and isolate in a separate provider all GA specific -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4650) JDK9 Certification - aerogear-hybrid

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4650?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-4650. ---------------------------- > JDK9 Certification - aerogear-hybrid > ------------------------------------ > > Key: JBDS-4650 > URL: https://issues.jboss.org/browse/JBDS-4650 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Pavol Srna > Assignee: Pavol Srna > 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-20943) WP engines are being downloaded but not recognized in UI

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20943?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20943. ------------------------------ Verified in devstudio 11.3.0.AM1 > WP engines are being downloaded but not recognized in UI > -------------------------------------------------------- > > Key: JBIDE-20943 > URL: https://issues.jboss.org/browse/JBIDE-20943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.Final > Reporter: Pavol Srna > Assignee: Rastislav Wagner > Fix For: 4.3.x, 4.5.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=479630 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25697) New Resource Wizard: Improve error message when resource does not exist

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25697?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-25697: --------------------------------------- Hi [~jeffmaury], in which version it has been fixed? I have tried devstudio build AM2-v20180227-0424-B2123, but there is no change in showing error - still it is stacktrace and the last line is half line visible. > New Resource Wizard: Improve error message when resource does not exist > ----------------------------------------------------------------------- > > Key: JBIDE-25697 > URL: https://issues.jboss.org/browse/JBIDE-25697 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Minor > Labels: resource_wizard > Fix For: 4.5.x > > Attachments: Screenshot_20180209_104512.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > 5. Error message is not shown correctly and it shows stacktrace(see screenshot). -- 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 Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-25303: --------------------------------------- [~jeffmaury] CDK > 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. > ** -Dfabric8.generator.from=fabric8/s2i-java > # 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-25756) OpenShift Explorer: OpenShift connection is not automatically refreshed

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25756?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25756: ---------------------------------- Steps to Reproduce: 1. Create connection to OpenShift online instance 2. Create project with application 3. Delete project and immediately create new one 4. Create application in newly created project 5. The old project is still in OpenShift explorer - but when I click on project there is a error message: "User "xxx" cannot list builds in project "xxx" User "xxx" cannot list builds in project "xxx" " (I am not sure, if this is 100% reproducible) was: 1. Create connection to OpenShift online instance 2. Create project with application 3. Delete project and immediately create new one 4. Create application in newly created project 5. The old project is still in OpenShift explorer - but when I click on project there is a error message: "User "xxx" cannot list builds in project "xxx" User "xxx" cannot list builds in project "xxx" " > OpenShift Explorer: OpenShift connection is not automatically refreshed > ----------------------------------------------------------------------- > > 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 > > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25756) OpenShift Explorer: OpenShift connection is not automatically refreshed

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25756: ------------------------------------- Summary: OpenShift Explorer: OpenShift connection is not automatically refreshed 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 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)

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 February 2018