buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Toulme (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-280) integration task not calling compile task properly
Date Sun, 28 Feb 2010 18:50:06 GMT

    [ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839472#action_12839472
] 

Antoine Toulme commented on BUILDR-280:
---------------------------------------

Sean, are you still hitting the problem ? If yes, can you attach the changes you had made
?

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message