On 3/6/07, Guillaume Lederrey <[EMAIL PROTECTED]> wrote:
Might be ... but it did work correctly before I added the dependency on ojdbc ... strange ... I'll check and let you know.
what does happen if you build your web module only (after installing your root pom using mvn -N if necessary) ? Does it solve your problem ? I am currently troubleshooting a similar problem where I've moved some dependency declarations in a <dependencyManagement> section in a root pom, and now one dependency disappeared from the maven classpath in the sub module build although the dependency is listed in the sub-module POM !! So my build fails. Yet if I go in the sub-module, the dependency is resolved correctly and my build works. I am reviewing the mvn -X install log of the full build and find nothing particular yet. Strange... Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
