Re : Re: "Un-mavenize" a Maven2 project ?

[Jean-François Mathiot <jm...@servebox.com>]

Hello Alessio,
Why don't you use assembly plugin to create the second project ?
Hope this helps.
Jeff
Jean-Francois Mathiot
____________________________________

Tel : 0 821 800 891
Gsm : +33 (0) 607 967 911
____________________________________

-----Original Message-----
From: Alessio Pace <al...@gmail.com>

Date: Fri, 27 Feb 2009 08:43:01 
To: Maven Users List<us...@maven.apache.org>
Subject: Re: "Un-mavenize" a Maven2 project ?


On Fri, Feb 27, 2009 at 8:36 AM, Ketan Khairnar <ke...@gmail.com>wrote:

> simple solution would be to include classpath-entry  in .classpath eclipse
> file
>
> e.g.
>
> *<classpathentry combineaccessrules="false" kind="src"
> path="/DependencyProject"/>*



I don't know if we are talking about the exact use case I was referring to.
I would like to have re-create a project source tree with a directory of
libraries (the jars) my current project depend on, and have these jars
inside this source tree (not just in my $M2 repository).

I know I can do maven eclipse:eclipse and then copy the files listed in the
.classpath into my source tree, but I was wondering only if there was a more
custom solution for this.

Thank you anyway.

Regards,
Alessio Pace.


>
>
>
> On Fri, Feb 27, 2009 at 1:03 PM, Alessio Pace <alessio.pace@gmail.com
> >wrote:
>
> > On Fri, Feb 27, 2009 at 8:24 AM, Ketan Khairnar <
> ketan.khairnar@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.pace@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.
> > > >
> > >
> >
>