Hi, thinking about our project layout, I realize that it is only possible to have one block generated by the build.xml per project, and there is only one melrin.properties that gets copied with its deployment directive hardcoded.
How do you manage multiple MerlinUnit TestCases where you want to test with different blocks, like test for wrong configurations, wrong deps etc? The blocks could be generated in other projects as the only artifact, but: - how do I reference them in the TestCase? I could include them as deps in the project of course but then only one block is generated again - I think it would be good to be able to override the merlin.deployment from within the testcase in order to be able to specify a block from there, but maybe it would be better to specify an artifact where the block should be taken from, like the block generating sub project outcomes? If nothing works, you can only have one Merlin integration test that uses magic-generated block definitions, which I think is not good. That would lead to hand-coded blocks like in the merlin-unit source which will not work once you start versioning. Just random thoughts. /peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
