/*.* behaves like /**/*.*

[Kaiserludi]

Our scripts make a lot use of /. and /**/..
The first copies all top level files in the folder, but no subfolders, the second one additionally also includes subfolders
This has worked fine until we have upgraded to version 0.9.2, but after upgrading /. now also copies includes the subfolders, so that the only way to only copy all the top-level files in a folder withouth also copying the subfolders, is, to specify every used file-ending separately. This can be reprocuded, by for example switching back to an older nant version like 0.91-alpha2 - the same unchanged scripts work correctly again, but only until switching forward to 0.92 again. i have not tried with any version between 0.91-alpha2 and 0.92, so I can't tell the exact version, that has introduced that bug.

[dguder]

Could you please provide me an example how you use /. in your build files. I was not able to reproduce this issue.

[Kaiserludi]

https://dl.dropbox.com/u/4296291/reproCase.zip
The buildfile in the zip with nant 0.91 correctly just copies test.txt from Bar into Foo, but with nant 0.92 it wrongly also copies SubFolder/test.txt from Bar into Foo.

[dguder]

Thanks for the repro, I see the issue now.

[rmboggs]

I believe this is related to one of my fixes I put into 0.92 while trying to address another bug request. That being said, I was thinking about seeing whether or not I can switch this back to only recognize files with . without disrupting the rest of the fix. I'll assign this to me.

[dguder]

Ok.

[rmboggs]

Please check to see if the recent commit to my issues_64_85 branch solves for this issue.

[rmboggs]

I believe that the pull request I just made should resolve this.

[rmboggs]

This type of issue has been reported a few times. This should be fixed now.

[awglyde]

A bit late to the party. @rmboggs will a new version of nant-0.92 be posted on sourcetree that has this fix?