On 07/27/2012 12:58 AM, Costea, George wrote:
It works fine from the CLI (I was running out of memory).  I'm still getting an 
issue with Eclipse though about a cycle being detected from the build path.

Please elaborate on this cyclic dependency (I guess this is the issue, right?)

What matters the most is that you can build from CLI.
Some of the oVirt engine mantainers do not build from Eclipse (I personally find the maven plugin to be too buggy) , but it's a matter of personal preference. We will try to help you regardlessly

Yair


-----Original Message-----
From: Oved Ourfalli [mailto:ov...@redhat.com]
Sent: Thursday, July 26, 2012 5:34 PM
To: Costea, George
Cc: engine-devel@ovirt.org
Subject: Re: [Engine-devel] Building ovirt engine instructions



----- Original Message -----
From: "George Costea"<george.cos...@netapp.com>
To: engine-devel@ovirt.org
Sent: Thursday, July 26, 2012 11:33:04 PM
Subject: [Engine-devel] Building ovirt engine instructions





I think the wiki page (
http://wiki.ovirt.org/wiki/Building_Ovirt_Engine ) to build the ovirt
engine is outdated. When I reach the deploy section, it always fails.
Is there an update to get the ear file deployed?


Can you elaborate more on the issue? What's the exact failure/error you see 
when deploying?


The Eclipse instructions (
http://wiki.ovirt.org/wiki/Building_Ovirt_Engine/IDE ) also seem to be
out of date. When I follow the steps to change project settings, I get
an error stating that “A cycle was detected in the build path of the
project...” Could we get an update on this too?



Thanks,

George


_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel

Reply via email to