[jbosstools-issues] [JBoss JIRA] (JBDS-2555) JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-2555:
----------------------------------

Seeing as we now have a Central TP zip (JBDS-2623), a JBDS update site zip and the archtype offline install script (JBDS-2543), plus a script for installing JBDS headlessly (JBDS-2715), I think we're done here.

Only thing left to do, I suppose, is to provide a link to the Central TP zip from the early access page for JBDS 7.1.0.Beta1.

[~maxandersen] [~mmurray] [~mmusaji] - do you agree with the above? Should we link to the Central TP (and anything else) from the Early Access page so as to better explain offline JBDS usage? Or keep all that in a separate section of the JBDS GSG/UG docs?
                
> JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip
> ----------------------------------------------------------------------------
>
>                 Key: JBDS-2555
>                 URL: https://issues.jboss.org/browse/JBDS-2555
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: central, updatesite
>            Reporter: Jiri Pallich
>             Fix For: 7.1.0.Beta1
>
>
> Offline Usage of JBoss Central (Customers without or very slow Internet access)
> On-line once, then off-line - aka a user demo/instructional class - the  testLocal cache is usable/complete after one on-line install. Provide a script that pre-caches everything for an instructor/demo'er in the field (online once, then offline).
> Related to: https://issues.jboss.org/browse/JBDS-2535

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