Niclas, How strict is the release policy regarding source artifacts? Currently, our build process generates a source archive that isn't inherently buildable. It contains all of the source for Pivot, but it isn't laid out in such a way that Eclipse or our Ant script can build it. Essentially, it is a "flattened" view of the source tree, with the source for all Pivot sub-projects (Core, WTK, Web, etc.) consolidated into a single tree.
Is this acceptable, or should I modify the packaging process to produce something that is more readily buildable (assuming that the developer installs all the required library dependencies)? Thanks, Greg
