Another way to think of this is you really shouldn't have many "jar only" modules, no?
If you're using something like CC, then each of these "jar only" modules would be separate projects. The final application (ear/war/w/e) will depend on these other modules. When it comes time to build the ear/war/etc type modules, it will pull from your repository (if you have set one up for internal use). I think the goal is to NOT build every module each and every time you need to build your application. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 11:32 AM To: Maven Users List Subject: Re: Dependency understanding problem 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.htm l#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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
