> It's a *wicket* archetype that uses Maven as a build tool. But if it *breaks* the assumptions made by all other plugins used by Maven as a build tool, is it then not an archetype that *abuses* Maven as a build tool? :)
What other contexts would you want to use this *wicket* archetype that does not involve Maven? If none, why should it not create a project structure that Maven likes? Yes, you can override *anything* in Maven if you want to, but *do* you really want to? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
