Hi all,

I have a very interesting issue with M2 tests...
The project structure looks like this:

Parent-1.0-alpha-3-SNAPSHOT
        +A-1.0-alpha-3-SNAPSHOT
        +B-1.0-alpha-3-SNAPSHOT

A-1.0-alpha-3-SNAPSHOT depends on B-1.0-alpha-2 (not on the SNAPSHOT!)

B-1.0-alpha-3-SNAPSHOT has some changes in one of its classes which require a class that was not present in its previous release (alpha-2).

Attempting to run mvn clean test on the parent fails because one of the A's tests throws java.lang.NoClassDefFoundError complaining about the aforementioned class.
However, running mvn clean install succeeds!
Running mvn clean test on A alone succeeds also!
Removing the B reference from parent's child modules list enables us to run a successful mvn clean test on the parent!

Any suggestion?
Adrian.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to