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.
Is there a plugin that detects when you have a version consistency problem across projects? 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? Thanks, Grant --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
