All they have to do is unziping the maven.zip and set the PATH. Really, all other options - _including_ manual eclipse project config and ANT setup - are _much_ more time consuming than this.
You don't even have to give them a share and create a logon for each of the students. Simply direct them to http://maven.apache.org/download LieGrue, strub --- Ian Petzer <ianpet...@gmail.com> schrieb am Sa, 28.2.2009: > Von: Ian Petzer <ianpet...@gmail.com> > Betreff: Re: "Un-mavenize" a Maven2 project ? > An: "Maven Users List" <users@maven.apache.org> > Datum: Samstag, 28. Februar 2009, 21:25 > Hi Alessio, > > A possible solution to your problem that would allow you to > keep your > mavenised project and isolate your students from Maven > would be: > > 1) Generate an eclipse project using Maven > 2) Create a lib folder in your project structure (at the > same level as src) > 3) Manually or automatically copy the the project > dependencies from your > local repo into the lib folder (maintaining their relative > directory > structures) > 4) Distribute the project to your students. Each of them > will have to use > the 'Import existing eclipse project' option to get > it into their workspace. > 5) All of the project dependencies are mapped relative to > the M2_REPO > variable, so your students would have to create this > variable and then point > it at the lib folder containing the dependencies. > > By this point they should be up and running and ready to > code. > > I haven't tried this but I think it should work fine. > You could also > distribute the lib folder seperately to the project if you > preferred that. > > Ian > > > > > On Fri, Feb 27, 2009 at 6:44 PM, Mark Struberg > <strub...@yahoo.de> wrote: > > > but ant must be installed also before it can be used. > And installing ant is > > the same effort than installing maven. > > So this will not add anything to his problem. > > > > LieGrue, > > strub > > > > > > --- David Weintraub <qazw...@gmail.com> schrieb > am Fr, 27.2.2009: > > > > > Von: David Weintraub <qazw...@gmail.com> > > > Betreff: Re: "Un-mavenize" a Maven2 > project ? > > > An: "Maven Users List" > <users@maven.apache.org> > > > Datum: Freitag, 27. Februar 2009, 19:18 > > > Would Ant be okay to use? > > > > > > You don't have to demavenize a thing -- just > add a > > > build.xml to your project. > > > > > > We converted many of our projects from Ant to > Maven, but > > > still have > > > both the build.xml and pom.xml in the root > directory. I > > > even removed > > > the third party jars from our repository. > Instead, I added > > > Ant's <get> > > > task to the build.xml to fetch the needed jars. > It is up to > > > the tech > > > leads to decide whether to use Maven or Ant in > our > > > continuous build > > > process although more and more projects are now > being built > > > with > > > Maven. > > > > > > Then again, installed Maven, set the settings.xml > in the > > > Maven > > > directory, then tarred it up and pass it out to > the > > > students. It's > > > pretty self contained. All they need to do is > untar it > > > somewhere, and > > > put a link to the "mvn" script into > their PATH. > > > That will allow the > > > students to learn Maven while they are at it. > > > > > > Might as well let your students learn how to use > Maven now > > > while their > > > brains are still soft and moist rather than wait > a few > > > years after > > > brain hardening has started to set in. > > > > > > On Fri, Feb 27, 2009 at 2:19 AM, Alessio Pace > > > <alessio.p...@gmail.com> wrote: > > > > Hi, > > > > > > > > a project I'm working on is built by > Maven2. It is > > > a single module, it uses > > > > M2 merely for dependency managament. > > > > > > > > I have to let some students play with it as > part of a > > > lab project. Their > > > > machines just have plain Eclipse, and the > users are > > > Maven-unaware, and I > > > > can't afford to make them pre-install > Maven or > > > install it during the lab > > > > session (too few hours). > > > > > > > > What I wanted to do is to > "un-mavenize" the > > > project, creating a separate > > > > source tree in the old fashion: without the > pom.xml > > > but with a libs > > > > directory filled with all the jars my > project depends > > > on. Possibly also with > > > > the Eclipse .project and .classpath files > already > > > configured (ok ok, this is > > > > optional). > > > > > > > > Thanks in advance for any suggestion on how > to achieve > > > that, or with > > > > comments if you ever had to deal with such a > situation > > > (and possibly if you > > > > want me to discourage to go with the > un-mavenize > > > process) > > > > > > > > Regards, > > > > Alessio Pace. > > > > > > > > > > > > > > > > -- > > > -- > > > David Weintraub > > > qazw...@gmail.com > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: > > > users-h...@maven.apache.org > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > users-unsubscr...@maven.apache.org > > For additional commands, e-mail: > users-h...@maven.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
