[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-426) Add info about JBDS Central TP zip

[Michelle Murray (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923368#comment-12923368 ] 

Michelle Murray commented on TOOLSDOC-426:
------------------------------------------

For JBDS, it needs to have a JBDS URL, like the update zip. So yes, a zip should be pulled from jbt site and pushed elsewhere.

Info I have about the update site is:
"You can download the update .zip from https://access.redhat.com on the Customer Portal website or https://devstudio.jboss.com/updates/7.0/ on the Red Hat JBoss Developer update website."

Can we duplicate this for central zip? so have it on access.redhat and devstudio.blah?
                
> Add info about JBDS Central TP zip
> ----------------------------------
>
>                 Key: TOOLSDOC-426
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-426
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: User Guide - JBoss Central & JBoss Perspective
>    Affects Versions: 4.1.1
>            Reporter: Michelle Murray
>            Assignee: Michelle Murray
>             Fix For: 4.1.1
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> JBDS Central TP (3rd party) zip enables user to install 3rd party plug-ins while offline.
> How is this implemented?
> * Do users initiate the install download of Central TP from within IDE (like JBoss Central examples offline)?
> * Or do users download the zip from access.redhat (+ other sites) like the update zip?
> * And once users have zip how do they install bits of it? Window > Install New Software and point to zip on system (like install from update zip)? 
> Will require a new section in User Guide, Central chapter, probably in customization section.

--
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