RE: 1.6.0 + ns
I also find this a bit counter-intuitive Matt, but look at it the other way around. Before the way-NS-are-handled change in beta3, if you had a custom task that had an addXyz(XyzType xyz), where XyzType is a custom type, you would be doing something like: my:task xyz ... / /my:task Even though xyz is defined in the AntLib of NS prefix 'my'. This is also counter-intuitive. To get a limited form of polymorphism, one could use the NS of the nested element to instantiate it... Assume the 'my' AntLib provides it's own 'enhanced' fileset declared under the fileset type name. Doing: my:task my:fileset ... / /my:task could be made different to: my:task fileset ... / /my:task by instantiating a 'my' fileset instead of an Ant one. By this scheme breaks down because the nested element name is controlled by the add* method name, not the type of it's argument. Assume you have a task accepting two Paths as nested elements, one for the classpath, another for the systempath. To have the scheme I decribe above work, you'd have to alias your (fictitious) custom Path as both classpath and systempath. This just doesn't scale. The solution is the proposed ant:type attribute, which unfortunately didn't make it to Ant 1.6. With it, you could do: javac classpath ant:type=my:buildpath ... / javac for example, or: my:task my:systempath ... / !-- Regular Ant Path -- my:classpath ant:type=my:buildpath ... / !-- Custom Path -- /my:task I hope I'm making sense. Peter will correct me if I said anything silly ;-) --DD -Original Message- From: Matt Benson Okay, I confess to never having gotten around to testing beta3. :( So I am just now dealing with the final way of handling namespaces, particularly with namespaced antlibs. I have custom tasks that take nested elements of normal Ant types such as fileset... pretty common, of course. Now, adding my antlib's namespace to fileset or mapper i.e. mylib:fileset, mylib:mapper seems to work but is counterintuitive to my eye. Is it an accident that this works? Should I be using Ant's default/core namespace? What is that? I know I've seen some messages that alluded to it but I can't find them now in the archives... -Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
typo
I found two typo in docs/manual/CoreTypes/filterchain.html. reading the ant manual month for me:-) Index: filterchain.html === RCS file: /home/cvspublic/ant/docs/manual/CoreTypes/filterchain.html,v retrieving revision 1.15 diff -u -i -r1.15 filterchain.html --- filterchain.html1 Dec 2003 22:03:25 - 1.15 +++ filterchain.html20 Dec 2003 09:59:05 - @@ -23,12 +23,12 @@ lt;copy file=quot;fooquot; tofile=quot;barquot; head=quot;10quot; contains=quot;bleequot;/gt; /codeP The obvious problem thus surfaced: Ant tasks would not be able -to accomodate such data transformation attributes as they would +to accommodate such data transformation attributes as they would be endless. The task would also not know in which order these attributes were to be interpreted. That is, must the task execute the contains attribute first and then the head attribute or vice-versa? What Ant tasks needed was a mechanism to allow pluggable filter (data -tranformer) chains. Ant would provide a few filters for which there +transformer) chains. Ant would provide a few filters for which there have been repeated requests. Users with special filtering needs would be able to easily write their own and plug them in.P @@ -1344,4 +1344,4 @@ HR P align=centerCopyright copy; 2002-2003 Apache Software Foundation. All rights -Reserved./P/BODY/HTML \ No newline at end of file +Reserved./P/BODY/HTML -- Yuji Yamano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25668] - FTP get actions won't download files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25668. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25668 FTP get actions won't download files --- Additional Comments From [EMAIL PROTECTED] 2003-12-20 12:54 --- Hi, what is the default directory for the user anonymous when logging on to your ftp server ? if the default directory is not C:\, you need to specify a remotedir. Pay attention, when doing a ftp action=get .../ , the basedir of the nested fileset does not count, only the include/exclude patterns of the fileset are used. The remotedir attribute will tell the ftp task where to cd to. Cheers, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant/docs/manual/CoreTypes filterchain.html
antoine 2003/12/20 05:25:55 Modified:docs/manual/CoreTypes filterchain.html Log: typo Submitted by: Yuji Yamano Revision ChangesPath 1.16 +3 -3 ant/docs/manual/CoreTypes/filterchain.html Index: filterchain.html === RCS file: /home/cvs/ant/docs/manual/CoreTypes/filterchain.html,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- filterchain.html 1 Dec 2003 22:03:25 - 1.15 +++ filterchain.html 20 Dec 2003 13:25:55 - 1.16 @@ -23,12 +23,12 @@ lt;copy file=quot;fooquot; tofile=quot;barquot; head=quot;10quot; contains=quot;bleequot;/gt; /codeP The obvious problem thus surfaced: Ant tasks would not be able -to accomodate such data transformation attributes as they would +to accommodate such data transformation attributes as they would be endless. The task would also not know in which order these attributes were to be interpreted. That is, must the task execute the contains attribute first and then the head attribute or vice-versa? What Ant tasks needed was a mechanism to allow pluggable filter (data -tranformer) chains. Ant would provide a few filters for which there +transformer) chains. Ant would provide a few filters for which there have been repeated requests. Users with special filtering needs would be able to easily write their own and plug them in.P @@ -1344,4 +1344,4 @@ HR P align=centerCopyright copy; 2002-2003 Apache Software Foundation. All rights -Reserved./P/BODY/HTML \ No newline at end of file +Reserved./P/BODY/HTML - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant/docs/manual/CoreTypes filterchain.html
antoine 2003/12/20 05:26:44 Modified:docs/manual/CoreTypes Tag: ANT_16_BRANCH filterchain.html Log: Merge from HEAD Typo correction Submitted by: Yuji Yamano Revision ChangesPath No revision No revision 1.13.2.4 +2 -2 ant/docs/manual/CoreTypes/filterchain.html Index: filterchain.html === RCS file: /home/cvs/ant/docs/manual/CoreTypes/filterchain.html,v retrieving revision 1.13.2.3 retrieving revision 1.13.2.4 diff -u -r1.13.2.3 -r1.13.2.4 --- filterchain.html 12 Nov 2003 09:36:08 - 1.13.2.3 +++ filterchain.html 20 Dec 2003 13:26:44 - 1.13.2.4 @@ -24,12 +24,12 @@ lt;copy file=quot;fooquot; tofile=quot;barquot; head=quot;10quot; contains=quot;bleequot;/gt; /codeP The obvious problem thus surfaced: Ant tasks would not be able -to accomodate such data transformation attributes as they would +to accommodate such data transformation attributes as they would be endless. The task would also not know in which order these attributes were to be interpreted. That is, must the task execute the contains attribute first and then the head attribute or vice-versa? What Ant tasks needed was a mechanism to allow pluggable filter (data -tranformer) chains. Ant would provide a few filters for which there +transformer) chains. Ant would provide a few filters for which there have been repeated requests. Users with special filtering needs would be able to easily write their own and plug them in.P - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: typo
Yuji Yamano wrote: I found two typo in docs/manual/CoreTypes/filterchain.html. reading the ant manual month for me:-) Thanks for your corrections Yuji, they are now submitted both in HEAD and in the ANT_16_BRANCH. Cheers, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant ReleaseInstructions
antoine 2003/12/20 08:19:00 Modified:.ReleaseInstructions Log: The ant 1.6.0 distribution includes 5 documents which still refer to the beta, most notably the index.html at the root of the docs directory. Let's try to put the ReleaseInstructions in an order such that we do not have this type of problems in the future. PR: 25652 Revision ChangesPath 1.21 +38 -20ant/ReleaseInstructions Index: ReleaseInstructions === RCS file: /home/cvs/ant/ReleaseInstructions,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- ReleaseInstructions 30 Sep 2003 13:08:00 - 1.20 +++ ReleaseInstructions 20 Dec 2003 16:19:00 - 1.21 @@ -39,17 +39,35 @@ to the right areas of Ant's website. ]] 5. Before a build : -Update the following files for version number, and commit your changes. - -* docs/manual/cover.html -* docs/manual/credits.html -* build.xml (version property) the first beta on the 1.6 branch should be called 1.6Beta1, ... the version property in build.xml governs the output of ant -version and the naming of the distribution files. +Update the following files for version number: + +On the branch only : + +* docs/manual/cover.html +* docs/manual/credits.html +* build.xml (version property manifest-version property) + +Commit your changes. + +On the branch and on the main trunk (*): + +* xdocs/antnews.xml (Announcement) +* xdocs/faq.xml (Ant's history details - not for betas) +* xdocs/index.xml (Announcement, latest release details, link to +manual under Documentation) +* xdocs/srcdownload.xml +* xdocs/bindownload.xml + +Generate the html files by invoking ant on docs.xml - you need +jakarta-site2 checked out for this. Commit the modified/generated +files + 6. Ensure you have all the external libraries that Ant uses in your lib/optional directory. To find out what libraries you need, execute the build with -verbose option and scan for lines beginning with @@ -101,7 +119,9 @@ 12. Address the available release tags in BugZilla. Create a new tag 1.6Beta1 and a 1.7Alpha. Assign all existing 1.6 alpha bugs to one of these release -labels. +labels. Note that such massive changes can be done at once by choosing the +link Change several bugs at once at the bottom of the bug list +displaying the 1.6alpha bugs. 13. Once that is done, do a test download to make sure everything is OK. A common problem may be: @@ -114,15 +134,7 @@ made (ant website, main jakarta website, announcements@jakarta.apache.org, etc). -Also ensure you: -* Update antnews.xml (Announcement) -* Update faq.xml (Ant's history details - not for betas) -* Update index.xml (Announcement, latest release details, link to - manual under Documentation) - -Generate the html files by invoking ant on docs.xml - you need -jakarta-site2 checked out for this. Commit the modified/generated -files and also perform a cvs update on files in minotaur's +and also perform a cvs update on files in minotaur's /www/ant.apache.org/ Announce beta releases at freshmeat.net (Stefan Bodewig is the @@ -160,12 +172,13 @@ * Make sure that the symbolic link README.html points to the new RELEASE-NOTES. -18. Change the links in /xdocs/bindownload.xml and /xdocs/srcdownload.xml, -regenerate the HTML files, commit and update the site. +18. Update the ant.apache.org site : + +running cvs update *.html under /www/ant.apache.org should update the +files regenerated and committed in point 5 above (index.html, faq.html, +antnews.html, srcdownload.html, bindownload.html). -As the mirrors may need some days to pick up the new release, you -may want to add a note to that effect to the pages and remove it a few -days later. +Update the online manual too. 19. Clean up. @@ -197,3 +210,8 @@ 22. You can now reacquaint yourself with your family and friends. +(*) the xdocs need to be updated on both the branch and the HEAD revision + because traditionally the ant.apache.org web site reflects the HEAD + revisio of the xdocs, but the users downloading a distribution will get + the xdocs and the generated html from the branch and will complain if there + are discrepancies in version numbers. \ No newline at end of file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
cvs commit: ant ReleaseInstructions
antoine 2003/12/20 08:31:45 Modified:.ReleaseInstructions Log: Re add something about mirrors. Revision ChangesPath 1.22 +11 -2 ant/ReleaseInstructions Index: ReleaseInstructions === RCS file: /home/cvs/ant/ReleaseInstructions,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- ReleaseInstructions 20 Dec 2003 16:19:00 - 1.21 +++ ReleaseInstructions 20 Dec 2003 16:31:45 - 1.22 @@ -3,6 +3,7 @@ Authors: Conor MacNeill Stefan Bodewig Magesh Umasankar + Antoine Levy-Lambert Note: This document was updated in the context of releasing Ant 1.6. Please interpret the branch names, tags, etc. according to @@ -172,6 +173,8 @@ * Make sure that the symbolic link README.html points to the new RELEASE-NOTES. +(**) + 18. Update the ant.apache.org site : running cvs update *.html under /www/ant.apache.org should update the @@ -212,6 +215,12 @@ (*) the xdocs need to be updated on both the branch and the HEAD revision because traditionally the ant.apache.org web site reflects the HEAD - revisio of the xdocs, but the users downloading a distribution will get + revision of the xdocs, but the users downloading a distribution will get the xdocs and the generated html from the branch and will complain if there - are discrepancies in version numbers. \ No newline at end of file + are discrepancies in version numbers. + +(**) Mirrors : the srcdownload.html and bindownload.html each list a number of + mirrors. For ant 1.6.0 the mirrors picked up the new version in 8 hours + or less, the release having been done at midnight on Dec 18th, the + mirrors had it on Dec 19th at 8 am. The srcdownload/bindownload pages both + contain a note advising users to be patient immediately after the release. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant ReleaseInstructions
antoine 2003/12/20 08:33:20 Modified:.Tag: ANT_16_BRANCH ReleaseInstructions Log: Merge from HEAD Improve ReleaseInstructions to deliver a doc with a welcome page showing the version number being delivered. PR: 25652 Revision ChangesPath No revision No revision 1.17.2.5 +48 -24ant/ReleaseInstructions Index: ReleaseInstructions === RCS file: /home/cvs/ant/ReleaseInstructions,v retrieving revision 1.17.2.4 retrieving revision 1.17.2.5 diff -u -r1.17.2.4 -r1.17.2.5 --- ReleaseInstructions 16 Dec 2003 14:48:10 - 1.17.2.4 +++ ReleaseInstructions 20 Dec 2003 16:33:20 - 1.17.2.5 @@ -3,6 +3,7 @@ Authors: Conor MacNeill Stefan Bodewig Magesh Umasankar + Antoine Levy-Lambert Note: This document was updated in the context of releasing Ant 1.6. Please interpret the branch names, tags, etc. according to @@ -39,17 +40,35 @@ to the right areas of Ant's website. ]] 5. Before a build : -Update the following files for version number, and commit your changes. - -* docs/manual/cover.html -* docs/manual/credits.html -* build.xml (version property) the first beta on the 1.6 branch should be called 1.6Beta1, ... the version property in build.xml governs the output of ant -version and the naming of the distribution files. +Update the following files for version number: + +On the branch only : + +* docs/manual/cover.html +* docs/manual/credits.html +* build.xml (version property manifest-version property) + +Commit your changes. + +On the branch and on the main trunk (*): + +* xdocs/antnews.xml (Announcement) +* xdocs/faq.xml (Ant's history details - not for betas) +* xdocs/index.xml (Announcement, latest release details, link to +manual under Documentation) +* xdocs/srcdownload.xml +* xdocs/bindownload.xml + +Generate the html files by invoking ant on docs.xml - you need +jakarta-site2 checked out for this. Commit the modified/generated +files + 6. Ensure you have all the external libraries that Ant uses in your lib/optional directory. To find out what libraries you need, execute the build with -verbose option and scan for lines beginning with @@ -101,7 +120,9 @@ 12. Address the available release tags in BugZilla. Create a new tag 1.6Beta1 and a 1.7Alpha. Assign all existing 1.6 alpha bugs to one of these release -labels. +labels. Note that such massive changes can be done at once by choosing the +link Change several bugs at once at the bottom of the bug list +displaying the 1.6alpha bugs. 13. Once that is done, do a test download to make sure everything is OK. A common problem may be: @@ -114,15 +135,7 @@ made (ant website, main jakarta website, announcements@jakarta.apache.org, etc). -Also ensure you: -* Update antnews.xml (Announcement) -* Update faq.xml (Ant's history details - not for betas) -* Update index.xml (Announcement, latest release details, link to - manual under Documentation) - -Generate the html files by invoking ant on docs.xml - you need -jakarta-site2 checked out for this. Commit the modified/generated -files and also perform a cvs update on files in minotaur's +and also perform a cvs update on files in minotaur's /www/ant.apache.org/ Announce beta releases at freshmeat.net (Stefan Bodewig is the @@ -141,8 +154,8 @@ file under /usr/local/apache2/logs 16. When the final beta is considered OK, propose a vote on [EMAIL PROTECTED] to -officially adopt the latest beta as the Ant 1.6.0 release. If it is passed, -(it usually does,) this would be labelled ANT_160 and built in a similar +officially adopt the latest beta as the Ant 1.6 release. If it is passed, +(it usually does,) this would be labelled ANT_16 and built in a similar fashion to the above process. 17. BUT @@ -160,15 +173,15 @@ * Make sure that the symbolic link README.html points to the new RELEASE-NOTES. -18. Change the links in /xdocs/bindownload.xml and /xdocs/srcdownload.xml, -regenerate the HTML files, commit and update the site. +(**) + +18. Update the ant.apache.org site : -Updating the site includes updating the online manual which should display -the manual of ant 1.6.0 instead of 1.5.4 +running cvs update *.html under /www/ant.apache.org should update the +files regenerated and committed in point 5 above (index.html,
DO NOT REPLY [Bug 25652] - Minor nits in documentation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25652. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25652 Minor nits in documentation [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Target Milestone|--- |1.6.1 --- Additional Comments From [EMAIL PROTECTED] 2003-12-20 16:52 --- Hi Sebb, concerning the Welcome page, I have fixed our release procedures to avoid delivering a version of ant with an index page referring to the previous version in the future. Concerning the WHATSNEW, it is a similar type of problem. The WHATSNEW in the binary comes from the ANT_16_BRANCH, where we had concentrated on delivering a history of changes between each beta. On the download site, the release notes are showing the changes between ANT 1.5.4 and ANT 1.6.0. OK, this is inconsistent too. This http://www.apache.org/dist/ant/README.html is shorter than the WHATSNEW of the distribution, because it does not contain some bug reports which were regressions of the 1.6 alpha or beta versions compared to 1.5.4 and were fixed before 1.6.0. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25674] New: - delete with followSymlinks=false fails if pointed at non-existant directory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25674.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25674
delete with followSymlinks=false fails if pointed at non-existant directory
Summary: delete with followSymlinks=false fails if pointed at
non-existant directory
Product: Ant
Version: 1.7Alpha (nightly)
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
While trying to write a failing test case reflecting bug 25181 I stumbled on to
this behavior.
This works when ${tdir} doesn't exist
target name=setup
delete dir=${tdir}/
mkdir dir=${tdir}/
/target
This doesn't work when ${tdir} doesn't exist
target name=setup
delete dir=${tdir} followSymlinks=false/
mkdir dir=${tdir}/
/target
In the latter case I get:
[junit] Testcase: testSingle took 0.141 sec
[junit] Caused an ERROR
[junit]
/home/gus/projects/ant/src/etc/testcases/taskdefs/optional/unix/test-working not
found.
[junit]
/home/gus/projects/ant/src/etc/testcases/taskdefs/optional/unix/symlink.xml:36:
/home/gus/projects/ant/src/etc/testcases/taskdefs/optional/unix/test-working not
found.
[junit] at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:387)
[junit] at
org.apache.tools.ant.taskdefs.MatchingTask.getDirectoryScanner(MatchingTask.java:231)
[junit] at org.apache.tools.ant.taskdefs.Delete.execute(Delete.java:555)
[junit] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:306)
[junit] at org.apache.tools.ant.Task.perform(Task.java:401)
[junit] at org.apache.tools.ant.Target.execute(Target.java:338)
[junit] at org.apache.tools.ant.Target.performTasks(Target.java:365)
[junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1237)
[junit] at
org.apache.tools.ant.BuildFileTest.executeTarget(BuildFileTest.java:269)
[junit] at
org.apache.tools.ant.taskdefs.optional.unix.SymlinkTest.setUp(SymlinkTest.java:97)
[junit] at junit.framework.TestCase.runBare(TestCase.java:125)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:326)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1004)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:676)
[junit] at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:650)
[junit] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:306)
[junit] at org.apache.tools.ant.Task.perform(Task.java:401)
[junit] at org.apache.tools.ant.Target.execute(Target.java:338)
[junit] at org.apache.tools.ant.Target.performTasks(Target.java:365)
[junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1237)
[junit] at
org.apache.tools.ant.Project.executeTargets(Project.java:1094)
[junit] at org.apache.tools.ant.Main.runBuild(Main.java:705)
[junit] at org.apache.tools.ant.Main.startAnt(Main.java:225)
[junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:215)
[junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:90)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 25181] - SYMLINK task creates cyclic symlinks
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181 SYMLINK task creates cyclic symlinks --- Additional Comments From [EMAIL PROTECTED] 2003-12-20 19:20 --- I have replicated this in a failing test case now. It seems I have run afoul of a polymorphic syntax in the ln command ln [OPTION]... TARGET [LINK_NAME] ln [OPTION]... TARGET... DIRECTORY Obviously, I need to account for this Hopefully by later today. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
