[
https://issues.jboss.org/browse/JBDS-2768?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBDS-2768:
-------------------------------------------
i suggested to remove them because they are not cleaned up nor ready for actual enduser
consumption.
I don't see these scripts being ready before they actually can be updated and released
and just work out of box -thats why I suggested putting them in devdocs since they are
obviously not ready.
I would like to do these as PR's - thats fine by me but
https://github.com/jbdevstudio/jbdevstudio-website/pull/29 was already just merged in and
released...so now we'll have to adjust already published stuff instead of just doing
it in a pr and push when ready.
But i'll comment on the pull29
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