On 10/27/2015 04:04 PM, Tal Nisan wrote:
> I agree with Allon, there's no reason to have different version
> throughout the modules (again, not including GWT for obvious reasons),
> there is practically no harm I can think of in raising the version for
> all modules at once
I have updated the
I think it's a really bad practice to have different modules in the same
project with different language versions.
For GWT it seems to be required, but for the rest of the backend, I think
we should have one patch that moves the entire project in one go.
We can have the various maintainers ack it
I agree with Allon, there's no reason to have different version throughout
the modules (again, not including GWT for obvious reasons), there is
practically no harm I can think of in raising the version for all modules
at once
On Tue, Oct 27, 2015 at 10:36 AM, Allon Mureinik
Hello,
As you probably know oVirt Engine 4 will use WildFly 10, and that
requires Java 8. The version of WildFly that we currently use is 8.2.1,
and it can work with both Java 7 and Java 8. In order to ease the
transition I'm about to merge the following patch, that will require
Java 8 during
On 10/26/2015 12:05 PM, Martin Mucha wrote:
> not strictly related question: are we going to raise language level as well?
> So we can start using JDK8 features like lambdas etc?
>
> M.
>
Shortly after merging that patch I'll merge another one to raise the
language level in the RESTAPI:
not strictly related question: are we going to raise language level as well? So
we can start using JDK8 features like lambdas etc?
M.
- Original Message -
> Hello,
>
> As you probably know oVirt Engine 4 will use WildFly 10, and that
> requires Java 8. The version of WildFly that we