And if anyone decides to do this and has questions about the current
scripts feel free to ask me. I've spent plenty of time attempting to fix
them :)
On 05/29/2013 07:29 AM, Brian Stansberry wrote:
We've planned for a while to create powershell variants for all
our
Windows scripts and to basically deprecate the old ones.[1] If someone
wants to take that on, please contact Tomaz Cerar. He's unavailable for
a couple weeks, so if you urgently want to take it on, let me know.
[1]
https://issues.jboss.org/browse/WFLY-676
On 5/27/13 6:59 AM, Spolti wrote:
> :),
>
> Is the best way use powershell?
> Or we can put a dependency in standalone/domain.bacth, or something like
> that?
>
>
> On 05/27/2013 08:52 AM, Nicklas Karlsson wrote:
>> Only pre-installed on Windows7/Server 2008+
>>
>>
>> On Mon, May 27, 2013 at 2:45 PM, Spolti <filippespolti(a)gmail.com
>> <mailto:filippespolti@gmail.com>> wrote:
>>
>> All windows versions have powershell instaled by default?
>>
>>
>> On 05/27/2013 07:26 AM, Tristan Tarrant wrote:
>> > 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(a)redhat.com
>> <mailto:ssilvert@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(a)lists.jboss.org
<mailto:wildfly-dev@lists.jboss.org>
>> >>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >>
>> >>
>> > _______________________________________________
>> > wildfly-dev mailing list
>> > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>> >
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> --
>> Regards,
>> ______________________________________
>> Filippe Costa Spolti
>> Linux User n°515639 -
http://counter.li.org/
>> filippespolti(a)gmail.com <mailto:filippespolti@gmail.com>
>> +55 34 9679-2388 <tel:%2B55%2034%209679-2388>
>> "Be yourself"
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>>
>>
>> --
>> Nicklas Karlsson, +358 40 5062266
>> Vaakunatie 10 as 7, 20780 Kaarina
> --
> Regards,
> ______________________________________
> Filippe Costa Spolti
> Linux User n°515639 -http://counter.li.org/
> filippespolti(a)gmail.com
> +55 34 9679-2388
> "Be yourself"
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
James R. Perkins
JBoss by Red Hat