[jira] Resolved: (BUILDR-292) Downloading resources only works if "tmp" and ".m2" are on the same disk

["Victor Hugo Borja (JIRA)" <ji...@apache.org>]

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

Victor Hugo Borja resolved BUILDR-292.
--------------------------------------

    Resolution: Fixed

I was getting a "Permission denied" error on my ubuntu box (/tmp and ~/.m2 are on different devices), a workaround could be to set TMPDIR as Assaf commented on BUILDR-287, however that would require almost every Buildr user running on JRuby 1.3+ (at least those on unix with /tmp and ~/.m2 on different devices) to set the environment variable for buildr to work correctly.  

I've introduced buildr to my current client and so far they like it, but this issue has become a pain for people trying _jbuildr for the first time just to find that it can't  download the ant artifact unless they set TMPDIR to a directory on the same device as ~/.m2. 

So I've commited rev 799169 to fix this issue (following Charles Nutter advice on JRUBY-3381) by doing cp;mv if source and target are on != devices.

An alternative solution (that doesn't patch FileUtils) is at
    http://github.com/vic/buildr/commit/c6d8a8579beed3f220247aa64127051b40f6dd4e#L2R360





> Downloading resources only works if "tmp" and ".m2" are on the same disk
> ------------------------------------------------------------------------
>
>                 Key: BUILDR-292
>                 URL: https://issues.apache.org/jira/browse/BUILDR-292
>             Project: Buildr
>          Issue Type: Bug
>    Affects Versions: 1.3.4
>         Environment: Linux
> using the "java buildr"
>            Reporter: Klaas Prause
>            Priority: Minor
>
> We had a strange bug on our CI-Server. The download of artifacts (i.e. ANT jars) was not working, because of a "permission denied" issue. Only our admin found out that buildr uses the "rename" command to move downloaded artifacts from their download location to the repository. Rename only works if the directories are on the same disk, it would probably help to use "mv" for the implicit cp rm if the folders are on different disks.
> This issue is always a problem if the tmp-dir is located on a different drive.
> I cannot provide more information, because our admin fixed the issue by changing the folder for the tmp dir. The command he used to identify the issue was "strace -f -ox buildr build". The output file shows the failing rename command.
> Regards
> Klaas

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