I think the likely difference is that ant is running each test in its own JVM, and Maven is not.
Now, it is straightforward enough to add functionality that resets the ManifoldCF core classes, and tie that into the tests. However, that is not how ManifoldCF will be used in practice. The concern I have is that there are other static variables (for instance, the cache manager) which are never "reset", but would be if we need to "start from scratch" again inside the same JVM every time a test is run. Identifying all such cases may take some time. Karl On Mon, Jul 18, 2011 at 8:04 AM, Karl Wright <[email protected]> wrote: > These tests run fine under ant, but the ant build invokes test files > explicitly. I'm not quite sure what Ant's behavior is here, and how > exactly it differs from Maven's. > > Karl > > On Mon, Jul 18, 2011 at 7:41 AM, Tobias Rübner <[email protected]> wrote: >> The unit tests are currently not working. >> The first test in a module creates the properties and logging files and >> initializes the framework. >> All following tests are also creating those files, but because the framework >> is already initialized, they are useless. >> >> This depends on the static behaviour of ManifoldCF.isInitialized. >> After a test is done the ManifoldCF Object should also be reseted. >> >
