So, do I just look at the report and then go and update all the projects that need it? We have a fair amount of shared code spread across a couple of projects? Is the transitive checking going to exist in 1.1 or is that 2.0 only? I can live w/ updating the projects, just want a fast way to discover the inconsistencies. Do you think it is possible to script this easily ( a day or two)?
>>> [EMAIL PROTECTED] 08/10/05 12:45 PM >>> On Wed, Aug 10, 2005 at 06:42:09PM +0200, Trygve Laugstøl wrote: > On Wed, Aug 10, 2005 at 12:31:42PM -0400, Grant Ingersoll wrote: > > Have read http://maven.apache.org/using/managing-dependencies.html and > > it makes some sense, but am still a little confused on how to apply in > > reality. I now realize that you was asking about Maven 1 and I told you the answer for Maven 2, sorry about that. > I added a section about dependency management yesterday that you might > want to ready. Until the site is redeployed you can read it directly from > Subversion[1]. > > > > > Is there a plugin that detects when you have a version consistency > > problem across projects? > > There is a dependency report that should show you all versions of a > library in use. This is also true for Maven 1 but only on a per project basis. > > > We have several libraries that are part of our core code base that are > > used in multiple projects. What is the best way for managing/detecting > > when the libraries are out of synch. > > > > For instance, I have my core utilities library w/ versions 1.0 and 1.1. > > I have another library foo-1.0 that is dependent on core-1.0. My > > application, which needs some new feature in core-1.1 is currently > > dependent on foo-1.0. I know the solution is to go bring foo up on > > core-1.1, but what I am wondering is if there is a way to detect these > > dependencies ahead of time. Right now, I usually don't find out until > > runtime/test-time when I get a NoSuchMethodError or something along > > those lines. > > > > Any suggestions? I realize some of this problem is inherent to java > > and the lack of jar versioning capabilities. Was wondering, however, > > what people do in the real world to deal w/ this? > > Basically put all of your dependency information in a > <dependencyManagement> tag in your root pom and in your child poms > reference all dependencies by group id and artifact id only. > > [1]: > https://svn.apache.org/repos/asf/maven/components/trunk/maven-site/src/site/xdoc/dependency-mechanism.xml > > > -- > Trygve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
