5 a.m.
Hi all,
we plan to bump the GWT version to 2.9.0 (patch [1]).
Key changes:
1. support for building with Java 11
2. removing support for classic dev mode ( use super dev mode instead)
3. accumulated improvements and bug fixes (from versions 2.8.1, 2.8.2, 2.9.0)
Please review and check if your areas are impacted.
For details see BZ [2]
best regards,
radek
[1] https://gerrit.ovirt.org/110359/
[2] https://bugzilla.redhat.com/1860309
3:45 a.m.
On Fri, Jul 24, 2020 at 1:02 PM Radoslaw Szwajkowski <rszwajko(a)redhat.com>
wrote:
Hi all,
we plan to bump the GWT version to 2.9.0 (patch [1]).
Key changes:
1. support for building with Java 11
2. removing support for classic dev mode ( use super dev mode instead)
Is it mandatory to remove classic dev mode due to version bump? iirc, super
dev mode
as a limitation of supporting local debug only. I.e. engine should be on
the same machine as chrome.
Or is it already resolved by any chance?
3. accumulated improvements and bug fixes (from versions 2.8.1,
2.8.2,
2.9.0)
Please review and check if your areas are impacted.
For details see BZ [2]
best regards,
radek
[1] https://gerrit.ovirt.org/110359/
[2] https://bugzilla.redhat.com/1860309
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UY5ML5LKOKN...
7:28 a.m.
On Mon, Jul 27, 2020 at 10:45 AM Daniel Erez <derez(a)redhat.com> wrote:
On Fri, Jul 24, 2020 at 1:02 PM Radoslaw Szwajkowski <rszwajko(a)redhat.com> wrote:
>
> Hi all,
> we plan to bump the GWT version to 2.9.0 (patch [1]).
> Key changes:
> 1. support for building with Java 11
> 2. removing support for classic dev mode ( use super dev mode instead)
Is it mandatory to remove classic dev mode due to version bump?
Yes. Actually it stopped working already in 2017 in version 2.8.1.
It was the reason why Ovirt continued to use version 2.8.0 for so long.
For details see my comment in BZ [1]
iirc, super dev mode
as a limitation of supporting local debug only. I.e. engine should be on the same machine
as chrome.
Or is it already resolved by any chance?
Yes. In my daily work I use a remote engine (virtual machine) and
local code server.
See the instructions in ovirt-engine/README for base setup.
In my case:
1. .m2 directory and ovirt-engine repository are shared between
remote (CentOS 8) and local (Fedora 31)
2. engine build/install is executed on remote, gwt-debug is executed
locally (but re-uses artifacts from main build)
3. engine uses http - configuring https is possible but requires
extra effort - see [2]
>
> 3. accumulated improvements and bug fixes (from versions 2.8.1, 2.8.2, 2.9.0)
>
> Please review and check if your areas are impacted.
> For details see BZ [2]
>
> best regards,
> radek
>
> [1] https://gerrit.ovirt.org/110359/
> [2] https://bugzilla.redhat.com/1860309
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UY5ML5LKOKN...
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1860309#c2
[2] https://github.com/gwtproject/gwt/issues/7535
1385
days inactive
1388
days old
2 comments
2 participants
participants (2)
-
Daniel Erez -
Radoslaw Szwajkowski