On Mon, Oct 31, 2011 at 11:10 PM, Rafael Ribeiro <[email protected]> wrote: > Hilco, I am not saying that it should work without installing common but it It should work without install on ROOT level.
> fails even after installing common and the reason is cause it sees parent > as a dependency of common and fails to look it up locally thru relativePath > resolution (either with default value or forcefully specifying as This is expected as maven resolve common as dependency while the dependency in your local repo cannot find the parent in your local repo. At this point, common doesn't aware of your local source parent pom. As a general practice, you should always build your project from root until you understand how maven and your project dependency relationship works. Just a clean up suggestion for your sample poms: you don't need "<packaging>jar</packaging>" as it's default, less is more :) -Guo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
