[
http://jira.codehaus.org/browse/MEXEC-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109038
]
Yan Huang commented on MEXEC-26:
--------------------------------
Any idea as to when this issue can be fixed? It's pain of neck to add all
dependencies of test phase within "plugin" tag in order to work around this
problem.
> Wrong classpath for the phases Test and Integration-Test
> --------------------------------------------------------
>
> Key: MEXEC-26
> URL: http://jira.codehaus.org/browse/MEXEC-26
> Project: Maven 2.x Exec Plugin
> Issue Type: Bug
> Affects Versions: 1.0, 1.0.1, 1.0.2, 1.1
> Environment: all
> Reporter: Matthias Pfau
>
> The Method {{ExecMojo.computeClasspath}} does not recognize which phase it is
> in. This means that you won't have any test-classes on your classpath if you
> use the plugin in a test or integration-test phases.
> The classpath for the test and integration-test phases should include
> {{/target/classes}} and {{/target/test-classes}} In my opinion
> {code}
> // FIXME check project current phase?
> // we should probably add the output and testoutput dirs based on the
> Project's phase
> if ( true )
> {
> if ( theClasspath.length() > 0 )
> {
> theClasspath.append( File.pathSeparator );
> }
> theClasspath.append( project.getBuild().getOutputDirectory() );
> }
> if ( false )
> {
> if ( theClasspath.length() > 0 )
> {
> theClasspath.append( File.pathSeparator );
> }
> theClasspath.append( project.getBuild().getTestOutputDirectory()
> );
> }
> {code}
--
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 from this list please visit:
http://xircles.codehaus.org/manage_email
