| Generate pack200 versions of plugin JARs using P2? [message #48584] |
Fri, 27 February 2009 15:12 |
 Chris Williams
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
We generate p2 metadata and repositories as the ultimate build artifacts
for most of our builds. Using techniques posted before about using per
plugin qualifiers based on our SVN rev has made updating on a
trunk/branch/nightly stream much quicker. We'd still like to improve the
download size/time for first time installs, or between major releases. In
the past we'd generate pack200 versions of JARs using the siteOptimizer
application.
Is there some process or build flag to generate pack200 versions of
plugins that gets understood and folded into the p2 metadata and artifact
generation? If we run siteOptimizer after the fact, the metadata won't
know about the pack200 versions - will P2 update code still look for
sibling pack200 versions of each JAR it tries to fetch anyways? Or does
there need to be metadata about them?
|
|
|
Powered by
FUDForum. Page generated in 1.27787 seconds
] 
Search
Help
Register
Login
Home
