> It seems that I need to "install" librarya before libraryb will compile.
This is correct. Unless you are running "mvn compile" from the top parent/aggregation pom. > Is there any way to define dependencies among sibling projects like this > (that are part of the same aggregation group) so that they do not need to be > individually installed (preferably not installed at all) and Maven can > auto-detect dependencies and properly build/rebuild? Yes, if you run compile from the top parent. > Also, during development, I do not update the version tag during every > single build/debug cycle. Will Maven properly detect source changes, rebuild > necessary libraries, and update the local repository? Yes, but make sure you are using x.y.z-SNAPSHOT until you ready to freeze a version number. In the Maven world (and its a good policy in general), there is only ONE true artifact for a given groupId/artifactId/version (GAV) combination. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
