I wasn't around for the full history here but just a general comment. Elements like <testResources> would/do confuse me when I see them in project.xml
Seems you are tying something specific to the test plugin in the more abstract project entity. Perhaps clover can do it's own work by having a prereq on compile, copy what it needs to say, I dunno ./target/clover/junk and do stuff there. Then again I am outta the loop and perhaps don't know what I'm talking about ;-) -Peter ----- Original Message ----- From: "bob mcwhirter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, September 21, 2002 9:52 PM Subject: <testResources> ? > > Howdy kids-- > > There was discussion about having clover compilation happen to a > different directory. I said that's evil, because I have a <preGoal> > that does some copying to maven.test.dir, and having clover compile > elsewhere would break that. > > Then, someone floated the <testResources> idea in project.xml to > mirror <resources>. Then, the clover stuff could use it alongside > normal testing, and all would be well with a multi-directory layout. > > So, my question: > > Where do we stand on this? Any volunteers? > > -bob > > -- > Bob McWhirter [EMAIL PROTECTED] > The Werken Company http://werken.com/ > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
