Looks like this problem is only happening when running Eclipse using the
java-gcj JVM, which is the default with Ubuntu's Eclipse package. In that
package, /usr/bin/eclipse is really a script that launches Eclipse and it
provides several ways to customize its behavior:
At a system level, you can edit /etc/eclipse/java_home to control the list
of places it will look for a */bin/java to execute.
At a per-user level, you can set JAVA_HOME and it will use that instead of
looking at /etc/eclipse/java_home.
Also at a per-user level, you can add something like this to the file
~/.eclipse/eclipserc :
JAVACMD="/usr/lib/jvm/java-1.5.0-sun/jre/bin/java"
You can also control VM arguments from the same file with something like
this:
VMARGS="-Xms128m -Xmx512m"
Anyway, switching to the Sun JVM eliminates this problem.
Hope that helps!
- John Lewis
Nick Peeples wrote:
>
> I got fed up with trying to fix it at home, so I made the plunge to
> get it up and running on WinXP Pro at work. It seems that this works
> just fine, so the variable here must be Linux (Kubuntu 7.04). Is there
> anyone who has made it threw the developers setup guide successfully
> on a similar platform?
>
> -Nick
>
> On 4/30/07, Nick Peeples <nick.peeple..mail.com> wrote:
>> 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
>> > >
>> >
>> >
>>
>
>
-- View this message in context: http://www.nabble.com/Eclipse-Maven2-plugin---build-problem--tf3667528.html#a10627429 Sent from the Cayenne - Dev mailing list archive at Nabble.com.
This archive was generated by hypermail 2.0.0 : Tue May 15 2007 - 13:38:26 EDT