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. http://jira.codehaus.org/browse/MNG-1041 Kind Regards, John Fallows. > On 9/28/05, John Fallows <[EMAIL PROTECTED]> wrote: > > 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. :-) > > > > project/ > > api-module/ > > impl-module/ > > > > The api-module generates 2 artifacts, one with classifier "mock". > > The impl-module depends on both of these artifiacts, one with "mock" > > classifier at "test" scope and the other with no classifier at the > > default "compile" scope. > > > > During compilation of the impl-module tests, classes from the > > api-module "mock" artifact are not found on the classpath. > > > > It seems as though the "mock" artifact and the regular artifact are > > colliding, causing the "mock" artifact to be removed from the test > > compilation classpath. > > > > Both the "mock" and regular artifacts from the api-module have type > > "jar". Even when the "mock" type is changed to "zip", the same > > problem occurs. > > > > Perhaps dependency classifiers are ignored while constructing the > > compilation classpath? > > > > Kind Regards, > > John Fallows. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]