March 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27069) JPA version 2.2 cannot be set in RH CRS while creating new Dynamic Web Project

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27069?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27069: ------------------------------------ Component/s: hibernate > JPA version 2.2 cannot be set in RH CRS while creating new Dynamic Web Project > ------------------------------------------------------------------------------ > > Key: JBIDE-27069 > URL: https://issues.redhat.com/browse/JBIDE-27069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Koen Aers > Priority: Major > Fix For: 4.14.0.Final > > Attachments: JPA_version.png > > > JPA version 2.2 cannot be set in RH CRS while creating new Dynamic Web Project. The highest offered version is 2.1. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27069) JPA version 2.2 cannot be set in RH CRS while creating new Dynamic Web Project

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27069?page=com.atlassian.jira.plug... ] Zbyněk Červinka updated JBIDE-27069: ------------------------------------ Fix Version/s: 4.14.0.Final (was: 4.15.x) > JPA version 2.2 cannot be set in RH CRS while creating new Dynamic Web Project > ------------------------------------------------------------------------------ > > Key: JBIDE-27069 > URL: https://issues.redhat.com/browse/JBIDE-27069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.14.0.Final > Reporter: Zbyněk Červinka > Assignee: Koen Aers > Priority: Major > Fix For: 4.14.0.Final > > Attachments: JPA_version.png > > > JPA version 2.2 cannot be set in RH CRS while creating new Dynamic Web Project. The highest offered version is 2.1. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26987) Deprecate vpe/forge/jst components

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-26987?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-26987. --------------------------------- Closing. Components are correctly marked as deprecated. Verified in: Red Hat CodeReady Studio Version: 12.14.0.GA Build id: GA-v20200227-0726-B6011 Build date: 20200227-0726 > Deprecate vpe/forge/jst components > ---------------------------------- > > Key: JBIDE-26987 > URL: https://issues.redhat.com/browse/JBIDE-26987 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, forge, jst, visual-page-editor-core > Affects Versions: 4.13.0.Final > Reporter: Stephane Bouchet > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.Final > > Attachments: Capture d’écran de 2019-12-19 10-55-02.png, Capture d’écran de 2019-12-19 10-55-16.png > > > Mark following components as not fully tested anymore : > - VPE > - Forge > - JST > The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27077) Extensions with status other than preview should get status displayed

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27077?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-27077. --------------------------------- Closing, PR is merged. Verified in: Red Hat CodeReady Studio Version: 12.14.0.GA Build id: GA-v20200227-0726-B6011 Build date: 20200227-0726 > Extensions with status other than preview should get status displayed > --------------------------------------------------------------------- > > Key: JBIDE-27077 > URL: https://issues.redhat.com/browse/JBIDE-27077 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27083) Process management for running odo cli instances

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-27083: ---------------------------------- Summary: Process management for running odo cli instances Key: JBIDE-27083 URL: https://issues.redhat.com/browse/JBIDE-27083 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.14.0.Final Reporter: Jeff MAURY Assignee: Stephane Bouchet Fix For: 4.15.0.AM1 While working on the odo based explorer to JBoss Tools, I noticed that we are starting long running process and those processes are not managed / controlled once launched. I think we should do and I will explain my proposition. The long processes are the following: * watch * follow log * debug Less critical , we also have describe, list services and component and in general each time we launch odo in a terminal. This is less critical because they are less long living. The problem that we have is: * we should stop them when context is switched * we should stop them when tooling stops (seems VSCode is handling that properly) * we should stop them when we undeploy/delete a component Another plus is that managing them will prevent multiple executions of the same task and control of state for the debug. Here is my proposition: each time we start a long running process we keep it at the OdoCli (for JBoss Tools / IJ) level in a map that is keyed by project / application / component / action-type. Then, we can: * while processing delete / undeploy, scan the map to find proper processes to stop * while processing debug we can check that debug is already running or not * for cleanup before tooling exit or context switch we should add a reset method (this is required btw for proxy support as we need to recompute the HTTPS_PROXY env variable that will be passed to future odo executions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26988) Mark old EAP runtimes not fully supported anymore

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-26988?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-26988. --------------------------------- Closing, PR is merged and old runtimes are marked correctly. Verified in: Red Hat CodeReady Studio Version: 12.14.0.GA Build id: GA-v20200227-0726-B6011 Build date: 20200227-0726 > Mark old EAP runtimes not fully supported anymore > ------------------------------------------------- > > Key: JBIDE-26988 > URL: https://issues.redhat.com/browse/JBIDE-26988 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.14.0.AM1 > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > EAP 5.x and 6.x are out of Maintenance support as of today, we should mark them as not fully tested anymore, but not remove them off. > see https://access.redhat.com/support/policy/updates/jboss_notes for dates. > also this article should be updated : https://access.redhat.com/articles/113373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26994) Provide an odo based developer experience

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-26994?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-26994. --------------------------------- Closing, issues in epic are closed. > Provide an odo based developer experience > ----------------------------------------- > > Key: JBIDE-26994 > URL: https://issues.redhat.com/browse/JBIDE-26994 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27038) Openshift ODO view should be opened by default

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27038?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-27038. --------------------------------- Closing - works as expected. Verified in: Red Hat CodeReady Studio Version: 12.14.0.GA Build id: GA-v20200227-0726-B6011 Build date: 20200227-0726 > Openshift ODO view should be opened by default > ---------------------------------------------- > > Key: JBIDE-27038 > URL: https://issues.redhat.com/browse/JBIDE-27038 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > In JBoss perspective is opened by default OpenShift Explorer, but OpenShift ODO view is not opened. > In my opinion we should have also this view opened by default to promote it. > In current state this feature is quite hidden. > Tested in: > Red Hat CodeReady Studio > Version: 12.14.0.GA > Build id: GA-v20200205-0411-B5842 > Build date: 20200205-0411 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-27016) Polish odo based explorer

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27016?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-27016. --------------------------------- Closing. Works as expected. Verified in: Red Hat CodeReady Studio Version: 12.14.0.GA Build id: GA-v20200227-0726-B6011 Build date: 20200227-0726 > Polish odo based explorer > ------------------------- > > Key: JBIDE-27016 > URL: https://issues.redhat.com/browse/JBIDE-27016 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > Tasks to be completed: > * add icons to the tree > * implement delete handlers > * Update component state after push > * OpenConsole DashBoard > * Describe Application > * Component > ** Create URL > ** Create Storage > ** Describe > ** Link Component > ** Link Service > ** Debug > ** Undeploy > ** Delete > * Service > ** Link Component > ** Describe > ** Delete > * URL > ** Open In Browser > ** Delete > * Storage > ** Delete > * -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug... ] Josef Kopriva commented on JBIDE-26740: --------------------------------------- [~nimo22] Maybe this pattern will work "\.class$" > add option to Wildfly-Overview to "auto-restart" after publishing > ----------------------------------------------------------------- > > Key: JBIDE-26740 > URL: https://issues.redhat.com/browse/JBIDE-26740 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.12.0.Final > Reporter: nimo stephan > Assignee: Robert Stryker > Priority: Critical > Fix For: 4.14.0.Final > > > Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. > Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020