Not even that is needed. You can pack your dependencies with your project. You need to pack those jars in the form maven would recognize it as its repository. Then you could specify local repo (the one that sits on the file system) in your parent pom.
On Thu, Jun 18, 2009 at 12:54 PM, Massimo Lusetti <mluse...@gmail.com>wrote: > On Thu, Jun 18, 2009 at 12:37 PM, Onno Scheffers <o...@piraya.nl> wrote: > > > > > > In a small operation you can get away with doing dependency management > > > manually, but not for enterprise applications or any development of > scale. > > > > > > > > For complex projects especially, I try to keep things simple by adding > all > > dependencies directly into the version-control system. New developers can > > just check out the project, load the project-file up in IntelliJ and they > > are ready to go. > > I prefer wasting diskspace over wasting developer time. > > Having a maven's proxy let you achieve the same without wasting disk space. > Having a maven proxy is a must have facility if you really want to > work with maven. > > Regards > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
