[
http://jira.codehaus.org/browse/MEXEC-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lacoste updated MEXEC-26:
--------------------------------
Description:
Problem: Wrong classpath for the phases Test and Integration-Test
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}
was:
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}
Issue Type: New Feature (was: Bug)
Summary: Allow to specify classpath scope for the exec mojo (was:
Wrong classpath for the phases Test and Integration-Test)
> Allow to specify classpath scope for the exec mojo
> ---------------------------------------------------
>
> Key: MEXEC-26
> URL: http://jira.codehaus.org/browse/MEXEC-26
> Project: Maven 2.x Exec Plugin
> Issue Type: New Feature
> Components: exec
> Affects Versions: 1.0, 1.0.1, 1.0.2, 1.1-beta-1
> Environment: all
> Reporter: Matthias Pfau
> Assignee: Jerome Lacoste
> Fix For: 1.1
>
> Attachments: MEXEC-26.diff
>
>
> Problem: Wrong classpath for the phases Test and Integration-Test
> 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
