[
https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-20996:
---------------------------------------
In the meantime, JBoss DV 6.2 was released (2016-08-10), so I created new JIRAs to have
that added:
JBIDE-24803
JDF-867
TBH, the value of having this available for download is a bit questionable - there is no
runtime detector for dv is there?
The warning is there, but I wonder how it works - it's not controlled by stacks.yaml:
https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.y...
So is it hardcoded somehow? What happens when the new dv requires eap 7?
DV 6.2 is shipped withou EAP. Can we do something about it in context
of Download Runtime wizard?
-------------------------------------------------------------------------------------------------
Key: JBIDE-20996
URL:
https://issues.jboss.org/browse/JBIDE-20996
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: runtime-detection, upstream
Affects Versions: 4.3.0.Final
Reporter: Radim Hopp
Assignee: Rob Stryker
Fix For: 4.5.0.AM2
It's great that now, with JBIDE-19852 and JBIDE-20769 resolved, one can download DV
6.2 using Download Runtimes wizard and have the installation path pre-filled. But the DV
6.2 installator requires EAP 6.4 already present on user's machine (and the
installation path must point to its JBOSS_HOME). If user does not have EAP 6.4, he has to
exit wizard, install EAP 6.4 and then download (again) and install DV 6.2.
Is there anything we could do to make this workflow easier.
Maybe at least tell user to install EAP 6.4 prior downloading DV 6.2?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)