Thomas, I've been trying several ways to prevent EjbSchedulerTest from being run against databases that do not have XA support. In my current approach I have a property named datasource.xa that is set in the corresponding database profiles in the base POM file. For instance, the postgresql profile is: <profile> <id>postgresql</id> <activation> <property> <name>database</name> <value>postgresql</value> </property> </activation> <properties> <datasource.xa /> </properties> </profile> In modules/enterprise/jar/pom.xml, I have defined two separate profiles with different exclude sets, based on the presence of the datasource.xa property, as follows. <profile> <id>no-xa-datasource</id> <activation> <property> <name>!datasource.xa</name> </property> </activation> </profile> <profile> <id>xa-datasource</id> <activation> <property> <name>datasource.xa</name> </property> </activation> </profile> However, the no-xa-datasource always gets activated, unless I pass -Ddatasource.xa on the command line. Isn't a property defined in a profile visible to other profiles? I'd appreciate your help here. -Alejandro