On 1/15/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I myself have intentionally stayed away from artifact resolution on the branch so do you have a test project I can use. I need to be able to reproduce your problem and turn it into some form of test. So I can see what's going on and so it doesn't regress again, if it is indeed a regression.
I managed to reproduce the problem on a very simple project. I will send you the ZIP in a few minutes. In the archive, you will find a project that has 3 dependecies: A -> D v2.1 B -> D v3 C (has no transitive dependency to D) In the project, I call a class that exists in D v3 but not in D v2.1. If you launch "mvn clean compile" with M2.0.4, the build is successful, but not with M2.0.5. And the most surprising: if you remove dependency C, then both builds break... That doesn't sound good though 2.0.4 and 2.0.5 both use the same
versions of classworlds and plexus so you're sure you have the same version of the checkstyle plugin there?
Yes, I saw that both Maven 2.0.4 and 2.0.5 use the same version of classworlds, that's why I don't really know what to think about it. But I checked the log: the same version of the Checkstyle plugin is used in both cases. I will send you the log so that you can check. Fabrice.
