[jbosstools-issues] [JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13266:
------------------------------------

Two comments in http://wiki.eclipse.org/Tycho/Pack200 that worry me:

a) "Note that deprecated eclipse-update-site doesn't consider packed artifacts. "

So we'll have to migrate the remaining eclipse-update-site poms to eclipse-repository (and may lose some of the post-processing steps we do right now in https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/build.xml)

b) "This does not apply on a full repository. eclipse-repository can only consume existing pack200'ed artifacts, not generate some. "

If I'm reading that correctly, I suspect that means that where today we can build an update site consisting of locally built AND upstream artifacts, in future this will have to be TWO builds: one to build stuff locally, then a second one to aggregate upstream and the local stuff into a single repo w/ pack.gz artifacts. I hope I'm wrong here, as that extra step would be a PITA.

                
> Use pack200 to speed up download and install
> --------------------------------------------
>
>                 Key: JBIDE-13266
>                 URL: https://issues.jboss.org/browse/JBIDE-13266
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: Build/Releng
>    Affects Versions: 4.0.0.CR1
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Minor
>             Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.

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