The file system errors seem to be because of a smaller limit on the length of file paths.

The following error is more confusing:

junit.framework.AssertionFailedError: Conversion from a Name value to a Boolean value should throw a ValueFormatException.
	at org.apache.jackrabbit.test.api.NamePropertyTest.testGetBoolean(NamePropertyTest.java:77)
	at org.apache.jackrabbit.test.AbstractJCRTest.run(AbstractJCRTest.java:456)

This code in NamePropertyTest.testGetBoolean() is as follows:

            Value val = PropertyUtil.getValue(prop);
            val.getBoolean();

and we only have one implementation of Value, called JcrValue. The getBooleanMethod() implementation delegates to the BooleanValueFactory in the graph module:

    public boolean getBoolean() throws ValueFormatException {
        try {
            boolean convertedValue = valueFactories.getBooleanFactory().create(value);
            return convertedValue;
        } catch (RuntimeException error) {
            throw createValueFormatException(boolean.class);
        }
    }

and the BooleanValueFactory.create(Object) method (since the type of 'value' is Object) does an instanceof check on the 'value' object. It should be a Name, but it must be something else. For example, if this is a String, then per the specification the conversion from a STRING type to a BOOLEAN type is to use the Boolean.valueOf(value) method, which of course returns true if the value is case-independently equal to "true", and false in all other cases.

The crazy thing is that the constructor for JcrValue will always convert the value object to the correct object type; i.e., in this case the NameFactory is used to create a Name object from the value. Thus the value should always be a Name.

I wonder if there is some difference with the IBM JDK in how switch statements behave.

Maybe a more likely explanation is that the Property object used by the test is not necessarily what we're expecting.

Link: Added: This issue related MODE-1023

I've logged MODE-1023 as being related to this issue, and hopefully the changes will fix the NamePropertyTest failure on the IBM JDK. (I have no way of testing this locally, and I'm not sure the project should be testing on many different JDKs.)

Link: Added: This issue related MODE-1024

I logged MODE-1024 to deal with the File System connector unit test failures.

ModeShape has committed a fix to the 2.2.x branch.  Also, you'll want to read the ModeShape related jira's to become better familiar with the changes.