[ http://issues.apache.org/jira/browse/BEEHIVE-403?page=comments#action_60196 ] Heather Stephens commented on BEEHIVE-403: ------------------------------------------
Not sure how many different combos there are out there in the world *grin*, but here's some info from my experience... In Windows OS I tried gnu tar in the mks, cygwin and the DOS shells and had various issues with all of them. I also tried mks tar ... this generated the files and I could unzip them in mks tar on Windows but linux users reported the archives were corrupt. The only combination of tar and shell on Windows I found that completed successfully and generated a tar.gz file that could be uncompressed "universally" (any OS, any shell, any tar version that users have tried so far) was the version of tar that comes with Windows executed from a DOS shell. This is why Ken's use of "exec" to work around the ANT bug works (obviously as long as gnu tar doesn't supercede Windows DOS tar). That said, I'm sure I didn't try all possible combinations. It was hard to test as I don't have a linux box. Another note: some people who may end up using this target to generate Beehive archives for shipping may only have a windows operating system. Somehow we have to be able to successfully generate archives from a Windows box that all users can unarchive. Hope this helps... > 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 > > 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
