Well, If you are able to turn in it into a maven assembly, or an ant build, it would become quite less cumbersome :).
It is not required to use maven or ant, but it is highly recommended to ensure you don't paint yourself into a particular process that only works on your particular toolset. Ant and maven tend to make this possible. There is one thing to take into consideration: source jars also need to be signed an contain the incubator disclaimer. Martijn On Thu, Mar 26, 2009 at 2:33 PM, Greg Brown <[email protected]> wrote: > 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 > > > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
