[
https://issues.apache.org/jira/browse/OAK-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-434:
------------------------------
Description:
We should change our build setup such that all tests of the upper layers
(oak-core, oak-jcr) can be run against either of the Microkernels. AFAIK
currently they are always run against the default Microkernel and not against
the MongoDB based Microkernel. Even though when the building with the mongomk
profile.
Also the integration testing profile should be changed such, that it runs all
against all Microkernel implementations. We need to figure out how we can do
that with the MongoDB based Microkernel since due to licensing issues I think
we can't just embed MongoDB.
was:We should change our build setup such that all tests of the upper layers
(oak-core, oak-jcr) can be run against either of the Microkernels. AFAIK
currently they are always run against the default Microkernel and not against
the MongoDB based Microkernel. Even though when the building with the mongomk
profile.
> Setup build profiles to run against either of the Microkernel implementations
> ------------------------------------------------------------------------------
>
> Key: OAK-434
> URL: https://issues.apache.org/jira/browse/OAK-434
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Reporter: Michael Dürig
>
> We should change our build setup such that all tests of the upper layers
> (oak-core, oak-jcr) can be run against either of the Microkernels. AFAIK
> currently they are always run against the default Microkernel and not against
> the MongoDB based Microkernel. Even though when the building with the mongomk
> profile.
> Also the integration testing profile should be changed such, that it runs all
> against all Microkernel implementations. We need to figure out how we can do
> that with the MongoDB based Microkernel since due to licensing issues I think
> we can't just embed MongoDB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
