"pgier" wrote : Did you build from the deployers-impl directory? If so, maven doesn't have a way to know where the managed module is located, so it tries to download it instead. | No. I built from the root like normal. anonymous wrote : | If you build from the parent directory (aggregator) then it should be able to find the classes directory of the sibling modules. Or if you just rebuild (install) the managed project, then it will get it from the local repository. | I deleted my local repository and that fixed it so it obviously had a wrong reference somewhere. I'm still not convinced that the local repository behaves very well (correctly), i.e. how can I convince myself that when I (re)build a tagged version it is building what I think it is building? Short of deleting my local repository on a regular basis to prevent it getting into one of these frequent corrupted states? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096057#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...