Jason and I had discussed this briefly a while ago... In my opinion, the best/clearest way to handle this is to branch the integration tests.
-Dan > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Sunday, October 29, 2006 4:24 PM > To: Maven Developers List > Subject: integration tests: how to handle versions? > > Hi, > > I like the new integration testing method. However, I've just added a > test that will only work with a version of Maven that fixes the bug > (which I have sorted out locally, just doing some other checks before > committing). > > So the two things we need to do: > - exclude that test from Maven < 2.0.5 > - display what Maven version is being used before starting, because I > keep accidentally using the wrong version. > > Maybe the <prerequisite /> tag in the pom.xml for the test (and > handle the error case from Maven), or just have a condition in the > test that if mavenVersion < 2.0.5(which would need to be obtained in > the verifier, perhaps by scraping mvn -version), output SKIPPED. > > Any thoughts on the best way to do this? > > - Brett _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
