Description David Williams 2011-01-16 19:45:09 EST

Currently, on a builds download page, in the big table of bundles produced, we link to each bundle in that build, and link to the version in the 'bundles' directory. To avoid redundancy, we should point to the version in the 'repository/plugins' directory. Eventually, then, we could get rid of the 'bundles' directory, and provide only the 'repository'. 

On that one hand, that'd be pretty simple change to make. But, on the other hand ... currently the bundles in the 'bundles' directory are of two types; jars and zip files. This is meant as a subtle documentation that the jar files can be used as-is (as jars) but the zip files are intended to be unzipped in an installation. This corresponds to a feature.xml file's specification of unpack=false/true for a given bundle. 

Once we change to point to the bundle in 'repository/plugins' directory, all bundles will be jars. 

So, ideally, I propose, we'd still provide this documentation as part of the big table, by adding a column named "unpack?" and put a "yes" in the cells that should be unzipped in most installations. 

To do that easily, we may want to provide some special/extra file as part of the build that lists which are meant to be unpacked in installs ... the php file that produces the table could then read this file ... instead of, for example, having to read/parse the content.jar/xml file for the repository. Maybe.