[
https://issues.jboss.org/browse/JBIDE-9847?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9847:
--------------------------------------
Not necessarily, but central isn't the right place to have this -
jboss central aggregates from various places - runtime download/detection etc. is better
combined.
> Why isn't this part of the runtime detection instead of in
central ?
The download ext. point is placed in the runtime plugin.
I think we could add the Download button to the runtime detection
page.
I'm not saying there shouldn't be a download button in
central - but the core extension point feels more sane to have in runtime detection.
The Download button in the central plugin enables downloading only required
runtimes/plugins. The Download button in the Runtime Detection page would enable
downloading any runtime. The core extension point is placed in the runtime plugin.
We can't do that - its api now and need to work with JBDS 4/JBT
3.2 too.
OK.
But for new extension points like the runtime download stuff better
to follow eclipse conventions.
OK.
jboss runtime extension point is not consistent
-----------------------------------------------
Key: JBIDE-9847
URL:
https://issues.jboss.org/browse/JBIDE-9847
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
"download jboss runtimes" - why not have it be about runtimes in general ?
Why isn't this part of the runtime detection instead of in central ?
Why are we using mixed cases in the xml ? thats not the convention of eclipse
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira