Martijn Dashorst wrote:
Our current Wicket release distribution consists of several zip files,
[...]
Wheee, this is almost getting religious. :)
Maven 2 users just, errr, use Maven 2. :)
So for the others, I'd have thought it simplest to have a single zip/tgz
download containing the wicket sub-project JARs plus all their deps. You
can easily automate this using the mvn assembly plug-in.
Maven 2 will generate a nice dependencies report, which we should
probably stick up somewhere, so if someone is not using Maven 2 and
wants the smallest set of dependency libraries, they don't need to go
hunting around to work out what they need.
-1 on all wicket sub-projects wrapped into single JAR. Spring started
out this way and has now fragmented into sub-project JARs, and they wish
they'd done it like that from the start. Most people will only use
wicket and wicket-extensions.
(I'd also suggest renaming wicket to wicket-core, as it makes it more
obvious there are other modules available, but whatever.)
Al
