Community
Participate
Working Groups
It has come to light in bug 312645 that you do not, apparently, 'pack' the org.apache.commons.discovery bundle. You presumably get from Orbit? Is there a reason why not? It should be conditioned and signed and ready for pack200, and I think the expectation is a pack.gz form provided. (There are, probably, some from Orbit that should not be packed, but think its a pretty short list ... such as the ICU4J bundles). Thanks for clarifying ...
Yes, we get the org.apache.commons.discovery from Orbit. In birt repo(http://download.eclipse.org/birt/update-site/2.6-interim/), the org.apache.commons.discovery is signed and packed. Or maybe you are talking about the org.apache.commons.discovery was shipped as FOLDER format in the BIRT build? In the map file of latest Orbit S-build S20100514103823: plugin@org.apache.commons.discovery,0.2.0=GET,http://download.eclipse.org/tools/orbit/downloads/drops/S20100514103823/bundles/org.apache.commons.discovery_0.2.0.v201004190315.zip,unpack=true It was appended with unpack=true, so this bundle was expected to be shipped as FOLDER format, right? In wtp 3.2.0RC1, org.apache.commons.discovery was shipped as folder too. So I'm confused what we can do here to resolve bug 312645?
no, not talking about 'folder' bundle, just jar vs. pack200. If you have pack.gz version and jar version, then I guess the hypothesis in bug 312645 is wrong. Maybe someone else. Feel free to close as invalid, if you are indeed saying you have both jar and pack.gz version on your site.
commons.discovery bundle on BIRT repo is packed and signed. Set as invalid.