Global exclude resolved the issue, thanks.
Btw, it seems that all initialization tests are only needed for api
tests. Now when api tests were extracted to separate project (JCR Tests)
and are not executed as part of the build, it could be simplified I think.
Additionally all initialization tests should be probably also moved to
JCR tests project. However I'll be more confident if JCR tests will be
run as part of jackrabbit install goal (executed in integration-test phase).
Przemo
Hi,
On 12/8/06, Jan Kuźniak <[EMAIL PROTECTED]> wrote:
Jukka Zitting wrote:
> Oh, bugger, you're right. It all boils down to the need to start the
> test suite with the test initialization code. Perhaps we could
> simplify that somehow...
There is an option to write Maven plugin that will execute
initialisation code.
I can try to do that, however the approach with two test executions
seemed
simpler for me.
Agreed, the current approach is much better than using a custom plugin.
I think I've now (as of revision 485595) solved the issue by using a
global exclude instead of <skip>true</skip> in the surefire
configuration.
BR,
Jukka Zitting
