[VOTE] Move from Beanshell to Groovy

[David E Jones]

This is a vote based on the recent discussion thread for changing the  
OFBiz best practice tool for writing data preparation scripts from  
using Beanshell to using Groovy, and more generally making Groovy the  
standard scripting language wherever generic scripting is needed, even  
as a way to implement services (as a secondary best practice to using  
simple-methods).

This sort of decision is perhaps not totally necessary to vote on, but  
does have a big impact on the project and many people involved, so a  
vote should help draw opinions and lead the community toward the best  
decision possible.

Please vote:

[+1] Yes, replace Beanshell with Groovy
[+0] I'm not for, but I'm not against
[-1] No, stick to Beanshell and don't migrate toward Groovy

Many comments were brought up in the discussion thread, but addition  
comments related to your vote are welcome. As per usual everyone is  
welcome to vote and express opinions though only PMC votes are binding.

-David

[Scott Gray]

+1

Scott

2008/5/21 David E Jones <[hidden email]>:

>
> This is a vote based on the recent discussion thread for changing the OFBiz
> best practice tool for writing data preparation scripts from using Beanshell
> to using Groovy, and more generally making Groovy the standard scripting
> language wherever generic scripting is needed, even as a way to implement
> services (as a secondary best practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but does
> have a big impact on the project and many people involved, so a vote should
> help draw opinions and lead the community toward the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
> comments related to your vote are welcome. As per usual everyone is welcome
> to vote and express opinions though only PMC votes are binding.
>
> -David
>
>

[Jacopo Cappellato-3]

+1

Jacopo

PS: I have also drafted out a migration script to rename files (.bsh -
 > .groovy).


On May 21, 2008, at 10:08 AM, David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing  
> the OFBiz best practice tool for writing data preparation scripts  
> from using Beanshell to using Groovy, and more generally making  
> Groovy the standard scripting language wherever generic scripting is  
> needed, even as a way to implement services (as a secondary best  
> practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on,  
> but does have a big impact on the project and many people involved,  
> so a vote should help draw opinions and lead the community toward  
> the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are  
> binding.
>
> -David
>

[Luke Grose]

+1

David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing the
> OFBiz best practice tool for writing data preparation scripts from using
> Beanshell to using Groovy, and more generally making Groovy the standard
> scripting language wherever generic scripting is needed, even as a way
> to implement services (as a secondary best practice to using
> simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but
> does have a big impact on the project and many people involved, so a
> vote should help draw opinions and lead the community toward the best
> decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
> comments related to your vote are welcome. As per usual everyone is
> welcome to vote and express opinions though only PMC votes are binding.
>
> -David
>
>
>

[Jacques Le Roux]

+1

Jacques

From: "David E Jones" <[hidden email]>

>
> This is a vote based on the recent discussion thread for changing the  
> OFBiz best practice tool for writing data preparation scripts from  
> using Beanshell to using Groovy, and more generally making Groovy the  
> standard scripting language wherever generic scripting is needed, even  
> as a way to implement services (as a secondary best practice to using  
> simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but  
> does have a big impact on the project and many people involved, so a  
> vote should help draw opinions and lead the community toward the best  
> decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are binding.
>
> -David
>

[Christian Geisert]

David E Jones schrieb:
>
> This is a vote based on the recent discussion thread for changing the
> OFBiz best practice tool for writing data preparation scripts from using
> Beanshell to using Groovy, and more generally making Groovy the standard
> scripting language wherever generic scripting is needed, even as a way
> to implement services (as a secondary best practice to using
> simple-methods).

+1

Christian

[byersa]

+1
-Al

On Wed, May 21, 2008 at 2:08 AM, David E Jones <[hidden email]>
wrote:

>
> This is a vote based on the recent discussion thread for changing the OFBiz
> best practice tool for writing data preparation scripts from using Beanshell
> to using Groovy, and more generally making Groovy the standard scripting
> language wherever generic scripting is needed, even as a way to implement
> services (as a secondary best practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but does
> have a big impact on the project and many people involved, so a vote should
> help draw opinions and lead the community toward the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
> comments related to your vote are welcome. As per usual everyone is welcome
> to vote and express opinions though only PMC votes are binding.
>
> -David
>
>

[Anil Patel-3]

+1

On May 21, 2008, at 7:09 AM, Al Byers wrote:

> +1
> -Al
>
> On Wed, May 21, 2008 at 2:08 AM, David E Jones <[hidden email]
> >
> wrote:
>
>>
>> This is a vote based on the recent discussion thread for changing  
>> the OFBiz
>> best practice tool for writing data preparation scripts from using  
>> Beanshell
>> to using Groovy, and more generally making Groovy the standard  
>> scripting
>> language wherever generic scripting is needed, even as a way to  
>> implement
>> services (as a secondary best practice to using simple-methods).
>>
>> This sort of decision is perhaps not totally necessary to vote on,  
>> but does
>> have a big impact on the project and many people involved, so a  
>> vote should
>> help draw opinions and lead the community toward the best decision  
>> possible.
>>
>> Please vote:
>>
>> [+1] Yes, replace Beanshell with Groovy
>> [+0] I'm not for, but I'm not against
>> [-1] No, stick to Beanshell and don't migrate toward Groovy
>>
>> Many comments were brought up in the discussion thread, but addition
>> comments related to your vote are welcome. As per usual everyone is  
>> welcome
>> to vote and express opinions though only PMC votes are binding.
>>
>> -David
>>
>>

[Rodrigo Lima-2]

-1

2008/5/21, David E Jones <[hidden email]>:

>
>
> This is a vote based on the recent discussion thread for changing the OFBiz
> best practice tool for writing data preparation scripts from using Beanshell
> to using Groovy, and more generally making Groovy the standard scripting
> language wherever generic scripting is needed, even as a way to implement
> services (as a secondary best practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but does
> have a big impact on the project and many people involved, so a vote should
> help draw opinions and lead the community toward the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
> comments related to your vote are welcome. As per usual everyone is welcome
> to vote and express opinions though only PMC votes are binding.
>
> -David
>
>

[Adrian Crum]

+1

David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing the
> OFBiz best practice tool for writing data preparation scripts from using
> Beanshell to using Groovy, and more generally making Groovy the standard
> scripting language wherever generic scripting is needed, even as a way
> to implement services (as a secondary best practice to using
> simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but
> does have a big impact on the project and many people involved, so a
> vote should help draw opinions and lead the community toward the best
> decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
> comments related to your vote are welcome. As per usual everyone is
> welcome to vote and express opinions though only PMC votes are binding.
>
> -David
>
>

[Joe Eckard]

+1

On May 21, 2008, at 4:08 AM, David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing  
> the OFBiz best practice tool for writing data preparation scripts  
> from using Beanshell to using Groovy, and more generally making  
> Groovy the standard scripting language wherever generic scripting is  
> needed, even as a way to implement services (as a secondary best  
> practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on,  
> but does have a big impact on the project and many people involved,  
> so a vote should help draw opinions and lead the community toward  
> the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are  
> binding.
>
> -David

[Ean Schuessler]

Am I eligible to vote? I guess so!

+1

----- "David E Jones" <[hidden email]> wrote:

> This is a vote based on the recent discussion thread for changing the
>
> OFBiz best practice tool for writing data preparation scripts from  
> using Beanshell to using Groovy, and more generally making Groovy the
>
> standard scripting language wherever generic scripting is needed, even
>  
> as a way to implement services (as a secondary best practice to using
>
> simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but
>  
> does have a big impact on the project and many people involved, so a
>
> vote should help draw opinions and lead the community toward the best
>
> decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
>
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are
> binding.

--
Ean Schuessler, CTO Brainfood.com
[hidden email] - http://www.brainfood.com - 214-720-0700 x 315

[Tim Ruppert]

+1

On May 21, 2008, at 2:08 AM, David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing  
> the OFBiz best practice tool for writing data preparation scripts  
> from using Beanshell to using Groovy, and more generally making  
> Groovy the standard scripting language wherever generic scripting is  
> needed, even as a way to implement services (as a secondary best  
> practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on,  
> but does have a big impact on the project and many people involved,  
> so a vote should help draw opinions and lead the community toward  
> the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are  
> binding.
>
> -David
>

[Ray Barlow]

+1

David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing the
> OFBiz best practice tool for writing data preparation scripts from
> using Beanshell to using Groovy, and more generally making Groovy the
> standard scripting language wherever generic scripting is needed, even
> as a way to implement services (as a secondary best practice to using
> simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on, but
> does have a big impact on the project and many people involved, so a
> vote should help draw opinions and lead the community toward the best
> decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition
> comments related to your vote are welcome. As per usual everyone is
> welcome to vote and express opinions though only PMC votes are binding.
>
> -David
>
>

[Andrew Zeneski-2]

+1

On May 21, 2008, at 1:08 AM, David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing  
> the OFBiz best practice tool for writing data preparation scripts  
> from using Beanshell to using Groovy, and more generally making  
> Groovy the standard scripting language wherever generic scripting is  
> needed, even as a way to implement services (as a secondary best  
> practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on,  
> but does have a big impact on the project and many people involved,  
> so a vote should help draw opinions and lead the community toward  
> the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are  
> binding.
>
> -David
>

[Nicolas Malin]

+1

On May 21, 2008, at 1:08 AM, David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing  
> the OFBiz best practice tool for writing data preparation scripts  
> from using Beanshell to using Groovy, and more generally making  
> Groovy the standard scripting language wherever generic scripting is  
> needed, even as a way to implement services (as a secondary best  
> practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on,  
> but does have a big impact on the project and many people involved,  
> so a vote should help draw opinions and lead the community toward  
> the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are  
> binding.
>
> -David
>

--
MALIN Nicolas
Trésorier de l'association Néogia
Tél : [phone]
http://www.neogia.org/

[Ashish Vijaywargiya]

+1

On Thu, May 22, 2008 at 2:07 AM, Nicolas Malin <[hidden email]>
wrote:

> +1
>
> On May 21, 2008, at 1:08 AM, David E Jones wrote:
>
>
>> This is a vote based on the recent discussion thread for changing  the
>> OFBiz best practice tool for writing data preparation scripts  from using
>> Beanshell to using Groovy, and more generally making  Groovy the standard
>> scripting language wherever generic scripting is  needed, even as a way to
>> implement services (as a secondary best  practice to using simple-methods).
>>
>> This sort of decision is perhaps not totally necessary to vote on,  but
>> does have a big impact on the project and many people involved,  so a vote
>> should help draw opinions and lead the community toward  the best decision
>> possible.
>>
>> Please vote:
>>
>> [+1] Yes, replace Beanshell with Groovy
>> [+0] I'm not for, but I'm not against
>> [-1] No, stick to Beanshell and don't migrate toward Groovy
>>
>> Many comments were brought up in the discussion thread, but addition
>>  comments related to your vote are welcome. As per usual everyone is
>>  welcome to vote and express opinions though only PMC votes are  binding.
>>
>> -David
>>
>>
>
> --
> MALIN Nicolas
> Trésorier de l'association Néogia
> Tél : [phone]
> http://www.neogia.org/
>

--
Thanks & Regards
Ashish Vijaywargiya
[phone]

+1

> +1
>
> On Thu, May 22, 2008 at 2:07 AM, Nicolas Malin <[hidden email]>
> wrote:
>
> > +1
> >
> > On May 21, 2008, at 1:08 AM, David E Jones wrote:
> >
> >
> >> This is a vote based on the recent discussion thread for changing  the
> >> OFBiz best practice tool for writing data preparation scripts  from using
> >> Beanshell to using Groovy, and more generally making  Groovy the standard
> >> scripting language wherever generic scripting is  needed, even as a way to
> >> implement services (as a secondary best  practice to using simple-methods).
> >>
> >> This sort of decision is perhaps not totally necessary to vote on,  but
> >> does have a big impact on the project and many people involved,  so a vote
> >> should help draw opinions and lead the community toward  the best decision
> >> possible.
> >>
> >> Please vote:
> >>
> >> [+1] Yes, replace Beanshell with Groovy
> >> [+0] I'm not for, but I'm not against
> >> [-1] No, stick to Beanshell and don't migrate toward Groovy
> >>
> >> Many comments were brought up in the discussion thread, but addition
> >>  comments related to your vote are welcome. As per usual everyone is
> >>  welcome to vote and express opinions though only PMC votes are  binding.
> >>
> >> -David
> >>
> >>
> >
> > --
> > MALIN Nicolas
> > Trésorier de l'association Néogia
> > Tél : [phone]
> > http://www.neogia.org/
> >
>
>
>
> --
> Thanks & Regards
> Ashish Vijaywargiya
> [phone]
>

[David E Jones]

The vote has passed with the following results:

+1 binding: 8
+1 general: 9
-1 general: 1

It looks like there is already a Jira issue to get some conversions  
going... so onward and upward!

I'll start working on the best practices guide and change it according  
to this.

-David


On May 21, 2008, at 2:08 AM, David E Jones wrote:

>
> This is a vote based on the recent discussion thread for changing  
> the OFBiz best practice tool for writing data preparation scripts  
> from using Beanshell to using Groovy, and more generally making  
> Groovy the standard scripting language wherever generic scripting is  
> needed, even as a way to implement services (as a secondary best  
> practice to using simple-methods).
>
> This sort of decision is perhaps not totally necessary to vote on,  
> but does have a big impact on the project and many people involved,  
> so a vote should help draw opinions and lead the community toward  
> the best decision possible.
>
> Please vote:
>
> [+1] Yes, replace Beanshell with Groovy
> [+0] I'm not for, but I'm not against
> [-1] No, stick to Beanshell and don't migrate toward Groovy
>
> Many comments were brought up in the discussion thread, but addition  
> comments related to your vote are welcome. As per usual everyone is  
> welcome to vote and express opinions though only PMC votes are  
> binding.
>
> -David
>