On 3/20/08, Ritz123 <[EMAIL PROTECTED]> wrote: > > Thanks for the quick response. > > Just to complete the thread - for ppl like me who are not too familiar with > maven - the way to force plugin version - in our case plugin-plugin is the > plugin!! Add that to Wicket top level pom.xml file under <build> section > along with other plugins. Make sure in the corresponding Plugin-Management > section you provide the exact version number. > > Maven gurus correct me if I am wrong - but thats how I resolved my issue.
Yep, that's the way I did it. The fix is in the comments of the JIRA issue I referred to before. There's also an example project attached that exhibits the behavior. The Tapestry folks think it's related to the fact that there is no source code in the archetype. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
