[wildfly-dev] Windows Batch Scripts

Tristan Tarrant ttarrant at redhat.com
Mon May 27 06:26:21 EDT 2013


Powershell ?

On 05/24/2013 01:37 PM, Dimitris Andreadis wrote:
> The problem with spaces in the path on Windows always surfaces one way or another. I think
> we need better automated testing for the scripts.
>
> I agree with Stan, switching to .exe is a bad idea.
>
> On 17/05/2013 14:29, ssilvert at redhat.com wrote:
>> On 5/16/2013 9:51 PM, James R. Perkins wrote:
>>> Hello All,
>>> There was an issue found with the Windows batch scripts if the JBOSS_HOME path had a space
>>> or a ) in it. I created a fix and PR to fix the issue [1].
>>>
>>> If anyone has any good or better ideas on how to make this cleaner please let me know. We
>>> are toying with the idea of just using an EXE instead of batch scripts, but any input from
>>> someone with more Windows batch scripting experience than me is welcome.
>> Whatever you do, don't turn it into an EXE.  For better or worse, customers have always
>> relied on being able to hack the batch script.  I think you'd get a lot of pushback.
>>> [1]: https://github.com/wildfly/wildfly/pull/4520
>>> --
>>> James R. Perkins
>>> JBoss by Red Hat
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>



More information about the wildfly-dev mailing list