[
https://issues.jboss.org/browse/JBIDE-19574?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-19574.
---------------------------------
Resolution: Done
I've added a bit more documentation. I've marked the extension point as internal,
and documented it. I've added some constants to IRuntimeInstaller with the currently
approved IDs (extract vs jar). The only new API for clients, then, is the use of the
setInstallationMethod(String) on a DownloadRuntime object, so I've documented those
new sections as well.
https://github.com/jbosstools/jbosstools-base/commit/30326c71541fb728c9ff...
Add API so that downloaded runtimes can be installed via java -jar
command
--------------------------------------------------------------------------
Key: JBIDE-19574
URL:
https://issues.jboss.org/browse/JBIDE-19574
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: runtime-detection, server
Affects Versions: 4.3.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.0.Alpha2
Runtime detection currently supports only 'extraction' as a method of
installation. It was recently expanded to include not just unzipping of jars, but also
extracting .tar.gz files / .tar files / etc. But there's still no API for completely
alternate methods of installation.
This JIRA should add an extension point for (basically the plumbing) to allow for
alternate installation types in general, as well as add a default java -jar installation
method as well.
It will be up to other runtimes (ie teiid etc) to USE this functionality in their own
products, but it is up to jbt-base to make sure it is feasible at the API level.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)