chuckle,
semantics :)
However as a long time maven user, I expect it to do one thing and it
does another.
I prefer my content separate and so I don't use the archetype because
it takes too long to fix the module and remove all the un-needed
additions than it does to just create the module by hand.
As I said before, maybe it should be optional.
- Brill
On 19-Mar-09, at 11:52 PM, Jeremy Thomerson wrote:
It's a *wicket* archetype that uses Maven as a build tool.
--
Jeremy Thomerson
http://www.wickettraining.com
On Thu, Mar 19, 2009 at 8:30 PM, Brill Pappin <[email protected]> wrote:
It's a Maven archetype is it not?
- Brill
On 19-Mar-09, at 3:22 PM, Jeremy Thomerson wrote:
On the subject of the archetype though, it *should* be doing the
maven
standard thing by default... maybe offering you a choice but the
default
should be into the resources directory.
Why should the *wicket* archetype be doing the *maven* standard
thing?
This
is the wicket standard way of doing things, which means that for the
wicket
archetype, it is the correct way.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
