Re: plugin search?
sounds like dependency:analyze should have some more heuristics 2009/6/5 Nord, James > I didn't want to enforce it just be able to run "mvn baddeps:analyze" and > have it tell me in a more obvious way than I can see at the > Moment (and I'm talkin about non transitive dependencies). > > e.g > > mvn baddeps:analyze > > Project B,Project C both declare a dependency on com.foo.bar:bax:1.0.1 > consider using dependecyManagement. > *** Project D,Project E use incosistent versions of com.foo.bar:whizbang > (1.0.1, 1.0.4) *** > > And if there was mvn baddeps:fix_it then all the better - but the first > part is more important to me (being able to see it obviously) > > Anyway - at least my question is answered - doesn't seem like there is > anything that can do this at the moment. > > /James > > > > > My answer is always that if you want to enforce something... > > use the enforcer. > > > > Once I get 1.0 out the door I will be splitting out one or > > two versions-api and versions-impl which will probably be > > added as dependencies of the enforcer-rules-impl so that we > > can share common code. > > > > In that respect I am not opposed to adding version-reporting > > stuff to the versions plugin... but perhaps this is a use > > case for the dependency plugin to have a report... > > > > We should socialize where such a mojo should live. I don't > > want the versions-maven-plugin to have too big a scope at the > > end of the day. > > > > -Stephen > > > > P.S. > > > > I suspect it will be somthing like > > > > versions-query-api > > > > and > > > > versions-change-api > > > > To allow enforcer to only depend on the querying code > > > > 2009/6/5 Nord, James > > > > > Hi Stephen, > > > > > > I didn't see any rules that would help for this situation ( > > > > > http://maven.apache.org/enforcer/enforcer-rules/index.html). > > (without > > > writing a custom rule) > > > > > > If some custom code needs to be written I would I think it > > would fit > > > better with the versions-maven-plugin? > > > > > > /James > > > > > > > -Original Message- > > > > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > > > > Sent: 05 June 2009 11:41 > > > > To: Maven Users List > > > > Subject: Re: plugin search? > > > > > > > > I think the enforcer plugin has rules to help. > > > > > > > > 2009/6/5 Martin Höller > > > > > > > > > Hi! > > > > > > > > > > On Friday 05 June 2009 Nord, James wrote: > > > > > > Is there a plugin that anoyone knows that can analyse > > > > dependencies > > > > > > in a multi module project and then warn if you have a > > > > depenendency > > > > > > on the same artifact with a set version (ie not using > > > > > > dependencyManagement) in more than one project? > > > > > > > > > > Sounds like a job for the versions-maven-plugin [0]. I > > think the > > > > > plugin already warns you if dependencyManagement is not > > > > used. Not sure > > > > > about different versions. If it doesn't support you use > > > > case file an > > > > > enhancement request in JIRA. Maybe Stephen Connolly can > > > > provide some more details. > > > > > > > > > > hth, > > > > > - martin > > > > > > > > > > [0] http://mojo.codehaus.org/versions-maven-plugin/ > > > > > > > > > > > > > > > > > > > > ** > > > This message is confidential and intended only for > > > the addressee. If you have received this message in error, please > > > immediately notify the postmas...@nds.com and delete it from your > > > system as well as any copies. > > > The content of e-mails as well as traffic data may be > > monitored by NDS > > > for employment and security purposes. To protect the environment > > > please do not print this e-mail unless necessary. > > > > > > NDS Limited. Registered Office: One London Road, Staines, > > Middlesex, > > > TW18 4EX, United Kingdom. A company registered in England > > and Wales. &
RE: plugin search?
I didn't want to enforce it just be able to run "mvn baddeps:analyze" and have it tell me in a more obvious way than I can see at the Moment (and I'm talkin about non transitive dependencies). e.g mvn baddeps:analyze Project B,Project C both declare a dependency on com.foo.bar:bax:1.0.1 consider using dependecyManagement. *** Project D,Project E use incosistent versions of com.foo.bar:whizbang (1.0.1, 1.0.4) *** And if there was mvn baddeps:fix_it then all the better - but the first part is more important to me (being able to see it obviously) Anyway - at least my question is answered - doesn't seem like there is anything that can do this at the moment. /James > > My answer is always that if you want to enforce something... > use the enforcer. > > Once I get 1.0 out the door I will be splitting out one or > two versions-api and versions-impl which will probably be > added as dependencies of the enforcer-rules-impl so that we > can share common code. > > In that respect I am not opposed to adding version-reporting > stuff to the versions plugin... but perhaps this is a use > case for the dependency plugin to have a report... > > We should socialize where such a mojo should live. I don't > want the versions-maven-plugin to have too big a scope at the > end of the day. > > -Stephen > > P.S. > > I suspect it will be somthing like > > versions-query-api > > and > > versions-change-api > > To allow enforcer to only depend on the querying code > > 2009/6/5 Nord, James > > > Hi Stephen, > > > > I didn't see any rules that would help for this situation ( > > > http://maven.apache.org/enforcer/enforcer-rules/index.html). > (without > > writing a custom rule) > > > > If some custom code needs to be written I would I think it > would fit > > better with the versions-maven-plugin? > > > > /James > > > > > -Original Message- > > > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > > > Sent: 05 June 2009 11:41 > > > To: Maven Users List > > > Subject: Re: plugin search? > > > > > > I think the enforcer plugin has rules to help. > > > > > > 2009/6/5 Martin Höller > > > > > > > Hi! > > > > > > > > On Friday 05 June 2009 Nord, James wrote: > > > > > Is there a plugin that anoyone knows that can analyse > > > dependencies > > > > > in a multi module project and then warn if you have a > > > depenendency > > > > > on the same artifact with a set version (ie not using > > > > > dependencyManagement) in more than one project? > > > > > > > > Sounds like a job for the versions-maven-plugin [0]. I > think the > > > > plugin already warns you if dependencyManagement is not > > > used. Not sure > > > > about different versions. If it doesn't support you use > > > case file an > > > > enhancement request in JIRA. Maybe Stephen Connolly can > > > provide some more details. > > > > > > > > hth, > > > > - martin > > > > > > > > [0] http://mojo.codehaus.org/versions-maven-plugin/ > > > > > > > > > > > > > > ** > > This message is confidential and intended only for > > the addressee. If you have received this message in error, please > > immediately notify the postmas...@nds.com and delete it from your > > system as well as any copies. > > The content of e-mails as well as traffic data may be > monitored by NDS > > for employment and security purposes. To protect the environment > > please do not print this e-mail unless necessary. > > > > NDS Limited. Registered Office: One London Road, Staines, > Middlesex, > > TW18 4EX, United Kingdom. A company registered in England > and Wales. > > Registered no. 3080780. VAT no. GB 603 8808 40-00 > > > > > ** > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > ** This message is confidential and intended only for the addressee. If you have received this message i
Re: plugin search?
My answer is always that if you want to enforce something... use the enforcer. Once I get 1.0 out the door I will be splitting out one or two versions-api and versions-impl which will probably be added as dependencies of the enforcer-rules-impl so that we can share common code. In that respect I am not opposed to adding version-reporting stuff to the versions plugin... but perhaps this is a use case for the dependency plugin to have a report... We should socialize where such a mojo should live. I don't want the versions-maven-plugin to have too big a scope at the end of the day. -Stephen P.S. I suspect it will be somthing like versions-query-api and versions-change-api To allow enforcer to only depend on the querying code 2009/6/5 Nord, James > Hi Stephen, > > I didn't see any rules that would help for this situation ( > http://maven.apache.org/enforcer/enforcer-rules/index.html). (without > writing a custom rule) > > If some custom code needs to be written I would I think it would fit better > with the versions-maven-plugin? > > /James > > > -Original Message- > > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > > Sent: 05 June 2009 11:41 > > To: Maven Users List > > Subject: Re: plugin search? > > > > I think the enforcer plugin has rules to help. > > > > 2009/6/5 Martin Höller > > > > > Hi! > > > > > > On Friday 05 June 2009 Nord, James wrote: > > > > Is there a plugin that anoyone knows that can analyse > > dependencies > > > > in a multi module project and then warn if you have a > > depenendency > > > > on the same artifact with a set version (ie not using > > > > dependencyManagement) in more than one project? > > > > > > Sounds like a job for the versions-maven-plugin [0]. I think the > > > plugin already warns you if dependencyManagement is not > > used. Not sure > > > about different versions. If it doesn't support you use > > case file an > > > enhancement request in JIRA. Maybe Stephen Connolly can > > provide some more details. > > > > > > hth, > > > - martin > > > > > > [0] http://mojo.codehaus.org/versions-maven-plugin/ > > > > > > > > ** > This message is confidential and intended only for the addressee. If you > have received this message in error, please immediately notify the > postmas...@nds.com and delete it from your system as well as any copies. > The content of e-mails as well as traffic data may be monitored by NDS for > employment and security purposes. To protect the environment please do not > print this e-mail unless necessary. > > NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 > 4EX, United Kingdom. A company registered in England and Wales. Registered > no. 3080780. VAT no. GB 603 8808 40-00 > > ** > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
RE: plugin search?
Hi Stephen, I didn't see any rules that would help for this situation (http://maven.apache.org/enforcer/enforcer-rules/index.html). (without writing a custom rule) If some custom code needs to be written I would I think it would fit better with the versions-maven-plugin? /James > -Original Message- > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > Sent: 05 June 2009 11:41 > To: Maven Users List > Subject: Re: plugin search? > > I think the enforcer plugin has rules to help. > > 2009/6/5 Martin Höller > > > Hi! > > > > On Friday 05 June 2009 Nord, James wrote: > > > Is there a plugin that anoyone knows that can analyse > dependencies > > > in a multi module project and then warn if you have a > depenendency > > > on the same artifact with a set version (ie not using > > > dependencyManagement) in more than one project? > > > > Sounds like a job for the versions-maven-plugin [0]. I think the > > plugin already warns you if dependencyManagement is not > used. Not sure > > about different versions. If it doesn't support you use > case file an > > enhancement request in JIRA. Maybe Stephen Connolly can > provide some more details. > > > > hth, > > - martin > > > > [0] http://mojo.codehaus.org/versions-maven-plugin/ > > > ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: plugin search?
I think the enforcer plugin has rules to help. 2009/6/5 Martin Höller > Hi! > > On Friday 05 June 2009 Nord, James wrote: > > Is there a plugin that anoyone knows that can analyse dependencies in a > > multi module project and then warn if you have a depenendency on the > > same artifact with a set version (ie not using dependencyManagement) in > > more than one project? > > Sounds like a job for the versions-maven-plugin [0]. I think the plugin > already warns you if dependencyManagement is not used. Not sure about > different versions. If it doesn't support you use case file an enhancement > request in JIRA. Maybe Stephen Connolly can provide some more details. > > hth, > - martin > > [0] http://mojo.codehaus.org/versions-maven-plugin/ >
Re: plugin search?
Hi! On Friday 05 June 2009 Nord, James wrote: > Is there a plugin that anoyone knows that can analyse dependencies in a > multi module project and then warn if you have a depenendency on the > same artifact with a set version (ie not using dependencyManagement) in > more than one project? Sounds like a job for the versions-maven-plugin [0]. I think the plugin already warns you if dependencyManagement is not used. Not sure about different versions. If it doesn't support you use case file an enhancement request in JIRA. Maybe Stephen Connolly can provide some more details. hth, - martin [0] http://mojo.codehaus.org/versions-maven-plugin/ signature.asc Description: This is a digitally signed message part.
plugin search?
Hi all, Is there a plugin that anoyone knows that can analyse dependencies in a multi module project and then warn if you have a depenendency on the same artifact with a set version (ie not using dependencyManagement) in more than one project? ie + root pom.xml |-- project A | \ pom.xml (depenedency on foo:bar:1.0.0 , bar:bar:1.0.0) | |-- project B | \pom.xml (depnedency on foo:bar 1.0.0, joe:blogs:1.3.2) | |-- project C | \pom.xml (dependency on joe:blogs:1.3.2, bob:dillon:4.3.2) that is when run would on the root module would 1) warn about A and B both declaring foo:bar:1.0.0 (should be in dependencyManagement of A) 2) warn very loudly about B and C both declaring joe:blogs but with different versions (need to standardise on a version and use dependencyManagement). Regards, /James ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
