> * regarding the projection: there isn't a predefined projections for the git connector because the test creates the projection and asserts the branches & tags contents of the repository, in similar fashion to the standalone test

Okay. I guess I just missed where the projection was being created.

> * regarding the directory paths: we can't use a test variable, because that isn't relevant: the test is run in a prepackaged war file, outside the repository. The repository runtime class path is effective that of the AS7 container. I agree it's not ideal, but I don't know any other way (any other server-side path we can use) in which to validate the connectors in the case of AS7. My thinking was that it's worth this format as it validates (through our unit tests) that the connectors work. Thoughts ?

I don't understand why we can't use a variable (like `${jboss.server.data.dir}`) within the `standalone-modeshape.xml` file, and then define the variable in the [`arquillian.xml` file](https://github.com/ModeShape/modeshape/blob/0aa84bb597972b1e5e3df4e274001a01a4f7bfa8/integration/modeshape-jbossas-integration-tests/src/test/resources/arquillian.xml#L14) in the same place we're defining other system properties.

The GitConnector.initialize method will already throw an exception if the specified directory does not correspond to a folder with a `.git` directory. And when the connectors are initialized, any connector that throws an exception will be removed from the list of instantiated connectors. So should anyone reuse the `standalone-modeshape.xml` file as-is, the "git" source simply will not be available.

But by using a variable, it cleans up the `standalone-modeshape.xml` file to remove the information that's obviously specific to our source code structure (and where the integration tests are run from). Yes, the repositories are very notional (even specific to our tests), but the `${jboss.server.data.dir}/../../../../../../` just seems to be really bogus.

Perhaps we should clean this up even more, in a different JIRA. For example, the `arquillian.xml` file already contains:

    <property name="serverConfig">standalone-modeshape.xml</property>

which we could change to:

    <property name="serverConfig">standalone-modeshape-tests.xml</property>

Then we could move many of the extra repository definitions to `standalone-modeshape-tests.xml`, include that file in the kit, and change `standalone-modeshape.xml` to have only a few more notional and usable-out-of-the-box repositories. The downside of doing this is that we wouldn't be directly testing the `standalone-modeshape.xml` configuration file without some additional tests (I'm not sure how we could easily do this).