On Mon, 2003-12-08 at 23:05, Brett Porter wrote: > It works just fine. It does not work just fine.
> Set sourceDirecotry = unitTestSourceDirectory, and > appropriate excludes to the tests and jar plugins so they don't get used > inappropriately. Until you have to actually do something useful like run clover. http://www.apache.org/~jvanzyl/maven-model-clusterfuck.tgz Chad, here's a live example for you to look at. See how well your tests run and how well your coverage reports come out. This is just one plugin that I tried, one that is most important to me. Tests fail all over the place and the coverage is reported as zero when in fact the coverage is 99.5% But this was just using the suggestion. I'm sure I could find ways around it but I'm not going to I don't suggest you do either. Setting those directories the same is an absolutely horrible suggestion and you're just going shoot yourself in the face if you do because you immediately buy yourself non-determistic behaviour from all the plugins. Tell your team members that for the very small input of having to separate the tests you gain many advantages due to a very simple separation. Would it really take you that long to place your tests in another directory? Are you that unwilling to unchange for what you get. Separating your sources means you get all Maven's reports without having to hack plugins in cases where having test/app sources in the same directory just doesn't work. I am harsh, but honest $DIETY I am only trying to make your life easier. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
