Thats just a one time work, it just cost you some time and bring you lots of benefits.you can use http://mvnrepository.com/ to find the right groupId and artifactoryId
2008/10/6 Valerio Schiavoni <[EMAIL PROTECTED]> > Hi, > > > On Sat, Oct 4, 2008 at 1:25 AM, emma.sender <[EMAIL PROTECTED]> wrote: > > > > > Hi, I'm trying to migrate a project to maven that has all the .jars in a > > lib > > folder relative to the project root folder, and I don't want to have to > > specify every .jar in a <dependency> element... Is there a way to include > > lib/*.jar in the classpath? > > > one thing that you could technically do is to define a "virtual" repository > pointing to your lib/ directory, and then specify that those dependencies > come from that repository. > Even if possible, it's a practice I would strongly discourage, and I would > go for the conventional technique. > > > WHy do you see a problem with that ? It's a do-it-once (almost) activity. > and once you define your deps in a top-level module, those are inherited by > the eventual submodules... > > > -- > http://www.linkedin.com/in/vschiavoni > http://jroller.com/vschiavoni >
