I have a multi-module project, only two modules, where Module-A creates a jar 
during phase=package goal=jar using classifier=stubs.  Module-B has it's only 
dependency set to this stubs jar which Module-A creates.  When I run the 
top-level pom as 'maven package', all of Module-A gets created fine but then 
fails at Module-B because the dependency on the stubs jar from Module-A cannot 
be found.  Is this the way it's suppose to work?  I don't think a multi-module 
project build should fail because of dependencies between the modules.  What 
can I be doing wrong?  Is this a quark of the Eclipse m2 plugin?

Reply via email to