Hi!
If you have a 100-dred jars, then you should really
use the declarative dependency mechanism via the pom.
Otherwise you don't get all the benefits out of maven.
Or as Sigi Goeschl always says:
Dirty remains, while quick is long forgotten
lg,
strub
--- goatwuss [EMAIL PROTECTED] schrieb:
Hello,
Thanks for the reply... the situation is that I am trying to load a project
with 100 or so jar files that I need to include in the library... I don't
want to have to manually add each one to a repository, and include a
separate dependency for each jar... I just need a quick and dirty
There's the teach a man to fish response and the give a man a fish
response. I'll try to do a bit of both.
I think the deeper question is what are your goals in migrating the
project to maven? Most users find the dependency management features of
Maven to be one of its strongest points. If
Some time ago (a few months), a user contributed a shell script (bash
iirc) which cycled through a lib directory, installed each jar into
the user's local m2 repo with generated poms, and output a long list
of dependencies that could be copied and pasted into your project's
pom.xml file to
I just need a quick and dirty way to compile this project
so you should'nt use maven ?! Take ant!
Fredy
2006/10/24, Wayne Fay [EMAIL PROTECTED]:
Some time ago (a few months), a user contributed a shell script (bash
iirc) which cycled through a lib directory, installed each jar into
the user's
