tag:blogger.com,1999:blog-5479191305093780981.post6674087209548572066..comments2011-10-03T16:08:51.906-07:00Lex Spoonhttp://www.blogger.com/profile/13859632965228608649noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5479191305093780981.post-30986134986466949252011-10-03T16:08:51.906-07:002011-10-03T16:08:51.906-07:00This is pretty much how Maven works. You create projects. Projects produce JAR artifacts and depend on other JAR artifacts (some local, some from the entire Java world). You change a file in a project, and you need to rebuild that project. <br /><br />If the rebuilds are a problem, just refactor the project into smaller sub projects.<br /><br />Being a declarative set of dependencies (as opposed to imperative sequence of instructions to create them) also produces benefits in that Maven project information allows IDEs to import project dependency structures, it allows dependency analysis tools, and it permits search engines like http://mvnrepository.netRayhttp://www.blogger.com/profile/15500855020734247560noreply@blogger.com