You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacques Le Roux <ja...@les7arts.com> on 2011/01/24 12:32:14 UTC
Default enabled containers/features in trunk...
Hi,
As suggested by Bilgin I create a new thread for that. Should we keep the Beanshell and Groovysh containers ready to use?
I think we could comment them out. I know it will break the policy we use that provide OOTB a developer friendly version rather
than an user/production ready. But it will prevent any admin/user oversights, because it's an important security concern. If a dev
needs them, it's really easy to uncomment? What do you think?
BTW, BJ suggested to keep them directly accessible in trunk but to comment them out in releases. This makes sense but is not easy to
handle automatically...
Thanks
Jacques
Re: Default enabled containers/features in trunk...
Posted by Jacopo Cappellato <ja...@hotwaxmedia.com>.
I don't care much; if there is a general consensus to comment them out, it will be fine for me as well.
Jacopo
On Jan 24, 2011, at 12:32 PM, Jacques Le Roux wrote:
> Hi,
>
> As suggested by Bilgin I create a new thread for that. Should we keep the Beanshell and Groovysh containers ready to use?
>
> I think we could comment them out. I know it will break the policy we use that provide OOTB a developer friendly version rather than an user/production ready. But it will prevent any admin/user oversights, because it's an important security concern. If a dev needs them, it's really easy to uncomment? What do you think?
>
> BTW, BJ suggested to keep them directly accessible in trunk but to comment them out in releases. This makes sense but is not easy to handle automatically...
>
> Thanks
>
> Jacques
>
>
Re: Default enabled containers/features in trunk...
Posted by Jacques Le Roux <ja...@les7arts.com>.
Done at r1063235 (after a reverted mistake)
Jacques
Jacques Le Roux wrote:
> Thanks for the info Adrian, again a point to comment them out by default...
> I will do if nobody see an issue with that...
>
> Jacques
>
> From: "Adrian Crum" <ad...@sandglass-software.com>
>> It doesn't matter to me - I comment out the Beanshell container in my
>> production deployments. I noticed OFBiz starts up faster and uses a lot
>> less memory without it.
>>
>> -Adrian
>> On 1/24/2011 3:32 AM, Jacques Le Roux wrote:
>>> Hi,
>>>
>>> As suggested by Bilgin I create a new thread for that. Should we keep
>>> the Beanshell and Groovysh containers ready to use?
>>>
>>> I think we could comment them out. I know it will break the policy we
>>> use that provide OOTB a developer friendly version rather than an
>>> user/production ready. But it will prevent any admin/user oversights,
>>> because it's an important security concern. If a dev needs them, it's
>>> really easy to uncomment? What do you think?
>>>
>>> BTW, BJ suggested to keep them directly accessible in trunk but to
>>> comment them out in releases. This makes sense but is not easy to
>>> handle automatically...
>>>
>>> Thanks
>>>
>>> Jacques
Re: Default enabled containers/features in trunk...
Posted by Jacques Le Roux <ja...@les7arts.com>.
Thanks for the info Adrian, again a point to comment them out by default...
I will do if nobody see an issue with that...
Jacques
From: "Adrian Crum" <ad...@sandglass-software.com>
> It doesn't matter to me - I comment out the Beanshell container in my
> production deployments. I noticed OFBiz starts up faster and uses a lot
> less memory without it.
>
> -Adrian
> On 1/24/2011 3:32 AM, Jacques Le Roux wrote:
>> Hi,
>>
>> As suggested by Bilgin I create a new thread for that. Should we keep
>> the Beanshell and Groovysh containers ready to use?
>>
>> I think we could comment them out. I know it will break the policy we
>> use that provide OOTB a developer friendly version rather than an
>> user/production ready. But it will prevent any admin/user oversights,
>> because it's an important security concern. If a dev needs them, it's
>> really easy to uncomment? What do you think?
>>
>> BTW, BJ suggested to keep them directly accessible in trunk but to
>> comment them out in releases. This makes sense but is not easy to
>> handle automatically...
>>
>> Thanks
>>
>> Jacques
>>
>>
>
Re: Default enabled containers/features in trunk...
Posted by Adrian Crum <ad...@sandglass-software.com>.
It doesn't matter to me - I comment out the Beanshell container in my
production deployments. I noticed OFBiz starts up faster and uses a lot
less memory without it.
-Adrian
On 1/24/2011 3:32 AM, Jacques Le Roux wrote:
> Hi,
>
> As suggested by Bilgin I create a new thread for that. Should we keep
> the Beanshell and Groovysh containers ready to use?
>
> I think we could comment them out. I know it will break the policy we
> use that provide OOTB a developer friendly version rather than an
> user/production ready. But it will prevent any admin/user oversights,
> because it's an important security concern. If a dev needs them, it's
> really easy to uncomment? What do you think?
>
> BTW, BJ suggested to keep them directly accessible in trunk but to
> comment them out in releases. This makes sense but is not easy to
> handle automatically...
>
> Thanks
>
> Jacques
>
>