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 file can't be found your component is useless.
Wicket goes beyond the call of duty to provide developers with the means to encapsulate your components, bringing Object Oriented design and programming to the web tier. Moving the necessary resources outside the package folder into a separate directory structure breaks this encapsulation is definitely not the Wicket Way (tm). The Wicket archetype is to make building Wicket applications easier, not to make the life of maven easier. Martijn On Fri, Mar 20, 2009 at 2:35 PM, Wilhelmsen Tor Iver <[email protected]> wrote: >> 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] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
