On Wed, Mar 30, 2011 at 7:20 AM, Wendy Smoak <wsm...@gmail.com> wrote: > On Wed, Mar 30, 2011 at 9:06 AM, Phillip Hellewell <ssh...@gmail.com> wrote: >> Is there any way short of recompiling Maven to allow custom tags in the >> pom.xml? >> >> Specifically, I would like to have a special tag inside <dependency>. >> It's ok if Maven ignores it; I will just look at it from my plugin >> that will parse the pom manually if it has to. > > So... what problem are you trying to solve? There may be another way > short of recompiling Maven...
I am looking for a way to specify whether a dependency should cause a version clash error or not. Currently we have a plugin in place in our parent pom that produces an error in the validate phase if there is a version clash (a dependency in the tree twice with different versions). However, we have found that there are some scenarios where we want to allow version clash. An alternative to the idea I had for adding a custom tag to the pom would be to have our version checking plugin only produce version clashes on certain components based on the name or classifier. For example, have it so that only components whose name ends with "-interfaces" can produce a version clash. If I go this route, then I won't have to do anything funky like custom tags in the pom. Phillip --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
