You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by David E Jones <jo...@hotwaxmedia.com> on 2008/05/21 10:08:08 UTC
[VOTE] Move from Beanshell to Groovy
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
Re: [VOTE] Move from Beanshell to Groovy
Posted by Luke Grose <lu...@permeance.com.au>.
+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
>
>
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Rodrigo Lima <ac...@gmail.com>.
-1
2008/5/21, David E Jones <jo...@hotwaxmedia.com>:
>
>
> 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
>
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Christian Geisert <ch...@isu-gmbh.de>.
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
Re: [VOTE] Move from Beanshell to Groovy
Posted by Adrian Crum <ad...@hlmksw.com>.
+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
>
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Anil Patel <an...@hotwaxmedia.com>.
+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 <jonesde@hotwaxmedia.com
> >
> 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
>>
>>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Al Byers <by...@automationgroups.com>.
+1
-Al
On Wed, May 21, 2008 at 2:08 AM, David E Jones <jo...@hotwaxmedia.com>
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
>
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Jacopo Cappellato <ja...@gmail.com>.
+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
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Joe Eckard <jo...@redrocketcorp.com>.
+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
Re: [VOTE] Move from Beanshell to Groovy
Posted by Ashish Vijaywargiya <vi...@gmail.com>.
+1
On Thu, May 22, 2008 at 2:07 AM, Nicolas Malin <ni...@neogia.org>
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 : 06.17.66.40.06
> http://www.neogia.org/
>
--
Thanks & Regards
Ashish Vijaywargiya
+919893479711
Re: [VOTE] Move from Beanshell to Groovy
Posted by Nicolas Malin <ni...@neogia.org>.
+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 : 06.17.66.40.06
http://www.neogia.org/
Re: [VOTE] Move from Beanshell to Groovy
Posted by Jacques Le Roux <ja...@les7arts.com>.
+1
Jacques
From: "David E Jones" <jo...@hotwaxmedia.com>
>
> 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
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Andrew Zeneski <an...@hotwaxmedia.com>.
+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
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Ray Barlow <ra...@makeyour-point.com>.
+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
>
>
[VOTE RESULT] Move from Beanshell to Groovy
Posted by David E Jones <jo...@hotwaxmedia.com>.
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
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Scott Gray <le...@gmail.com>.
+1
Scott
2008/5/21 David E Jones <jo...@hotwaxmedia.com>:
>
> 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
>
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Tim Ruppert <ti...@hotwaxmedia.com>.
+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
>
Re: [VOTE] Move from Beanshell to Groovy
Posted by Ean Schuessler <ea...@brainfood.com>.
Am I eligible to vote? I guess so!
+1
----- "David E Jones" <jo...@hotwaxmedia.com> 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
ean@brainfood.com - http://www.brainfood.com - 214-720-0700 x 315