On Jun 5, 2009, at 11:03 AM, Adam Heath wrote:
Adrian Crum wrote:
Sharing some more thoughts on this...
I tried doing a test run of installing seed-initial and seed data
only.
I couldn't get logged in because the admin user login is in demo
data -
not seed. I moved it to seed-initial - since the account should
only be
created/updated during the initial install (from my perspective
anyway).
I still couldn't log in because all of the components put their admin
permissions in the FULLADMIN security group, and I had left the
security
group assignments in demo data. So, that security group would have
to be
part of seed data too.
No.
There's an ant target you are supposed to call that created the admin
user login.
Yes, this is a good point.
Don't confuse the term "seed" with the system being all configured and
ready to run, or implying that any part of it should be expected to
run as desired (including login).
The definitions in the entityengine.xml file where these are defined
might be helpful:
seed = OFBiz and External Seed Data - to be maintained along
with source and updated whenever a system deployment is updated
seed-initial = OFBiz and External Seed Data - to be maintained along
with source like other seed data, but only loaded initially and not
updated when a system is updated except manually reviewing each line
demo = OFBiz Only Demo Data
ext = External General Data (custom)
ext-test = External Test Data (custom)
ext-demo = External Demo Data (custom)
The admin user is, IMO (and based on discussions a bit ago), is part
of demo data and not seed or seed-initial.
Based on that, Adrian do you still think there is a big issue with
data that is in seed versus demo data files? I'm guessing there are
still some small issues with that, but hopefully it's not as big a
deal as you thought before...
-David
