[
https://issues.jboss.org/browse/JBIDE-20996?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-20996:
-------------------------------------
[~maxandersen] I can add a property to the DownloadRuntime object and have the UI display
this in the section where it lists project url and download url... but the problem right
now is that download runtimes pulls almost all data from stacks.yaml.
I'm not entirely sure adding a label in stacks.yaml with a user-visible string makes
sense, but I'm also pretty sure having the dl-runtimes providers add stuff for
specific runtimes only also doesn't make sense.... so I'm not quite sure
where's appropriate to list things like pre-reqs, especially when those pre-reqs could
be a few steps that need explanation in plain language, not easily represented by code.
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
Affects Versions: 4.3.0.Final
Reporter: Radim Hopp
Assignee: Rob Stryker
Fix For: 4.4.0.Alpha1
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
(v6.4.11#64026)