[jbosstools-issues] [JBoss JIRA] (JBDS-2668) Bring back the JBDS Update Site zip

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-2668:
----------------------------------


I've applied these 2 PRs to put back the links to the JBDS Update Site Zip, so we can include this fix in Beta2 respin-a this weekend:

master: https://github.com/jbdevstudio/jbdevstudio-product/pull/11
Beta2x: https://github.com/jbdevstudio/jbdevstudio-product/pull/12

Update site zip has been put back on the build results page.

However, because it (like the unzipped site) now contains pack.gz jars, it's actually LARGER than the installer jar.

http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_70/installer/

    Universal Multi-Platform Standalone 480.53M
    Universal Multi-Platform EAP 6 Bundle 590.37M
    Update Site Zip 693.67M



                
> Bring back the JBDS Update Site zip
> -----------------------------------
>
>                 Key: JBDS-2668
>                 URL: https://issues.jboss.org/browse/JBDS-2668
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: installer
>    Affects Versions: 6.0.1.GA
>            Reporter: Fred Bricon
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 7.0.0.CR1
>
>
> As per discussion in JBDS-2649:
> Max said:
> {quote}we are close to GA to fix this and this is a "bug" we also had in JBDS 6.
> The content is more or less "dead weight" and should be removed but lets do that in 7.0+
> but lets make sure we separate installer.jar from updatesite.zip in docs/and uploads so
> it is not considered the same since in time installer.jar != updatesite.zip.
> {quote}
> Denis said:
> {quote}
> +1 to postpone that to 7.0+
> {quote}

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