You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Alessio Pace <al...@gmail.com> on 2009/02/27 08:19:29 UTC
"Un-mavenize" a Maven2 project ?
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.
Re: "Un-mavenize" a Maven2 project ?
Posted by David Weintraub <qa...@gmail.com>.
On Fri, Feb 27, 2009 at 1:44 PM, Mark Struberg <st...@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.
Ant is included when you install Eclipse. It's one of the reasons our
developers aren't exactly on board with our conversion to Maven. They
don't have to install Ant, and Maven's configuration isn't exactly
straight forward because of the changes you have to make to the
settings.xml file in order to use our local repository.
I publish the settings.xml, and I have a preconfigured Maven install,
but you can't beat something that's already included when you download
Eclipse.
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by Mark Struberg <st...@yahoo.de>.
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 <ia...@gmail.com> schrieb am Sa, 28.2.2009:
> Von: Ian Petzer <ia...@gmail.com>
> Betreff: Re: "Un-mavenize" a Maven2 project ?
> An: "Maven Users List" <us...@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
> <st...@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 <qa...@gmail.com> schrieb
> am Fr, 27.2.2009:
> >
> > > Von: David Weintraub <qa...@gmail.com>
> > > Betreff: Re: "Un-mavenize" a Maven2
> project ?
> > > An: "Maven Users List"
> <us...@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
> > > <al...@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
> > > qazwart@gmail.com
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail:
> > > users-help@maven.apache.org
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> users-unsubscribe@maven.apache.org
> > For additional commands, e-mail:
> users-help@maven.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by Ian Petzer <ia...@gmail.com>.
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 <st...@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 <qa...@gmail.com> schrieb am Fr, 27.2.2009:
>
> > Von: David Weintraub <qa...@gmail.com>
> > Betreff: Re: "Un-mavenize" a Maven2 project ?
> > An: "Maven Users List" <us...@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
> > <al...@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
> > qazwart@gmail.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail:
> > users-help@maven.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: "Un-mavenize" a Maven2 project ?
Posted by Mark Struberg <st...@yahoo.de>.
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 <qa...@gmail.com> schrieb am Fr, 27.2.2009:
> Von: David Weintraub <qa...@gmail.com>
> Betreff: Re: "Un-mavenize" a Maven2 project ?
> An: "Maven Users List" <us...@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
> <al...@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
> qazwart@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail:
> users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by David Weintraub <qa...@gmail.com>.
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 <al...@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
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by Baptiste MATHUS <ml...@batmat.net>.
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 <pe...@mcpplc.com>
> 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:antonio.petrelli@gmail.com]
> Sent: 27 February 2009 09:07
> To: Maven Users List
> Subject: Re: "Un-mavenize" a Maven2 project ?
>
> 2009/2/27 Alessio Pace <al...@gmail.com>:
> > 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
RE: "Un-mavenize" a Maven2 project ?
Posted by "Inman, Peter" <pe...@mcpplc.com>.
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:antonio.petrelli@gmail.com]
Sent: 27 February 2009 09:07
To: Maven Users List
Subject: Re: "Un-mavenize" a Maven2 project ?
2009/2/27 Alessio Pace <al...@gmail.com>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by Antonio Petrelli <an...@gmail.com>.
2009/2/27 Alessio Pace <al...@gmail.com>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by Alessio Pace <al...@gmail.com>.
On Fri, Feb 27, 2009 at 9:45 AM, Mark Struberg <st...@yahoo.de> wrote:
> Allessandro,
>
> just my opinion (as a former student and as someone who holds lessons from
> time to time):
>
> Since maven nowadays is really a standard tool in the java world which
> almost _everyone_ uses, it would be a good point to introduce it to your
> students.
> Also other ways fumbling around with eclipse config are much more time
> consuming than downloading maven.zip.
>
> LieGrue,
> strub
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!
Regards,
Alessio Pace.
>
>
> --- Alessio Pace <al...@gmail.com> schrieb am Fr, 27.2.2009:
>
> > Von: Alessio Pace <al...@gmail.com>
> > Betreff: Re: "Un-mavenize" a Maven2 project ?
> > An: "Maven Users List" <us...@maven.apache.org>
> > Datum: Freitag, 27. Februar 2009, 8:43
> > 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.
> > > > > >
> > > > >
> > > >
> > >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re : Re: "Un-mavenize" a Maven2 project ?
Posted by 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.
> > > >
> > >
> >
>
Re: "Un-mavenize" a Maven2 project ?
Posted by Mark Struberg <st...@yahoo.de>.
Allessandro,
just my opinion (as a former student and as someone who holds lessons from time to time):
Since maven nowadays is really a standard tool in the java world which almost _everyone_ uses, it would be a good point to introduce it to your students.
Also other ways fumbling around with eclipse config are much more time consuming than downloading maven.zip.
LieGrue,
strub
--- Alessio Pace <al...@gmail.com> schrieb am Fr, 27.2.2009:
> Von: Alessio Pace <al...@gmail.com>
> Betreff: Re: "Un-mavenize" a Maven2 project ?
> An: "Maven Users List" <us...@maven.apache.org>
> Datum: Freitag, 27. Februar 2009, 8:43
> 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.
> > > > >
> > > >
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
Posted by Alessio Pace <al...@gmail.com>.
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.
> > > >
> > >
> >
>
Re: "Un-mavenize" a Maven2 project ?
Posted by Ketan Khairnar <ke...@gmail.com>.
simple solution would be to include classpath-entry in .classpath eclipse
file
e.g.
*<classpathentry combineaccessrules="false" kind="src"
path="/DependencyProject"/>*
On Fri, Feb 27, 2009 at 1:03 PM, Alessio Pace <al...@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.
> > >
> >
>
Re: "Un-mavenize" a Maven2 project ?
Posted by Alessio Pace <al...@gmail.com>.
On Fri, Feb 27, 2009 at 8:24 AM, Ketan Khairnar <ke...@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.
> >
>
Re: "Un-mavenize" a Maven2 project ?
Posted by Ketan Khairnar <ke...@gmail.com>.
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
On Fri, Feb 27, 2009 at 12:49 PM, Alessio Pace <al...@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.
>