[
https://issues.apache.org/jira/browse/BUILDR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Assaf Arkin resolved BUILDR-88.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.3.2
Changed for both compiled classes and resources.
> Test classes/resources should come before compile classes/resources so they
> load up earlier in java classpath
> -------------------------------------------------------------------------------------------------------------
>
> Key: BUILDR-88
> URL: https://issues.apache.org/jira/browse/BUILDR-88
> Project: Buildr
> Issue Type: Improvement
> Components: Core features
> Affects Versions: 1.3.1
> Reporter: Lacton
> Fix For: 1.3.2
>
>
> When running tests, test classes and test resources should come before
> compile classes and compiles resources in the java classpath, so that classes
> and resources for test can override classes and resources for 'real' use.
> This behaviour would be consistent with Maven.
> Example:
> myproject/
> --- src/
> ------ main/
> --------- java/
> --------- resources/
> ------------ myProperties.properties # This one is for the real world
> ------ test/
> --------- java/
> --------- resources/
> ------------ myProperties.properties # This one is for testing and should
> override the other one
> Buildr 1.3.1.1 uses the following classpath to run tests.
> ...dependencies...:myproject/target/classes:myproject/target/resources:myproject/target/test/classes:myproject/target/test/resources:...jars
> for testing...
> 'myproject/target/test/classes' and 'myproject/target/test/resources' should
> come before 'myproject/target/classes' and 'myproject/target/resources'.
> This issue can be solved by adding 'test.with test.resources.target' in the
> project definition. Yet, I think it should be the default behaviour.
> Regards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
