-
Task
-
Resolution: Done
-
Major
-
4.13.0.Final
-
None
-
devex #179 Jan/Feb 2020, devex #180 Feb/Mar 2020
-
3
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.
- relates to
-
-
- Resolved
-
[JBIDE-26987] Deprecate vpe/forge/jst components
Hi stephane.bouchet and jmaury@redhat.com, we should also mark forge and jst server in central as deprecated, as it has been done for Livereload. Thank you! Josef
Stephane Bouchet
added a comment - I second jmaury@redhat.com about warn the user that we still ship as is the tooling as our best effort only, starting with 4.14 version.
Stephane Bouchet
added a comment - I second jmaury@redhat.com about warn the user that we still ship as is the tooling as our best effort only, starting with 4.14 version. 
Jeff MAURY
added a comment - I would vote for the second option, it is important to state that it is not supported again.
Jeff MAURY
added a comment - I would vote for the second option, it is important to state that it is not supported again. 
Supriya Takkhi (Inactive)
added a comment - Hello stephane.bouchet and jmaury@redhat.com. Here is what I have right now: "Although the Forge tooling is a part of the current release of Red Hat CodeReady Studio, it is not tested anymore." To me, this is vague. Should we not tell the user about it not being supported anymore. Better still, sate: Although the Forge tooling is a part of the current release of Red Hat CodeReady Studio, it is not tested and is not supported starting with version <studio-version>."
Please let me know what you both think about this. Thanks!
Supriya Takkhi (Inactive)
added a comment - Hello stephane.bouchet and jmaury@redhat.com . Here is what I have right now: "Although the Forge tooling is a part of the current release of Red Hat CodeReady Studio, it is not tested anymore." To me, this is vague. Should we not tell the user about it not being supported anymore. Better still, sate: Although the Forge tooling is a part of the current release of Red Hat CodeReady Studio, it is not tested and is not supported starting with version <studio-version>."
Please let me know what you both think about this. Thanks! Supriya Takkhi (Inactive)
added a comment - Thanks for letting me know about this, jkopriva@redhat.com! I have created an RHDEVDOCS JIRA for this and have added it to a future sprint (https://issues.redhat.com/browse/RHDEVDOCS-1540).
Supriya Takkhi (Inactive)
added a comment - Thanks for letting me know about this, jkopriva@redhat.com ! I have created an RHDEVDOCS JIRA for this and have added it to a future sprint ( https://issues.redhat.com/browse/RHDEVDOCS-1540 ). supriya.bharadwaj Hi, we will also need to update doc regarding to this JIRA. Ping me, if you need more info. Thank you!
in central, there is only 2 installed entry for forge and jst, none for visual page editor, see :
not sure if those need to be changed, though.
Stephane Bouchet
added a comment - - edited in central, there is only 2 installed entry for forge and jst, none for visual page editor, see :
not sure if those need to be changed, though. Jeff MAURY
added a comment - What needs to be clarified is if this requires some changes in Central. The only other places are in website and QE
Jeff MAURY
added a comment - What needs to be clarified is if this requires some changes in Central. The only other places are in website and QE 
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