Ok. That's my problem. I did mvn eclipse:eclipse. I wonder how I
can undo it?
Can we either disable or change the behavior of this command if it
doesn't work as expected? This is the first thing a Maven user is
going to try to do to get the project to work in Eclipse. At
minimum, the web page needs to have a DON'T DO IT warning in big
letters :-)
On 2/28/07, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Mike, I think you've already past this point, but let me still
> comment...
>
> * Do not run "mvn eclipse:eclipse", as it is incompatible with the
> maven plugin. Besides we have .classpath and .project files in all
> projects that are being actively developed.
> * M2_REPO is not needed; Maven plugin uses
> 'MAVEN2_CLASSPATH_CONTAINER' var that is already in .classpath.
>
> Andrus
>
>
> On Feb 28, 2007, at 5:53 AM, Mike Kienenberger wrote:
>
> > Looks like M2_REPO in Ecilpse also has to be defined. Probably
> > something like this, although the exact location will vary. In
> > Eclipse 3.1, it's done by going to windows -> preferences -> java ->
> > build path -> classpath variables, then clicking New and entering the
> > following values:
> >
> > Name: M2_REPO
> > Path: C:/m2/repository
> >
> > On 2/27/07, Mike Kienenberger <mkienen..mail.com> wrote:
> >> Using Eclipse with Mavenized Cayenne - http://cayenne.apache.org/
> >> eclipse.html
> >>
> >> Unfortunately this page needs some details.
> >>
> >> ==========================
> >> # Get code from Subversion and build it from command line to seed the
> >> local repository.
> >> # Create two workspaces - one for JDK 1.4 and one for 1.5 code.
> >> ==========================
> >>
> >> I'm guessing from my MyFaces maven experience that the checkout
> >> directory must be external to the workspaces created. There should
> >> probably be more explicit instructions on how to import the projects,
> >> and I suspect that "mvn eclipse:eclipse" has to be executed
> >> beforehand. You might be able to crib notes from
> >> http://wiki.apache.org/myfaces/Eclipse_IDE (The first paragraph now
> >> seems out of place with the original document, so you'll want to sort
> >> through it).
> >>
> >> ==========================
> >> # Most Maven modules that contain source code include Eclipse project
> >> files, so they can be imported in a corresponding workspace,
> >> depending
> >> on the required JDK compliance level. You don't have to import all
> >> modules, only those that you are planning to work on, as the projects
> >> do not have Eclipse-level dependencies on each other (dependencies
> >> are
> >> resolved via Maven).
> >> ==========================
> >>
> >> It's also unclear which modules should be imported into which
> >> workspace.
> >>
> >
>
>
This archive was generated by hypermail 2.0.0 : Wed Feb 28 2007 - 09:29:48 EST