[
https://issues.apache.org/jira/browse/BUILDR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lacton updated BUILDR-116:
--------------------------
Attachment: BUILDR-116.lib.patch
Here is another patch. It supersedes the previous one.
All existing specs and the two new ones are green with it.
I like it much more, because it removes some duplication and shows the intent
more clearly.
> TestTask should include the main compile target in its dependencies, even
> when using non standard directories
> -------------------------------------------------------------------------------------------------------------
>
> Key: BUILDR-116
> URL: https://issues.apache.org/jira/browse/BUILDR-116
> Project: Buildr
> Issue Type: Improvement
> Components: Test frameworks
> Environment: Trunk revision 680924
> Reporter: Lacton
> Priority: Minor
> Fix For: 1.3.3
>
> Attachments: BUILDR-116.lib.patch, BUILDR-116.spec.patch,
> BUILDR-116.spec.patch2
>
>
> TestTask should include the main compile target in its dependencies, even
> when using non standard directories (e.g., 'src/java' instead of
> 'src/main/java').
> For instance, I have a project with java sources in 'src/java' and its junit
> tests in 'src/test'. The buildfile is roughly like this:
> <code>
> define 'my-project' do
> compile _('src/java')
> test.compile _('src/test')
> end
> </code>
> 'buildr clean test' fails on test compilation because the main compile target
> (i.e., 'target/classes') is not in the TestTask's dependencies. The problem
> is that
> 1. the main CompileTask tries to set its target directory during the
> 'before_define' phase, which is too early because it is before the "compile
> _('src/java')" line.
> 2. the TestTask does not add the main compile target during the
> 'after_define' phase, because the main CompileTask still has no target at
> that time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
