Re: [discuss] How to resolve wicket aggregate classes / sources jar issues

[Ryan McKinley]

>
> [x] - Just forget about the aggregated wicket.jar and modify the wicket
> module a pom-only module.  This means Maven users can eternally depend on
> wicket only, and not care about how we (re-)structure our code.  Non-maven
> users will have to download all the separate jars, or use Ivy, or whatever.
>