Yes, I was able to do a full build using mvn install, so the
repository and cayenne are built. I did notice that a Maven
Dependencies was setup under the project, but there was nothing in
there, which striked me as a little odd, not sure if that helps at
all.
-Nick
On 4/30/07, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Hi Nick, I am successfully running on Eclipse 3.2.0 with same version
> of Maven plugin. Just to doublecheck, before importing projects in
> Eclipse, have you done a full command-line build? This seeds local
> repo and provides Maven Eclipse plugin with needed artifacts.
>
> Cheers,
> Andrus
>
>
> On Apr 30, 2007, at 5:14 AM, Nick Peeples wrote:
>
> > I'm am attempting to build Cayenne 3.0, but am running into some
> > difficulties, and was wondering if anyone has seen and climbed this
> > hill.
> >
> > I am running Eclipse 3.2.2 on Linux with the Maven2 0.0.10 (from
> > manage configuration) plugin. I have noticed two different things
> > happening:
> >
> > 1. When I import the cayenne-jdk1.5-unpublished project, eclipse never
> > seems to stop initializing the project. It just goes and goes, and the
> > JVM is taking up all of one processor. I finally kill the jvm and
> > eclipse, and the project shows up after reloading the workspace, but
> > it just feels like it didn't completely import.
> >
> > 2. If I can get eclipse up and running (see #1), then whenever I issue
> > a build Eclipse gets to 50% then stops on reading pom.xml. I am
> > relatively new to using Maven, and the is potentially the wrong way to
> > be doing things, but I can't help but thinking it is related to #1. If
> > it is the wrong way, does anyone have a guide with some maven and
> > eclipse best practices or walkthroughs, I was quite unsuccessful
> > finding any.
> >
> > Thank you for you time,
> > Nick
> >
>
>
This archive was generated by hypermail 2.0.0 : Mon Apr 30 2007 - 09:22:52 EDT