Re: "Un-mavenize" a Maven2 project ?
On Fri, Feb 27, 2009 at 1:44 PM, Mark Struberg 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 qazw...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: "Un-mavenize" a Maven2 project ?
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 schrieb am Sa, 28.2.2009: > Von: Ian Petzer > Betreff: Re: "Un-mavenize" a Maven2 project ? > An: "Maven Users List" > 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 > 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 schrieb > am Fr, 27.2.2009: > > > > > Von: David Weintraub > > > Betreff: Re: "Un-mavenize" a Maven2 > project ? > > > An: "Maven Users List" > > > > 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 > > > 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 > > > 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 > > > &
Re: "Un-mavenize" a Maven2 project ?
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 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 schrieb am Fr, 27.2.2009: > > > Von: David Weintraub > > Betreff: Re: "Un-mavenize" a Maven2 project ? > > An: "Maven Users List" > > 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 > > 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 > > 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 > >
Re: "Un-mavenize" a Maven2 project ?
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 schrieb am Fr, 27.2.2009: > Von: David Weintraub > Betreff: Re: "Un-mavenize" a Maven2 project ? > An: "Maven Users List" > 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 > 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 > 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
Re: "Un-mavenize" a Maven2 project ?
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 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 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
Re: "Un-mavenize" a Maven2 project ?
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 > 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.petre...@gmail.com] > Sent: 27 February 2009 09:07 > To: Maven Users List > Subject: Re: "Un-mavenize" a Maven2 project ? > > 2009/2/27 Alessio Pace : > > 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-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 > > -- Baptiste MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
RE: "Un-mavenize" a Maven2 project ?
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.petre...@gmail.com] Sent: 27 February 2009 09:07 To: Maven Users List Subject: Re: "Un-mavenize" a Maven2 project ? 2009/2/27 Alessio Pace : > 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-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
Re: "Un-mavenize" a Maven2 project ?
2009/2/27 Alessio Pace : > 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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Re: "Un-mavenize" a Maven2 project ?
Hi, good point indeed, I'll give it a try! Thank you. Regards, Alessio Pace. On Fri, Feb 27, 2009 at 8:56 AM, Jean-François Mathiot < jmath...@servebox.com> wrote: > 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 > > Date: Fri, 27 Feb 2009 08:43:01 > To: Maven Users List > Subject: Re: "Un-mavenize" a Maven2 project ? > > > On Fri, Feb 27, 2009 at 8:36 AM, Ketan Khairnar >wrote: > > > simple solution would be to include classpath-entry in .classpath > eclipse > > file > > > > e.g. > > > > * > 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 > >wrote: > > > > > 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. > > > > > > > > > > > > > > > >
Re: "Un-mavenize" a Maven2 project ?
On Fri, Feb 27, 2009 at 9:45 AM, Mark Struberg 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 schrieb am Fr, 27.2.2009: > > > Von: Alessio Pace > > Betreff: Re: "Un-mavenize" a Maven2 project ? > > An: "Maven Users List" > > Datum: Freitag, 27. Februar 2009, 8:43 > > On Fri, Feb 27, 2009 at 8:36 AM, Ketan Khairnar > > wrote: > > > > > simple solution would be to include classpath-entry > > in .classpath eclipse > > > file > > > > > > e.g. > > > > > > * > 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 > > > > >wrote: > > > > > > > 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 > > > > >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-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: "Un-mavenize" a Maven2 project ?
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 schrieb am Fr, 27.2.2009: > Von: Alessio Pace > Betreff: Re: "Un-mavenize" a Maven2 project ? > An: "Maven Users List" > Datum: Freitag, 27. Februar 2009, 8:43 > On Fri, Feb 27, 2009 at 8:36 AM, Ketan Khairnar > wrote: > > > simple solution would be to include classpath-entry > in .classpath eclipse > > file > > > > e.g. > > > > * 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 > > >wrote: > > > > > 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 > > > >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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Re: "Un-mavenize" a Maven2 project ?
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 Date: Fri, 27 Feb 2009 08:43:01 To: Maven Users List Subject: Re: "Un-mavenize" a Maven2 project ? On Fri, Feb 27, 2009 at 8:36 AM, Ketan Khairnar wrote: > simple solution would be to include classpath-entry in .classpath eclipse > file > > e.g. > > * 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 >wrote: > > > 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 > > >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 ?
On Fri, Feb 27, 2009 at 8:36 AM, Ketan Khairnar wrote: > simple solution would be to include classpath-entry in .classpath eclipse > file > > e.g. > > * 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 >wrote: > > > 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 > > >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 ?
simple solution would be to include classpath-entry in .classpath eclipse file e.g. ** On Fri, Feb 27, 2009 at 1:03 PM, Alessio Pace wrote: > On Fri, Feb 27, 2009 at 8:24 AM, Ketan Khairnar >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 > >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 ?
On Fri, Feb 27, 2009 at 8:24 AM, Ketan Khairnar 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 >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 ?
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 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. >
"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.