<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=SL link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US>> </span>Although we believe the new console is stable enough, we could add an <o:p></o:p></p><p class=MsoNormal><span lang=EN-US>> </span>additional endpoint in WildFly 13 for the old console. This would enable <o:p></o:p></p><p class=MsoNormal><span lang=EN-US>> </span>users to switch back and forth between the new and old console. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>How much extra fat would that bring to the server distribution?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>--</p><p class=MsoNormal>tomaz</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:hpehl@redhat.com">Harald Pehl</a><br><b>Sent: </b>petek, 02. marec 2018 10:30<br><b>To: </b><a href="mailto:wildfly-dev@lists.jboss.org">WildFly Dev</a><br><b>Subject: </b>[wildfly-dev] HAL.next / replace console in WildFly 13</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The development of HAL.next [1] has reached a point where we can replace the </p><p class=MsoNormal>existing console with HAL.next. We'd like to make this transition for </p><p class=MsoNormal>WildFly 13. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>HAL.next ships with everything which is available in the current console. </p><p class=MsoNormal>In addition there are plenty new and enhanced features. I'm currently </p><p class=MsoNormal>preparing a website which will include basic user documentation and a list </p><p class=MsoNormal>of new and enhanced features.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Although we believe the new console is stable enough, we could add an </p><p class=MsoNormal>additional endpoint in WildFly 13 for the old console. This would enable </p><p class=MsoNormal>users to switch back and forth between the new and old console. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What do you think?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>.: Harald</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[1] https://github.com/hal/hal.next</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>wildfly-dev mailing list</p><p class=MsoNormal>wildfly-dev@lists.jboss.org</p><p class=MsoNormal>https://lists.jboss.org/mailman/listinfo/wildfly-dev</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>