Don't use local config in unit tests.

+ Define a constant in phpunit.xml.
+ Only set __CA_LOCAL_CONFIG_DIRECTORY__ when not in a unit test.
Merge pull request #104 from leftclickben/PROV-916

PROV-916: Don't use local configuration in unit tests
PROV-799 keep specific attr settings in indexing
PROV-798 Allow <table>.<list element>.hierarchy.preferred_labels syntax in get(); enables display of hierarchy for list elements.
PROV-913: (Follow-up bugfix) Add missing returns.

Hook methods weren't returning anything, which was preventing other plugins
from executing.  Returning the passed-in parameters (or true) fixes this.
Merge pull request #105 from leftclickben/PROV-913-bugfix

PROV-913: (Follow-up bugfix) Add missing returns.
PROV-920 Fix for incorrect nesting; added --out switch to write output directly to a file
Merge branch 'develop' of github.com:collectiveaccess/providence into develop
PROV-902 remove old "relationship" attribute types
PROV-915 Properly support RDF mode for XML exports with namespaces.

Previously we’d always try to run each record through DOMDocument again
for “pretty printing” (indentation and such). That could cause problems
in RDF mode because you usually wouldn’t define all your used
namespaces in all your mappings for the whole graph. DOMDocument
complains about undefined namespaces though. So we simply skip that
step in RDF mode, which means our formatting might be a little off, but
at least the XML is correct and complete.
Merge branch 'master-fix' into develop
NOJIRA fix transaction safety in hierarchy builders
NOJIRA prevent sql error when hierpath goes long
NOJIRA type restrict on right table
PROV-919 Restore intrinsic indexing broken by
Merge branch 'develop' of git://github.com/collectiveaccess/providence into develop
PROV-922 Added support for relationship types

Previously it would be incredibly hard or even impossible to find out
the relationship type for items in sub-exports (what we call context
switches). We now support a couple of special keys in the source
columns. The names are along the lines of relationship display
templates:

* relationship_type_id
* relationship_type_code
* relationship_typename

Those work in deeply nested mappings as well and always refer to the
‘parent’ item in the export, if you will (the item where the context
was last switched). If the context is unchanged or these keys are
somehow not applicable, for instance if you traverse hierarchical
(type-less) relationships, mappings with these keys are ignored.
Merge branch 'master-fix' into develop
display helpers
refinery