[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13266: ---------------------------------------- {quote} 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/aggregat...) {quote} eclipse-update-site hqs been deprecated for a long time now. We need to get away from it. That was part of the concerns for JBIDE-10596. {quote} 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. {quote} Nope, it means that the update-site does not create the pack200'd bundles. It consumes them from the artifacts build. Pack200 has to be enabled on eclipse-plugin and eclipse-test-plugin builds. -- 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