I have a software project that is roughly organized like this:
master (aggregation project)
librarya
libraryb (depends on librarya)
It seems that I need to "install" librarya before libraryb will compile.
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?
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?
--
View this message in context:
http://n2.nabble.com/Newbie-Question%3A-Dependencies-among-Sibling-Projects--tp2477109p2477109.html
Sent from the maven users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
