[ http://jira.codehaus.org/browse/MNG-591?page=comments#action_44292 ]
John Casey commented on MNG-591: -------------------------------- the problem with adding integration-test dependency scope and srcdir is that this is a slippery slope. Can we really define all of the types of tests that are out there, and if we do, do we really want <integrationTestSourceDirectory/> and <functionalTestSourceDirectory/> and ...? I think it's reasonable to expect that integration- or functional- or ... tests will need their own set of dependencies, and that it's unreasonable to expect that these can be satisfied using <scope>test</scope>. The source dir is easier, although we'd still have to provide a utility to help these plugins compile it. This got shot down once before, but I'll toss it out there again, just to see if it'll help generate some discussion/thinking: what about allowing dependencies to be tied to a particular lifecycle phase? While this would help by allowing <phase>integration-test</phase> in the dependency, it could conceivably muddy the waters of scope vs. bindings for dependencies. Calculating inheritedScope is easy on this...if it's not runtime || compile, it's not included transitively. I think it might not be such a great thing to ship maven 2.0 with the disclaimer "We can't handle all of your testing needs yet." However, I'm not sure what the way forward is. I'd really like to get started on this issue, though, since it looks like the highest-risk issue left for -beta-1. > Integration tests lifecycle > --------------------------- > > Key: MNG-591 > URL: http://jira.codehaus.org/browse/MNG-591 > Project: Maven 2 > Type: Improvement > Reporter: Kenney Westerhof > Assignee: John Casey > Priority: Blocker > Fix For: 2.0-beta-1 > > > I'm trying to do an integration test that depends on a war/ear to be deployed. > What i'm missing is: > - integration-test-compile stage and/or: > - a way to specify an integrationTestSourceDirectory or multiple > testSourceDirectories in the pom > I can't put the test sources in src/test/java because then surefire will run > them in the test stage, when > there's no artifact to deploy yet. > [Btw, I'm doing this while creating a cactus plugin, for the moment using > cargo in the TestSuite itself to deploy.] > The idea is that the integration test sources go in src/itest/*; that there > be a integration-test-compile, > integration-test-package and/or integration-test-appdeploy[or something] and > that surefire > is also bound to integration-test. > Maybe something can be done using the src/test/project/some-project/.... > approach seen in > maven-javadoc-plugin, maven-site-plugin and maven-eclipse-plugin (i'd like to > see some of that > standardized anyway to allow plugin testing generally - which can also be > seen as integration testing). > Thoughts, comments, approaches? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
