Today I upgraded utplsql 3.0.3 to 3.0.4. The first run with Jenkins is not reporting any output.

Situation:

1. Jenkins resets a database schema with the code to test
2. Jenkins deploys utPlSql in this database schema
3. Jenkins deploys the unit tests in this schema, divided into two test suites
4. Each test suite is run by a separate call utPLSQL-sql-cli with the following options: @{connectstring} -p=@{schema}:@{packagesuite} -f=ut_documentation_reporter -s -f=ut_xunit_reporter -o=@{outputfile}

The first test suite that is executed results in a empty output file. Also no screen output is displayed. The second test suite is reporting results. Manually executing utPLSQL-sql-cli after this Jenkins job results in a non-empty output file.

Could this be an issue with the new caching mechanism? Or should I reset something? In version 3.0.3 the process described above worked fine.