why ** is slightly different between Ant and Java 7

[Jeanne Boyarsky]

The code and scenario are here

It ends with:

The Ant approach probably feels more natural to me because I’ve been using it longer. But the Java approach seems more logical because it doesn’t have the extra slash that doesn’t actually get matched.

Which approach do you find more natural? I suspect the Java once, but I'd like to see if that reality matches for someone who hasn't used Ant.

[Bill Gorder]

I like the Ant one, but like you I have used so many frameworks that have adapted the Ant style pattern matching that I am probably just used to it.

[Jeanne Boyarsky]

Bill Gorder wrote:I like the Ant one, but like you I have used so many frameworks that have adapted the Ant style pattern matching that I am probably just used to it.

Interesting. Can you give an example of a framework that uses the Ant style? I wasn't aware it was adopted elsewhere. (it isn't surprising though)

[Bill Gorder]

The most notable one is Spring, and of course Spring Security (and Acegi before that). Apache Shiro (another Security framework) also uses ant style pattern/path matching.

http://docs.spring.io/spring-security/site/docs/3.2.0.RELEASE/apidocs/org/springframework/security/web/util/AntPathRequestMatcher.html
http://docs.spring.io/spring/docs/3.1.4.RELEASE/javadoc-api/org/springframework/util/AntPathMatcher.html
http://docs.spring.io/spring/docs/2.5.6/api/org/springframework/core/io/support/PathMatchingResourcePatternResolver.html

To name a few of the classes.

[Jeanne Boyarsky]

Of course. I've even used that feature in Spring. I didn't notice the style of ** because I just assumed it always worked that way! Thanks for reminding.