I think the ultimate goal is that any artifact should be able to be checked out and built without the need to install anything...
that provides the least cost entry point for a new developer to being able to participate in a systems development... look at the way the xorg project has broken itself down... kde too... they are moving in the oposite direction from monolithic build... you want to allow a developer to pickup a small well defined piece of code and be able to fix it/change it test it and verify it without having to necessarily have a full understanding of the system On Wednesday 24 October 2007 04:31, Wayne Fay wrote: > You've got to start at the beginning. Go to the simplest jar that has > the fewest dependencies, build it, and install it (mvn install). > > Then go to the next one (that probably has a dependency on the first > one) and do the same. Rinse and repeat until all jars build and are > installed. > > If these are all part of the same larger project, then you should > probably have a parent pom with <modules> specified. Then when you > build from the top parent, Maven figures out the correct build graph > and things Just Work. > > Wayne > > On 10/23/07, Danni <[EMAIL PROTECTED]> wrote: > > Hi All, > > I am new to maven. I want to use it to get some kind of versioning system > > going for our multi-project application. > > So far everything went smooth, but now i'm getting to the point where i > > want to build jars for single projects which depend on other projects. My > > question is: > > > > how do i declare a dependency on another project instead of on a > > jar-file? > > > > it seems to me maven is always looking for jars, which cant be built > > because other jars are missing to compile and package them: > > > > Compiler output: > > Missing: > > ---------- > > 1) net.tvrl.:burancore2:jar:0.1.1.1 > > > > > > with POM entry: > > > > <dependency> > > <groupId>net.tvrl</groupId> > > <artifactId>burancore2</artifactId> > > <version>0.1.1.1</version> > > </dependency> > > > > > > Of Course the Compiler cant find that jar, because it hasnt been created > > yet. To create it, the burancore is dependent on other jars, which > > themselves don't exist. > > frustrating. > > Can anyone help? > > > > Thx > > > > > > -- > > View this message in context: > > http://www.nabble.com/Dependency-understanding-problem-tf4677961s177.html > >#a13365897 Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
