Thanks, Juan.
> 1. If you have a maven project in the filesystem you can run mvn > eclipse:eclipse in the directory with the pom.xml. This creates the > necessary files for eclipse to recognise the project as a maven > project. After this u only have to import the project to eclipse. U > would have to import the root directory. The issue is that the project already exists in Eclipse. Is there any way for Eclipse to recognize the existing Eclipse project as a Maven project? Or do I have to re-import everything? I'd like to avoid that if possible, as these directories are all under version control, and completely redoing the directory structure would be a pain from that perspective. Thanks again for any help. On Thu, Jul 16, 2009 at 1:13 AM, Juan E. Maya <maya.j...@gmail.com> wrote: > John, there are 2 ways that i know to do this: > 1. If you have a maven project in the filesystem you can run mvn > eclipse:eclipse in the directory with the pom.xml. This creates the > necessary files for eclipse to recognise the project as a maven > project. After this u only have to import the project to eclipse. U > would have to import the root directory. > > 2. I u have the m2 pluging for eclipse u could actually run the > archetype inside eclipse to create a new project. To do this select > new->maven project. The wizard would let u choose if u want to create > a new simple project (no archetype) or in the second step would ask u > for an archetype. U can then choose the tapestry archetype from the > list. > > I guess that in ur case the first option is the easiest one because > the project already exist. However i think u would have to erase ur > current project from eclipse (not from the filesystem). > > I hope it helps > > On 7/16/09, John Frege <john.fr...@gmail.com> wrote: > > Hi all, > > Another question: > > > > I began my tapestry project by following these instructions: > > http://tapestry.apache.org/tapestry5/quickstart/ . Then after running > mvn > > package, I imported the .war file into eclipse and have been working with > > that project ever since. (I'm not entirely sure why I did it this way. > I > > think I was more or less following the instructions from the Kolesnikov > > book). They key result of this is that my pom.xml file is located at > > WebContent/META-INF/maven/[project group]/[project name]/pom.xml. > > > > Now I'm trying to get Hibernate working, and it seems like the easiest > way > > to do this is by adding dependencies to the pom.xml file and then getting > > the Maven Eclipse plugin to magically pull down all of the new .jar > files. > > Unfortunately it doesn't seem to be working that way. The plugin > doesn't > > recognize that my project even has a pom.xml file, and it forces me add a > > new one (located at the project root by default) to get the .jars. > > > > So before I proceed further and muck things up even more, does anyone > have > > any advice on how to get the maven eclipse plugin to recognize that my > > project is actually a maven project? > > > > Thanks for the help, > > John > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
