[ http://issues.apache.org/jira/browse/BEEHIVE-403?page=comments#action_60224 ] Jim Cummings commented on BEEHIVE-403: --------------------------------------
Sent this around by email last night when JIRA was down - just adding this in for historical purposes.... Digging around the ant docs at http://ant.apache.org/manual/CoreTasks/tar.html, it sounds like different tar apps support file paths >100 characters in incompatible ways. Ant defaults to generating long file paths the GNU way, which apparently does not work with MKS tar. Unfortunately we have lots of files in our distribution with paths >100 chars. I don't know if GNU tar can untar MKS tar files with long file paths, but that would require MKS tar for dist builds. I did try using WinZip on the .tar.gz archive we have on the website and even WinZip seems to have troubles with the long file paths. My gut is that the norm is to do GNU formatted tars since Linux users will be using the GNU tar, and I would assume most Windows users would just use the .ZIP versions. > ant build.dist.archives does not work from DOS window > ----------------------------------------------------- > > Key: BEEHIVE-403 > URL: http://issues.apache.org/jira/browse/BEEHIVE-403 > Project: Beehive > Type: Bug > Components: Build > Versions: V1, V1Beta > Environment: Windows, DOS Shell, cygwin at end of my PATH and a drive letter > in my paths > Reporter: Jim Cummings > Priority: Minor > Attachments: installed.db > > This is really 2 related problems: > 1) When I run ant build.dist.archives from my DOS prompt, the .gz files do > not generated. There are errors that go by, but the build still thinks it is > successful. In distribution.xml, if you add a failonerror="true" attribute > to the exec elements this lets it fail the build if tar failed. Might want > to do this for the 'svn' execs as well. > 2) The other problem is why the .gz files are not getting generated. My path > is finding my cygwin GNU tar (version 1.13.25). The cause is that tar is > failing with this error: > [exec] D: Unknown Host > [exec] > apache-beehive-incubating-svn-snapshot/docs/apidocs/classref_controls/org/apache/beehive/controls/api/bean/ControlInterface.html > [exec] tar (child): > D\:\\beehive_trunk\\trunk\\build\\dist\\archives/apache-beehive-incubating-svn-snapshot.tar.gz: > Cannot open: Input/Output error > [exec] tar (child): Error is not recoverable: exiting now > Apparently GNU tar fails with the "Unknown Host" error if you use drive > letters in your file paths. I tried taking it out of my BEEHIVE_HOME, but > the drive letter crops up from somewhere else still. If you add this as the > 1st argument to the exec tar element it seems to fix the problem. > <arg value="--force-local"/> -- 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
