> There is no sane reason why anyone would put the html, js,
> css and properties resources in any place except *next* to
> the corresponding.java file. Your .java file can not function
> without the .html file. Your component will fail if the
> .properties file is not available. When the js fi
> 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
