Serge Knystautas wrote:
I think that will be messy since there has been so much changes on each, but I don't have a better suggestion. grunt grunt grunt.
This really could expose our Archiles heel though, which is a lack of adequate testing to make sure the merged version works well. Have we made any progress/thoughts on how to automate testing?
1. Migrate to Maven (which I can help with) 2. Do an api/impl split (which will make me happy) 3. Use the AbstractMerlinTestCase to deploy james in a container with services accessible to your unit test - you unit test would only neew two dependecy declarations - mailet API and the merlin test case. You can structure the deployment scenario to expose whatever services are needed for the test (e.g. Mailet, or RemoteAdmin or or whatever). Behind the scenes its no different to running up James as an NT service - same system - just a different embedding scenario.
Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
