You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/04/30 00:43:45 UTC
[jira] Closed: (MNG-2365) classes before test-classes in
MavenProject.getTestClasspathElements() - should be the other way around?
[ http://jira.codehaus.org/browse/MNG-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-2365.
---------------------------
Assignee: John Casey
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2.x)
2.2.0
applied the unit test, and all tests out just fine.
> classes before test-classes in MavenProject.getTestClasspathElements() - should be the other way around?
> --------------------------------------------------------------------------------------------------------
>
> Key: MNG-2365
> URL: http://jira.codehaus.org/browse/MNG-2365
> Project: Maven 2
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 2.0.4
> Environment: doesnt matter
> Reporter: kai lilleby
> Assignee: John Casey
> Fix For: 2.2.0
>
> Attachments: MNG-3118-test.patch
>
>
> in getTestClasspathElements() we have:
> List list = new ArrayList( getArtifacts().size() + 1 );
> list.add( getBuild().getOutputDirectory() );
> list.add( getBuild().getTestOutputDirectory() );
> - causing classes to be prior to test-classes in the classpath- something then prohibits test-resources/classes to shadow classes/ resources fom main. .I.e. it is not possible to redefine resources/classes for usage when running tests.
> Sugested solution:
> List list = new ArrayList( getArtifacts().size() + 1 );
> list.add( getBuild().getTestOutputDirectory() );
> list.add( getBuild().getOutputDirectory() );
> add test-classes before classes
--
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