I'm not disagreeing with what you want to do... I'm just saying that it would be better to write this check as an enforcer rule rather than a whole plugin.
The idea of the enforcer plugin is to enforce stuff and fail the build if the stuff has not been enforced. It sounds like you are writing a plugin to enforce something and fail the build if the thing has not been enforced... That is duplication of some code that is already in the enforcer plugin plus writing a series of checks. I'm saying write the checks, but write them in the way that will be quickest for you and involve the least amount of duplication of code (i.e. as a custom enforcer rule) 2008/9/24 陈思淼 <[EMAIL PROTECTED]> > we're a big company's project, our project combine with jar dependence's. > To > manage the dependence is a hard work to do.for example, our last accident > is > becourse of dependence override. > our project denpends on ice 3.1.0, our partner group provide us a jar > which denpends on ice 3.2.0.GBK, the ice 3.2.0.GBK is include into the > final ear package. but the 3.2 is redesign the TCP connection method from > long connect to short connect. after it deploy. our web server fall down > for > 1 hour becourse of the connection pressure. > We try to ignore this kind of accident to verify the dependence conflict > and > force to use which jar when conflict happen. > > 2008/9/24 Stephen Connolly <[EMAIL PROTECTED]> > > > On 24 September 2008 09:36, 陈思淼 <[EMAIL PROTECTED]> wrote: > > > > > I want to write a plugin which can display all the conflict dependences > > > (the > > > same groupId and artifactId but different version) in the dependences > > > graph.Is > > > the Maven-core provide this function? > > > I want to define some strategy when some conflicts happen, the build > > > process > > > fail. > > > can anybody tell me how to get this conflicts information in my plugin? > > > > > > > Failing the build is really a job for the enforcer plugin. I would write > an > > enforcer rule to enforce what you want and then add that rule to the > > enforcer configuration > > >
