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:28:59 UTC

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

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.


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

Posted by "Ittay Dror (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770058#action_12770058 ] 

Ittay Dror commented on BUILDR-333:
-----------------------------------

Another suggestion is for ArchiveTask#needed? to be enhanced so it goes into folders to check if packaging is required

> 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.


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

Posted by "Ittay Dror (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770067#action_12770067 ] 

Ittay Dror commented on BUILDR-333:
-----------------------------------

note that it looks like ArchiveTask#needed? is wrong anyway, since it will not recreate the archive if a file inside an included directory changes (since only the directory's timestamp will be checked)

> 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.


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

Posted by "Ittay Dror (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BUILDR-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770056#action_12770056 ] 

Ittay Dror commented on BUILDR-333:
-----------------------------------

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.


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

Posted by "Ittay Dror (JIRA)" <ji...@apache.org>.
     [ 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.


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

Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BUILDR-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Toulme updated BUILDR-333:
----------------------------------

    Fix Version/s: Wish List

Targeting wishlist.

Note Eclipse and Buildr compile and package in different ways: Eclipse will put resources next to .class files, while buildr puts resources in target/resources, that makes me think this is mostly either an invalid bug or a big problem.

> 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
>             Fix For: Wish List
>
>
> 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.