<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi.<br>
<br>
Feedback from GSS could be useful for this topic too. If batch
script would just do call out to their .ps1 counter parts [1], it
may broke <span id="result_box" class="short_text" lang="en"><span
class="hps alt-edited">automatization</span><span class=""></span></span>
of some of our customers.<br>
<br>
Marek<br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/wildfly/wildfly-core/pull/1126">https://github.com/wildfly/wildfly-core/pull/1126</a><br>
<br>
<div class="moz-cite-prefix">On 09/29/2015 05:29 PM, Tomaž Cerar
wrote:<br>
</div>
<blockquote
cite="mid:CAMquZP631wcqL=1-ZnnKpT1NE1Lj4ORYKfeRqBMHvKevL4RC0A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>Hey guys,<br>
<br>
<br>
</div>
just heads up, I've managed to prepare[1] all powershell
scripts to replace the aging .bat ones.<br>
<br>
</div>
New scripts unify most of the shared "code" that all scripts
use by including common.ps1,<br>
</div>
<div>and each script only has the code that differs from common
behavior they all share.<br>
<br>
</div>
<div>As result of move we now have much more reliable and faster
scripts that share common code,<br>
</div>
<div>which helps with maintaining a lot.<br>
<br>
</div>
<div>New scripts (domain.ps1 & standalone.ps1) now support
--background (also controllable via .conf.ps1) <br>
option that runs the process in background and remembers its
pid and as such add support for <br>
</div>
<div>feature that until now was only in *nix version of scripts.<br>
</div>
<div>
<div><br>
</div>
<div>I would like to propose this PR for inclusion to WildFly
10. As it doesn't alter any existing behavior<br>
</div>
<div>but just adds & improve the script experience on
Windows.<br>
</div>
<div><br>
</div>
<div>As we get to test and verify that new scripts don't
break/include any currently available option/action<br>
</div>
<div>I would also like to remove the batch scripts[2], so they
would just do call out to their .ps1 counter parts.<br>
</div>
<div><br>
</div>
<div>Once this scripts get merged, I will send PR to also add
PS scripts for WildFly full defined scripts, <br>
given that most of the functionally is already in
"common.ps1" new scripts will be just simple 5 liners [3]<br>
</div>
<div><br>
<br>
--<br>
</div>
<div>tomaz<br>
</div>
<div><br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/wildfly/wildfly-core/pull/1118">https://github.com/wildfly/wildfly-core/pull/1118</a><br>
[2] <a moz-do-not-send="true"
href="https://github.com/wildfly/wildfly-core/pull/1126">https://github.com/wildfly/wildfly-core/pull/1126</a><br>
[3] <a moz-do-not-send="true"
href="https://github.com/ctomc/wildfly-core/blob/powershell/core-feature-pack/src/main/resources/content/bin/add-user.ps1">https://github.com/ctomc/wildfly-core/blob/powershell/core-feature-pack/src/main/resources/content/bin/add-user.ps1</a><br>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</blockquote>
<br>
</body>
</html>