I don't want that. If someone is anal about what maven is expecting, then it is their problem. I am in the business of making the best wicket development experience, from a Wicket perspective. We're using maven as a tool, we're not in the business of supplying maven with new users.
Putting all resources that belong to a component in the same physical folder as the component .java file is a best practice for Wicket users, even newbies. Doing it in any other way is opening the door to the nine hells of Maven usage and resource location. I really don't want the archetype to do anything else than it currently does, nor document such a way. The Official Wicket Way (tm) is to put all source files relating to a single unit of work in one package, in the same physical folder. If you decide to do it otherwise, it is not The Official Wicket Way. Feel free to disagree, but do it somewhere else, and in your own private projects. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
