...
I highly recommend setting up an entities directory for your team once you've had a successful export. This makes it easy for anyone working on your portal is completely optional, but it's easy to setup and allows developers on your team to populate their development database databases with the groups, channels, permissions, fragment-layouts, etc that your production portal uses. After you've completed your export copy your export folder under: uportal-impl/src/main/resources/properties/db
...
The contents should look something like this (note that I've omitted the contents of the larger directories):
| Panel |
|---|
channel: channel-type: entity-type: fragment-layout: fragment-users: group_membership: layout: permission: structure: theme: user: |
Modify build.xml
Now in your build.xml you should add a import task for your entities and change initdb to not call the default entities.
| Code Block |
|---|
<target name="db-import-calpoly" description="Imports the CalPoly groups, channels, memberships, permissions from a snapshot of prod Nov 2008">
<echo message="Importing CalPoly groups, channels, memberships, permissions data" />
<antcall target="crn-import">
<param name="dir" value="${basedir}/uportal-impl/src/main/resources/properties/db/calpoly_entities" />
</antcall>
</target>
|
In initdb remove the call to db-import. I also printed a message here:
| Code Block |
|---|
<echo message="You now need to run db-import-default, or db-import-calpoly to populate a working database." />
|
Note that I renamed db-import to db-import-default in my build.xml