[ http://jira.codehaus.org/browse/MNG-591?page=comments#action_43635 ]
Kenney Westerhof commented on MNG-591:
--------------------------------------
:) That really wasn't necessary! I should have filed it.
As long as we're being complete, I'll add another reason this is nice to have
and some more food for thought:
The xdoclet plugin currently has to have dependencies on all plugins for
xdoclet itself (container / environment specific),
because there's no way to add those to the plugin execution environment, except
now using <extensions> which contaminates
the root classloader. So basically by allowing this you can have plugins for
the plugins.
However, what we need to consider is the need to add some libraries to higher
level than the plugin classloader, for instance to
a lifecycle phase. Currently artifacts with scope=provided aren't being
resolved in the test scope:
(ScopeArtifactFilter.java:
else if ( DefaultArtifact.SCOPE_TEST.equals( scope ) )
{
providedScope = false;
compileScope = true;
runtimeScope = true;
testScope = true;
}
)
This poses a problem for the eclipse plugin. Enabling this will fix that, but
they stil aren't included in the plugin
classpath - the plugin will need to create it's own classloader for that.
However, sometimes just an -api artifact is
depended upon, and during tests an -impl version should be provided - ideally
this artifact is present in the classpath during all mojo
executions in a particular phase. (This may be a bad example since there' s
only one test plugin - does anybody have more examples?)
> Integration tests lifecycle
> ---------------------------
>
> Key: MNG-591
> URL: http://jira.codehaus.org/browse/MNG-591
> Project: Maven 2
> Type: Improvement
> Reporter: Kenney Westerhof
> 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]
