You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2011/06/22 12:12:47 UTC

[jira] [Closed] (BUILDR-280) integration task not calling compile task properly

     [ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald closed BUILDR-280.
-------------------------------


> integration task not calling compile task properly
> --------------------------------------------------
>
>                 Key: BUILDR-280
>                 URL: https://issues.apache.org/jira/browse/BUILDR-280
>             Project: Buildr
>          Issue Type: Bug
>          Components: Dependency management
>    Affects Versions: 1.3.4
>         Environment: buildr 1.3.4 with matz ruby 1.8.7 and jdk 1.5.18 on x64 Ubuntu 9.10.
>            Reporter: Sean Reque
>            Priority: Minor
>             Fix For: 1.4
>
>
> I've encountered several different errors managing my joint scala/java project with buildr, and I think it boils down to an issue of dependencies, specifically the integration task. For instance, if I modify a java source file and then run an integration test, I get an invalid magic number error. If I run the integration task from a clean checkout of my source code, I get compilation errors of the test classes. If I remove class files and then run the integration task, it does not recompile the classes but yields runtime errors related to the classes not being found. All of these errors go away when I manually run the compile task first.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira