You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Sean Reque (JIRA)" <ji...@apache.org> on 2009/05/18 17:29:36 UTC
[jira] Created: (BUILDR-280) integration task not calling compile
task properly
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.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.
[jira] Commented: (BUILDR-280) integration task not calling compile
task properly
Posted by "Sean Reque (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712452#action_12712452 ]
Sean Reque commented on BUILDR-280:
-----------------------------------
Actually it looks like buildr still runs integration setup before compiling test classes, which I find annoying, especially if the compile fails, but this may be considered a feature for some.
> 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.3.5
>
>
> 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.
[jira] Resolved: (BUILDR-280) integration task not calling compile
task properly
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-280.
-----------------------------------
Resolution: Incomplete
Marking as incomplete. Please attach the changes you had made and give us a spec so that we can reproduce the problem.
> 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.
[jira] Commented: (BUILDR-280) integration task not calling compile
task properly
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (BUILDR-280) integration task not calling compile
task properly
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-280:
---------------------------------
Fix Version/s: (was: 1.3.5)
1.4
> 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.
[jira] Updated: (BUILDR-280) integration task not calling compile
task properly
Posted by "lacton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lacton updated BUILDR-280:
--------------------------
Fix Version/s: (was: 1.3.4)
1.3.5
> 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.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.5
>
>
> 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.
[jira] Updated: (BUILDR-280) integration task not calling compile
task properly
Posted by "Sean Reque (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Reque updated BUILDR-280:
------------------------------
Priority: Minor (was: Major)
Affects Version/s: (was: 1.3.3)
1.3.4
I was able to resolve most of my dependency problems by using the Rake::Task#enhance method rather than using the global task method to define dependencies. I thought that under the hood those did the same thing, but I guess I was wrong. This has fixed the following issues for me
1. package task not calling the compile task.
2. integration task not calling the compile task
3. integration task performing setup before compiling test classes.
I thought I remember afterwards still seeing a problem where the package task would not recreate a war file even if one of its dependency source files was update, but I cannot reproduce it right now. This ticket can probably be closed if what I was doing previously is actually the incorrect way to add dependencies to tasks defined by buildr.
> 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.3.5
>
>
> 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.
[jira] Commented: (BUILDR-280) integration task not calling compile
task properly
Posted by "Sean Reque (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710973#action_12710973 ]
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: https://issues.apache.org/jira/browse/BUILDR-280
> 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.