Although we believe the new console is stable enough, we could add an additional endpoint in WildFly 13 for the old console. This would enable users to switch back and forth between the new and old console.

The development of HAL.next [1] has reached a point where we can replace

existing console with HAL.next. We'd like to make this transition for WildFly 13. HAL.next ships with everything which is available in the current console. In addition there are plenty new and enhanced features. I'm currently preparing a website which will include basic user documentation and a

of new and enhanced features. Although we believe the new console is stable enough, we could add an additional endpoint in WildFly 13 for the old console. This would enable users to switch back and forth between the new and old console. What do you think? .: Harald [1] https://github.com/hal/hal.next

On 19. Apr 2018, at 15:28, David Lloyd <david.lloyd(a)redhat.com&gt; wrote: My first impression is - it seems faster than the old console. It loaded more or less instantly in my (local) browser. So far so good! On Thu, Apr 19, 2018 at 8:12 AM, Claudio Miranda <claudio(a)claudius.com.br&gt; wrote: > Hi, just to let you know, HAL 3.0 is already merged in wildfly master > branch, so you may run it and give some feedback. > > On Fri, Mar 2, 2018 at 6:29 AM, Harald Pehl <hpehl(a)redhat.com&gt; wrote: >> The development of HAL.next [1] has reached a point where we can replace the >> existing console with HAL.next. We'd like to make this transition for >> WildFly 13. >> >> HAL.next ships with everything which is available in the current console. >> In addition there are plenty new and enhanced features. I'm currently >> preparing a website which will include basic user documentation and a list >> of new and enhanced features. >> >> Although we believe the new console is stable enough, we could add an >> additional endpoint in WildFly 13 for the old console. This would enable >> users to switch back and forth between the new and old console. >> >> What do you think? >> >> .: Harald >> >> [1] https://github.com/hal/hal.next > > > > -- > Claudio Miranda > > claudio(a)claudius.com.br > http://www.claudius.com.br > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev -- - DML

On 19. Apr 2018, at 16:21, Andrig Miller <anmiller(a)redhat.com&gt; wrote: Have a little typo on the main page of the web site: HAL ist the project name for the WildFly and JBoss EAP management console. On Thu, Apr 19, 2018 at 8:02 AM, Harald Pehl <hpehl(a)redhat.com <mailto:hpehl@redhat.com>> wrote: Glad you like it. We've setup a website for the new console, which summarises what's new and contains some background info. [1] // Harald [1] https://hal.github.io/ <https://hal.github.io/> > On 19. Apr 2018, at 15:28, David Lloyd <david.lloyd(a)redhat.com <mailto:david.lloyd@redhat.com>> wrote: > > My first impression is - it seems faster than the old console. It > loaded more or less instantly in my (local) browser. So far so good! > > On Thu, Apr 19, 2018 at 8:12 AM, Claudio Miranda > <claudio(a)claudius.com.br <mailto:claudio@claudius.com.br>> wrote: >> Hi, just to let you know, HAL 3.0 is already merged in wildfly master >> branch, so you may run it and give some feedback. >> >> On Fri, Mar 2, 2018 at 6:29 AM, Harald Pehl <hpehl(a)redhat.com <mailto:hpehl@redhat.com>> wrote: >>> The development of HAL.next [1] has reached a point where we can replace the >>> existing console with HAL.next. We'd like to make this transition for >>> WildFly 13. >>> >>> HAL.next ships with everything which is available in the current console. >>> In addition there are plenty new and enhanced features. I'm currently >>> preparing a website which will include basic user documentation and a list >>> of new and enhanced features. >>> >>> Although we believe the new console is stable enough, we could add an >>> additional endpoint in WildFly 13 for the old console. This would enable >>> users to switch back and forth between the new and old console. >>> >>> What do you think? >>> >>> .: Harald >>> >>> [1] https://github.com/hal/hal.next <https://github.com/hal/hal.next> >> >> >> >> -- >> Claudio Miranda >> >> claudio(a)claudius.com.br <mailto:claudio@claudius.com.br> >> http://www.claudius.com.br <http://www.claudius.com.br/> >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev> > > > > -- > - DML _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev> -- Andrig (Andy) T. Miller Global Platform Director, Middleware Red Hat, Inc.

Hi, just to let you know, HAL 3.0 is already merged in wildfly master branch, so you may run it and give some feedback. On Fri, Mar 2, 2018 at 6:29 AM, Harald Pehl <hpehl(a)redhat.com&gt; wrote: > The development of HAL.next [1] has reached a point where we can replace the > existing console with HAL.next. We'd like to make this transition for > WildFly 13. > > HAL.next ships with everything which is available in the current console. > In addition there are plenty new and enhanced features. I'm currently > preparing a website which will include basic user documentation and a list > of new and enhanced features. > > Although we believe the new console is stable enough, we could add an > additional endpoint in WildFly 13 for the old console. This would enable > users to switch back and forth between the new and old console. > > What do you think? > > .: Harald > > [1] https://github.com/hal/hal.next -- Claudio Miranda claudio(a)claudius.com.br http://www.claudius.com.br _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev