You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jonathan Costers (JIRA)" <ji...@apache.org> on 2009/03/30 03:08:50 UTC

[jira] Commented: (RIVER-270) tar tasks in release* ant targets fail due to 100-char limitation and are disabled

    [ https://issues.apache.org/jira/browse/RIVER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693631#action_12693631 ] 

Jonathan Costers commented on RIVER-270:
----------------------------------------

I re-enabled the tar tasks and added the longfile="gnu" parameter, meaning that long filenames will only be handled correctly by GNU complient tar.
Other possibilities are to fail, truncate, omit or warn, but that doesn't help much.
This change has been done in patch RIVER-301-JC-5.1.patch.

> tar tasks in release* ant targets fail due to 100-char limitation and are disabled
> ----------------------------------------------------------------------------------
>
>                 Key: RIVER-270
>                 URL: https://issues.apache.org/jira/browse/RIVER-270
>             Project: River
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: AR1
>            Reporter: Frank Barnaby
>            Priority: Minor
>
> The tar tasks in the release.bin and release.src ant targets fail due to a known 100-character limitation.  Consequently, these tasks are disabled (ie, commented-out).  Further investigation is necessary.
> Note that the Ant tar task has a "logfile" attribute that offers a variety of options for dealing with the
> 100-character limitation, but the viability of those options will need to be determined.

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