Bugzilla – Full Text Bug Listing
| Summary: | several projects do not provide pack.gz files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> | ||||
| Component: | Cross-Project | Assignee: | David Williams <david_williams> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | g.watson, kaloyan | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
PTP will include packed jars in the update site from now on. The Libra nightly p2 repository is already with pack200 optimization. The next build that will be promoted to Indigo (RC4) will contain packed jars. The final numbers for RC4 were better: Check of packed and not packed bundles. Number of jar files 3637 Number of pack.gz files 2768 Difference, number of jar files to check: 869 Checked 869 of 869. Errors found: 183 I'm sure some of those 183 can not be packed, but hopefully we can reduce the number, or at least better understand why there's so many that can not be packed. |
Created attachment 196620 [details] stats related to pack200 (or not) for Indigo RC2 files In this test, we'd never expect "complete" success, because some jars have been found to not be able to be packed (based on some particular patterns of java code, or something ... ) But, looking at the list of 300 jars that should be packed, it seems some patterns indicate the project simply doesn't do it. Again, an important requirement .. can reduce bandwidth during remote p2 installs.