I'm trying to compile a set of source code X that will be packaged into jar X. If I don't have an old version of jar X in the classpath, no problem. If I have old jar X in the classpath, then occasionaly source x will not compile.
Here's a way to duplicate this problem: Focus on some classes that your project makes into a jar. In your source tree take one of those classes and move it to a different package. Make sure that methods of the class are still called elsewhere in your code, although of course you've changed the import statements in your code to reflect the class's new package.
Now maven will be unable to compile your source, even though ant, your ide, and every other compilation method known to man will have no trouble with it. The reason is that your classpath is befouled with outdated information about your classes. You now have to work around that, and suddenly your build is far from the automatic whiz-bang you told your project manager about.
And right about then you want to know how to reference a jar in maven, and yet not have it be used in the classpath when compiling your code.
_________________________________________________________________
Take advantage of our limited-time introductory offer for dial-up Internet access. http://join.msn.com/?page=dept/dialup
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
