at compile-time maybe :)
But you still end up with jar duplication, you just get to avoid having to think about it too much when compiling. On Fri, 14 Mar 2003, Paulo Silveira wrote: > You are looking for MAVEN, thats it.... > Jar duplication is history > > http://jakarta.apache.org/turbine/maven/ > > ------------------------ > Paulo Silveira > http://www.paulo.com.br/ > http://www.guj.com.br/ > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: sexta-feira, 14 de mar�o de 2003 13:13 > > To: [EMAIL PROTECTED] > > Subject: so many jars > > > > > > Hi, > > I'm setting up a developpement environment and a documentation system > > for a school. They need their tools to be open source so I'm > > using much > > of what is in the jakarta project. > > > > Right, now for my question : The dependancies for many projets are > > pretty much the same, projets come with the jars they depend on > > (and some do not) which makes for a lot of duplication. Is > > there a quick > > way around this, a quick way to avoid duplication? Should a > > standard be > > set to avoid such duplication? Or is this duplication justified? > > > > Cheers, > > > > David Salib > > > > > > --------------------------------------------------------------------- > > 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]
