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