[jbpm-dev] Re: excluding ejb-scheduler-test from tests against non-xa datasources
Hi Alejandro,
Our QA environment is a three dimensional matrix: jdk,container,database
Ideally, we would be able to exclude a test based on these three
parameters. This however is currently not supported, instead we can only
exclude tests based on database.
In your specific case, would it not be sufficient to exclude the
EjbSchedulerTest for postgresql?
What should be clear however is, that if a certain test/functionality is
excluded we document that jBPM does not support that functionality in
the environment it is excluded in.
cheers
-thomas
Alejandro Guizar wrote:
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
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
BPM Product Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx