DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40059>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40059 Summary: Add method to explicitly define symlinks in <tar> task Product: Ant Version: 1.6.5 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Core tasks AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] Bug #15244 explains why it's pretty hard to read symlinks from the filesystem. However, it occurred to me that there's no reason why the <tar> task couldn't be told explicitly what symlinks to create and include them in the archive. The advantage with this approach is that I could run the build script on Windows (which doesn't support symlinks in the Unix sense) and still generate a .tar archive that could be extracted on Linux with the proper symlinks. I'm proposing the creation of a nested <symlink> element that provides the name and target (and perhaps other attributes) for the symlink. The <tar> task would read the element and generate a symlink within the .tar archive. At no point would there need to be a symlink on the actual filesystem itself. For example, this would create a symlink called "link" (in the root directory) with a relative path pointing to the file "foo/bar/target": <tar destfile="archive.tar"> <tarfileset dir="somedir"> <include name="foo/bar/target"/> </tarfileset> <symlink name="link" target="foo/bar/target"/> </tar> Another option might be to have the <symlink> element under the <tarfileset> element so that it can inherit settings like user, group and permissions. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
