On 9/28/05, Brett Porter [EMAIL PROTECTED] wrote:
I think its because the project you are depending on is in the
reactor, and its probably a bug.
Basically, its trying to use the built version of that project, but
projects are only identified by group:artifactId
Okay - filed issue MNG-1041.
Folks,
It seems like there is a collision between dependencies from the same
project but with different classifiers, causing only the main
dependency artifact to be present on the compilation classpath.
This example will look familiar to anyone following a previous public
mock api thread. :-)
I think its because the project you are depending on is in the
reactor, and its probably a bug.
Basically, its trying to use the built version of that project, but
projects are only identified by group:artifactId
- Brett
On 9/28/05, John Fallows [EMAIL PROTECTED] wrote:
Folks,
It seems like