[
https://issues.apache.org/jira/browse/BUILDR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760304#action_12760304
]
Alex Boisvert commented on BUILDR-322:
--------------------------------------
I've fixed this for .java, .scala and .groovy files for the 1.3.5 release.
Support for other languages may need additional code + refactoring.
boisv...@sixtine:~/svn/buildr-java$ svn commit -m "Fix BUILDR-322 timestamp
check for .java, .scala and .groovy files"
Sending lib/buildr/core/compile.rb
Transmitting file data .
Committed revision 819657.
> When specifying files (instead of directories) as sources for compile task,
> Buildr uses target directory timestamp only (not compiled output timestamp)
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BUILDR-322
> URL: https://issues.apache.org/jira/browse/BUILDR-322
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.2, 1.3.3, 1.3.4
> Reporter: Alex Boisvert
> Assignee: Alex Boisvert
> Fix For: 1.3.5
>
>
> When specifying files (instead of directories) as sources for compile task,
> Buildr uses target directory timestamp only... not the compiled output file
> timestamp.
> This is an issue in two noteworthy cases:
> 1) On Windows, the target directory's timestamp is not updated when files are
> added/updated/removed (which breaks incremental builds)
> 2) If the target directory is under version control, its timestamp may be
> more recent than sources (and thus sources are never compiled)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
