On 17/04/12 19:31, Geert Jansen wrote:
On 04/17/2012 05:54 PM, Itamar Heim wrote:
If we can expose the shared flag though, i think the API gets more
natural. We can then only show the shared disks in the root context.
Itamar, can we expose this flag, or do you consider this flag is
On 04/18/2012 09:51 AM, Ofer Schreiber wrote:
Ever wondered why the version of oVirt's first release is 3.0.0_0001?
The answer is simple - We use ovirt-engine jar's version as our main
release version.
Personally, I think the current versioning scheme is ugly. Actually, I can't
name even
On 18/04/12 13:36, Einav Cohen wrote:
[Top Posting]
Let's try to concentrate on the subject of this thread (we can discuss shared
disks in a separate thread):
- I agree with Ori: Disks root collection should have all disks, not only
floating (shared?) disks. Disk is an important
On 04/18/2012 01:36 PM, Einav Cohen wrote:
[Top Posting]
Let's try to concentrate on the subject of this thread (we can discuss shared
disks in a separate thread):
- I agree with Ori: Disks root collection should have all disks, not only floating
(shared?) disks. Disk is an important
On 04/18/2012 01:42 PM, Juan Hernandez wrote:
...
I suggest that for the upcoming release we'll do both, have 2 release
flavors, one RPM's like we released for 3.0 (with Jboss included) and
the other one tailored for Fedora.
My suggestion is that even if we decide to have two flavors of the
Hi guys,
We're trying to be as updated as possible in oVirt development.
In order to catch up with recent changes in major distro's,
we'd like to move to Maven 3.
Current oVirt engine code actually can be built with Maven 3 now,
but we still need to handle some minor issues. Also we need
to
Hi!
I like the idea.
Could you share some the changes you plan to do to move to maven 3?
Thank you,
Laszlo
- Original Message -
From: Doron Fediuck dfedi...@redhat.com
To: engine-devel@ovirt.org, a...@ovirt.org a...@ovirt.org
Sent: Wednesday, April 18, 2012 3:15:11 PM
Subject:
Hi Laszlo,
Sure.
As I said, the code already works well with Maven 3,
so no need for further changes.
What Asaf (CC'd) discovered is a corner case of failure,
when trying to start from scratch. This means there's
no local maven repo, and Maven start fetching the
artifacts. One of the GWT
