[
https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-2768:
----------------------------------
Issues w/ current HTML pages and scripts, from @maxandersen 's POV:
{quote}hardcoded paths, manual tweaking needed and too many options and no simply
walkthrough{quote}
So, which of the various install paths would make the most sense as the single approach?
* install from JBDS installer.jar to default location like ~/jbdevstudio-name-of-the-jar
* install from JBDS installer.jar or JBDS update site zip into existing Eclipse 4.3 Kepler
using "BYOE" (JBoss Developer Studio Core Features) feature
* install from installer jar + some other site(s) to create a single Eclipse instance
containing JBDS + additional tooling?
[~mmusaji], WDYT? What do users need most? A single solution (if so, which one?), or a
pair of tools & a collection of examples showcasing the various ways to perform a
headless JBDS install?
Is it just "how do I install from the installer.jar w/o having to click through the
UI?" ?
Installer scripts should be linked from jbdevstudio
---------------------------------------------------
Key: JBDS-2768
URL:
https://issues.jboss.org/browse/JBDS-2768
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: installer
Affects Versions: 7.1.0.Alpha1
Reporter: Michelle Murray
Assignee: Nick Boldt
Currently availability of scripts is listed on community site:
https://www.jboss.org/tools/download/installation/update_4_1#fromscript
And that links to instructions on community site:
http://download.jboss.org/jbosstools/updates/scripted-installation/JBDS/
Given that the instructions are for JBDS, the sites should be devstudio sites. For
example, availability stated here:
https://devstudio.jboss.com/earlyaccess/7.0.0.GA.html
And linking to scripts on same base URL.
If we want to have scripts on community site then they should only be for headless JBT
install.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira