On Fri, Feb 27, 2009 at 8:24 AM, Ketan Khairnar <ketan.khair...@gmail.com>wrote:
> write a ant script to move maven project to new directory with standard > eclipse project format. > > Once you open a project in eclipse class-path entries can be added. > > this is partial automation though Hi, thanks for your answer. I was wondering, but what about dependency resolution? Regards, Alessio Pace. > > > On Fri, Feb 27, 2009 at 12:49 PM, 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. > > >
