[
https://issues.apache.org/jira/browse/BUILDR-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Donald closed BUILDR-383.
-------------------------------
> artifact().from(task_dependency) should not trigger task_dependency if
> artifact exists
> --------------------------------------------------------------------------------------
>
> Key: BUILDR-383
> URL: https://issues.apache.org/jira/browse/BUILDR-383
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.3.5
> Reporter: Alex Boisvert
> Fix For: 1.4
>
> Attachments: BUILDR-383-patch.txt, BUILDR-383.txt
>
>
> As discussed in this thread:
> http://markmail.org/thread/znfqqa45fxrpd4lg
> There's a problem with artifact().from() where if it's passed a task
> dependency (e.g. FileTask), then the file task will either
> 1) always be invoked -- even if the artifact already exists
> 2) fail with an error such as,
> Buildr aborted!
> Don't know how to build task
> '/home/boisvert/tmp/buildr-zip2/target/zip/google-collect-1.0/google-collect-1.0.jar'
> if the FileTask.to_s returns a non-absolute pathname (which is the case for
> Rake's default FileTask, but not Buildr's file(...) method)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
