security groups are not seed reader type data.

[hans_bakker]

Implemented as discussed with revision:

r1352431 | hansbak | 2012-06-21 14:21:49 +0700 (Thu, 21 Jun 2012) | 2 lines

split up securitypermissions as seed data and securitygroups as demo
data with a single exception: the creation of a super security group
which has general access to the system and which is used with the 'ant
create-admin-user-login' command.


Regards,
Hans

[Jacques Le Roux]

BTW, do we really need create-admin-user-login since it underneath uses load-admin-user-login?
If yes, then,  in order to prevent any confusions, we should document in create-admin-user-login description that it uses underneath
load-admin-user-login

Jacques

From: "Jacques Le Roux" <[hidden email]>

> From: "Jacopo Cappellato" <[hidden email]>
>> If it makes things clearer we could also rename
>>
>> create-admin-userlogin
>>
>> into
>>
>> create-super-userlogin
>>
>> But this is actually minor...
>
> At least, a good target description would be welcome...
>
> Jacques
>
>> Jacopo
>>
>>
>> On Jun 20, 2012, at 8:28 AM, Jacopo Cappellato wrote:
>>
>>>
>>> On Jun 20, 2012, at 7:59 AM, Hans Bakker wrote:
>>>
>>>> The create-admin-userlogin should be associated with the new 'SUPER" security group.
>>>
>>> Yes, this is exactly what I was thinking.
>>>
>>> Jacopo
>>>
>>