we should have the aggregate module explained for the reason in mine and martijn's emails. we should simply change it so it doesnt deploy any artifacts, just a pom. non-maven users will have to figure it out.
-igor On Mon, Jan 24, 2011 at 10:43 AM, Jeremy Thomerson <jer...@wickettraining.com> wrote: > On Mon, Jan 24, 2011 at 12:43 PM, Jeremy Thomerson < > jer...@wickettraining.com> wrote: > >> On Mon, Jan 24, 2011 at 12:36 PM, Martin Grigorov >> <mgrigo...@apache.org>wrote: >> >>> Let's think now what problems would cause making -extentions (and all >>> other >>> except -util and -request) depending on wicket.jar >>> >> >> IMHO, we do *not* want wicket.jar to even be available in Maven. The >> aggregate jar should be only for those who do not use Maven. Those who use >> it should just change from "wicket" to "wicket-core" when they upgrade >> versions and everything will continue to work. >> > > Should have mentioned the reason again for this: to avoid the possibility of > Maven users having duplicate classes in the classpath. > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* >
