Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Buckminster 3.5 New and Noteworthy"
(→Convenient p2 Publishing for Headless and IDE use) |
(→Convenient p2 Publishing for Headless and IDE use) |
||
| Line 12: | Line 12: | ||
==Convenient p2 Publishing for Headless and IDE use== | ==Convenient p2 Publishing for Headless and IDE use== | ||
| − | New actions have been added in the PDE support to support the creation of p2 update sites. Actions are automatically added to publishable components. | + | New actions have been added in the PDE support to support the creation of p2 update sites. Actions are automatically added to publishable components. Below is a screenshot of the Buckminster action popup. The action "site.p2" builds the selected features, and everything it depends on, packs and signs content, generates source bundles, and outputs everything to a p2 site on disk. The various sub actions can also be invoked directly. |
| + | |||
[[Image:BuckminsterActionImage3.5NN.png]] | [[Image:BuckminsterActionImage3.5NN.png]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The fully functional defaults can be modified by passing different build properties. | The fully functional defaults can be modified by passing different build properties. | ||
Revision as of 07:42, 1 June 2009
Buckminster - Eclipse 3.5 (Galileo) - New and Noteworthy
Buckminster for Galileo 3.5 has the following new features:
- The use of Update Manager is now completely replaced by p2
- Convenient publishing to p2 repositories automatically available on publishable components
- Generation of source bundles/features is now supported.
The p2 integration
The p2 integration affects four areas:
- The eclipse.import reader was previously only capable of resolving if it found a 'site.xml' or a releng style map file. It is now capable of reading all types of repositories supported by p2.
- The 'targetPlatform' materializer has been replaced by a 'p2 materializer'.
- The buckminster installer is now based solely on the p2 director.
Convenient p2 Publishing for Headless and IDE use
New actions have been added in the PDE support to support the creation of p2 update sites. Actions are automatically added to publishable components. Below is a screenshot of the Buckminster action popup. The action "site.p2" builds the selected features, and everything it depends on, packs and signs content, generates source bundles, and outputs everything to a p2 site on disk. The various sub actions can also be invoked directly.
The fully functional defaults can be modified by passing different build properties. Sample property settings:
# Where all the output should go
buckminster.output.root=${user.home}/bmturorial
# Where the temp files should go
buckminster.temp.root=${user.home}/tmp/bmtutorial.tmp
# How .qualifier in versions should be replaced
qualifier.replacement.*=generator:lastRevision
# How the qualifier (last revision) should be formatted
generator.lastRevision.format=r{0,number,00000}
# If a site should use pack200, turn off for faster build
# site.pack200=true
# If a site should be signed
# site.signing=true
# If a site should be signed locally, or remotely at Eclipse
# signing.type=eclipse.remote
# Should local signing be performed
# local.sign=true
# Should source bundles be built and included
cbi.include.source=false
# What platforms should be built, * for "all"
target.os=*
target.ws=*
target.arch=*