Using mvn dependency:copy-dependencies would just retrieve all your dependencies quite simply. Then, it would just be a matter of seconds to configure your eclipse project to use those downloaded jars.
Cheers 2009/2/27 Inman, Peter <[email protected]> > You could get maven working from the command line in a few minutes. > > All your users do is unzip into a standard folder and if you pre-create the > settings.xml, environment batch files and any other bits that people need, > it only takes a few minutes. I did that with my small development team, and > they managed to install it and get it working very quickly - and they have > no Maven experience. > > Stick to the command line and forget about eclipse as it makes it much > easier.... > > Pete > -----Original Message----- > From: Antonio Petrelli [mailto:[email protected]] > Sent: 27 February 2009 09:07 > To: Maven Users List > Subject: Re: "Un-mavenize" a Maven2 project ? > > 2009/2/27 Alessio Pace <[email protected]>: > > Hi thanks for your point of view, the fact is that the lab session is > only > > few hours long, so I can't afford introducing Maven or asking users to > > install it inside Eclipse (you always have someone encountering errors, > > etc..). Otherwise, surely I would have done it! > > Why not m2eclipse? > http://m2eclipse.sonatype.org/ > > Antonio > > --------------------------------------------------------------------- > 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] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
