<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 24, 2014 at 4:31 PM, Stan Silvert <span dir="ltr"><<a href="mailto:ssilvert@redhat.com" target="_blank">ssilvert@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>I'm hoping that it won't be long before
the web console is a separate download that merely connects to
WildFly/EAP. At that point we would not ship web console with the
server and this won't really matter any more.<br></div></blockquote><div>Yes but until that is done, we can still have trimmed console. <br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
I assume that if we do trim the console, it will be for WildFly
only? That's probably a good thing but we would need to explain
why the EAP download is so much larger.<br></div></blockquote><div> Yes wildfly only, why would we need to explain EAP download size, there is so many things different in EAP that it really does not make sense to explain details like that.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
Also note that localization is not just for logging messages and
exceptions. Some DMR operations are localized too and presumably
the result does show up in the web console UI.<span class="HOEnZb"><font color="#888888"></font></span></div></blockquote></div>Yes, also DMR operations can be localized, but we don't ship translations in WildFly but only in EAP. so again, this does not apply to wildfly as it is right now.<br>
<br>--<br></div><div class="gmail_extra">tomaz</div></div>