You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Ittay Dror (JIRA)" <ji...@apache.org> on 2009/10/26 16:36:59 UTC

[jira] Updated: (BUILDR-333) buildr does not repackage when working with eclipse that compiles to target/classes

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

Ittay Dror updated BUILDR-333:
------------------------------

    Comment: was deleted

(was: another suggestion is that CompileTask#target should have all .class files as prerequisites )

> buildr does not repackage when working with eclipse that compiles to target/classes
> -----------------------------------------------------------------------------------
>
>                 Key: BUILDR-333
>                 URL: https://issues.apache.org/jira/browse/BUILDR-333
>             Project: Buildr
>          Issue Type: Bug
>          Components: Compilers
>            Reporter: Ittay Dror
>
> Many java developers set the project's output in Eclipse to target/classes to save compilation time of BuildR.
> Say I change a file:
> * jar task depends on compile.target
> * compile.target depends on compile task
> * compile task's needed? method checks Base#needed? 
> * Base#needed? compares sources, classes and dependencies timestamps
>   ==> since eclipse compiled the source, Base#needed? returns fals
>   ==> nothing is done (jar is not repackaged)
> Suggestion: Jar task should compare jar and classes timestamp. if there are newer classes, it is needed to be executed

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.