buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Reque (JIRA)" <>
Subject [jira] Commented: (BUILDR-280) integration task not calling compile task properly
Date Wed, 20 May 2009 02:09:45 GMT


Sean Reque commented on BUILDR-280:

I think I've actually narrowed down the magic number error to the eclipse scala plugin. If
I edit the file in vim I do not get the error. I only get it when I edit the file in eclipse.
However, if I delete the offending class file and run the integration test, buildr will not
rebuild the class file and I will instead get a plain runtime NoClassDefFoundError. I still
have to manually run compile to recompile the missing source file.

> integration task not calling compile task properly
> --------------------------------------------------
>                 Key: BUILDR-280
>                 URL:
>             Project: Buildr
>          Issue Type: Bug
>          Components: Dependency management
>    Affects Versions: 1.3.3
>         Environment: buildr 1.3.4 with matz ruby 1.8.7 and jdk 1.5.18 on x64 Ubuntu 9.10.
>            Reporter: Sean Reque
>             Fix For: 1.3.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.

View raw message