On Thu, Oct 6, 2016 at 9:49 PM, Martin Perina <mperina@redhat.com> wrote:

Hi Sandro,

does this means that we cannot use xmvn build with JDK 1.8? If so, then we would need to use same as engine (create Makefile which executes normal maven), right?

This means that the pach supposed to fix the bug (https://bugzilla.redhat.com/attachment.cgi?id=1207515&action=diff) is not working.

I've seen that a new patch (https://bugzilla.redhat.com/attachment.cgi?id=1207977&action=diff) has been attached to the xmvn bug (https://bugzilla.redhat.com/show_bug.cgi?id=1381883)

I'm going to rebuild xmvn using the new patch so we can test it.

 

For otopi/ovirt-host-deploy you are still using 1.7?

otopi and ovirt-host-deploy are using 1.5.

 

Thanks

Martin

On Thu, Oct 6, 2016 at 5:45 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

On Thu, Oct 6, 2016 at 4:26 PM, Piotr Kliczewski <pkliczew@redhat.com> wrote:

I added el7 [1] and simlink [2] but still the same [3] and I can see that the repo was added:

14:16:23 Adding repo centos -> https://cbs.centos.org/repos/virt7-ovirt-41-candidate/x86_64/os/

The package is correctly installed: 00:02:20.007 xmvn.noarch 0:1.3.0-5.1.el7

So the provided patch is not fixing your issue.

--

Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

--

Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com