On 29 Sep 2015, at 18:08, Emmanuel Hugonnet wrote:
Hum, it will break my NetBeans plugin as I rely on the shell scripts
;)
interesting - all my attempts on using the shell scripts ended with
misery since they resulted in not being able to reliably stop/start the
server since we don't get the chance to signal the process to die/stop.
Any info on how you worked around that in Netbeans ?
/max
I can easily fix this but I vote against removing the bat files this
late in the release process.
My 2 cents
Emmanuel
Le 29/09/2015 17:48, Brian Stansberry a écrit :
> Thanks for posting this.
>
> I'm curious if anyone on the list has concerns about the .bat scripts
> now delegating the powershell ones. The advantages are obvious; the
> disadvantages I really don't know.
>
> I only occasionally use Windows in a VM, so I haven't really kept up
> with what is supported in what versions of Windows. I know Powershell
> has been around a long, long time.
>
> On 9/29/15 10:29 AM, Tomaž Cerar wrote:
>> Hey guys,
>>
>>
>> just heads up, I've managed to prepare[1] all powershell scripts to
>> replace the aging .bat ones.
>>
>> New scripts unify most of the shared "code" that all scripts use by
>> including common.ps1,
>> and each script only has the code that differs from common behavior
>> they
>> all share.
>>
>> As result of move we now have much more reliable and faster scripts
>> that
>> share common code,
>> which helps with maintaining a lot.
>>
>> New scripts (domain.ps1 & standalone.ps1) now support --background
>> (also
>> controllable via .conf.ps1)
>> option that runs the process in background and remembers its pid and
>> as
>> such add support for
>> feature that until now was only in *nix version of scripts.
>>
>> I would like to propose this PR for inclusion to WildFly 10. As it
>> doesn't alter any existing behavior
>> but just adds & improve the script experience on Windows.
>>
>> As we get to test and verify that new scripts don't break/include
>> any
>> currently available option/action
>> I would also like to remove the batch scripts[2], so they would just
>> do
>> call out to their .ps1 counter parts.
>>
>> Once this scripts get merged, I will send PR to also add PS scripts
>> for
>> WildFly full defined scripts,
>> given that most of the functionally is already in "common.ps1" new
>> scripts will be just simple 5 liners [3]
>>
>>
>> --
>> tomaz
>>
>>
>> [1]
https://github.com/wildfly/wildfly-core/pull/1118
>> [2]
https://github.com/wildfly/wildfly-core/pull/1126
>> [3]
>>
https://github.com/ctomc/wildfly-core/blob/powershell/core-feature-pack/s...
>>
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
/max
http://about.me/maxandersen