Adam Gibbons wrote: > if you wrote an infinate loop that crashed your code, would it be maven's > job to pick that up too? that's essentually what you're looking for. in an > ideal world you should know which 3rd party libs work together and which > don't. > you now do know that, and once you've done something about it there will > be no issues with maven. there isn't anyway for the build tool to work out > what libs work with which others unless it exercieses all of their code in > all ways possible. surly you can see how this is outside the scope of a > build tool? > > maybe a plugin could be developed where people build up a library of > incompatabilities and a sanity check could be done by maven to ensure you > didn't have any of these incompatabilities (transient or otherwise) in > your code?
Funny enough, theres already the animal sniffer plugin (http://mojo.codehaus.org/animal-sniffer-maven-plugin/) that can be used to create something like this. It's currently used mainly for the Java runtime library, but it's by no way limited to it. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
