I think thats a good position.
I can't image that it was purposely done in order to enforce the maven
way, there are just too many people who would have broken builds.
- Brill
On 2-Apr-09, at 3:53 PM, Igor Vaynberg wrote:
i just want to say one quick thing about this.
there are two great things about maven
1) it established a convention that eliminated a lot of boilerplate
2) it does not force the convention - everything can be overridden and
customized by configuring plugins
once the authors of maven and or plugins lose sight of (2) and try to
force the convention i think most people will simply bail. personally,
if this was forced wicket or any other projects i work on would not be
using maven.
-igor
On Thu, Apr 2, 2009 at 12:43 PM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
Let's not even start this discussion again, please!
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Apr 2, 2009 at 2:34 PM, Philippe Marschall <kus...@gmx.net>
wrote:
You simply relied on a bug / undocumented featured. Move your
resources
where the belong into the resources folder.
Cheers
Philippe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
