Two options in my head: 1) Eliminate the warning. 2) Allow some means for officially defining scopes -- the problem being that the consumer is the logical place for the definition.
2011/6/27 Arnaud Héritier <aherit...@gmail.com>: > I don't have any pointer in mind except this page which doesn't say much > than a stricter validation of POM : > https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-StricterPOMValidation > But that right that in maven 2 we just ignored unknown scopes while maven 3 > throws a warning > > Arnaud > > On Mon, Jun 27, 2011 at 7:02 PM, Benson Margulies > <bimargul...@gmail.com>wrote: > >> In looking at the tomcat plugin, I noticed that it depends on using a >> custom scope, and there was commentary complaining that maven 3 >> complains. >> >> Is there a thread or a JIRA about this? I'm contemplating creating >> something like this of my own, and I'd like to know what trouble I'm >> getting myself into. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
