| [sapphire-dev] Sapphire build changes |
I have completed the changes to make Sapphire build leverage p2’s shared bundle pool facility. This improvement will reduce the required disk footprint of a Sapphire workspace and improve performance by being better cache for previously-downloaded artifacts than what was previously implemented in the build. These changes apply to 8.2.x, 8.3.x, 9.0.x, 9.1.x and master branches. If you have a SAPPHIRE_DOWNLOADS environment variable set to share the downloads cache between Sapphire branches, you will need to set SAPPHIRE_BUNDLE_POOL environment variable for a similar effect. The default location of the shared bundle pool is [root]/releng/pool. The bundle pool is not emptied by any of the build targets, but the build does actively prune unused content with every invocation.
Key Build Targets dev-build – This target was previously called clean-start. It does a clean build of Sapphire as well as creates dev-eclipse and dev-target Eclipse installations. full-build – This is a new target. It does everything dev-build does, plus cross-builds against alternative supported configurations, runs tests, performs findbugs analysis and exports documentation. hudson-build – This is equivalent to full-build, minus the creation of dev-eclipse and dev-target Eclipse installations. Any questions? Thanks, - Konstantin |