You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Kenneth Tam (JIRA)" <be...@incubator.apache.org> on 2005/02/23 01:23:56 UTC
[jira] Assigned: (BEEHIVE-86) tar.gz file probs from build.dist.archives
[ http://issues.apache.org/jira/browse/BEEHIVE-86?page=history ]
Kenneth Tam reassigned BEEHIVE-86:
----------------------------------
Assign To: Kenneth Tam
It's not clear to me that anything's changed here (ie, whether the <tar> task under Windows handles long paths correctly), but I'll investigate.
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://issues.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Assignee: Kenneth Tam
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira