Wildcard syntax

13 views
Skip to first unread message

Oliver Gierke

unread,
Aug 4, 2008, 9:03:17 AM8/4/08
to architecture-rules-users
As already mentioned here I'd linke to suggest the ANT style wildcard
package syntax over the current one as it seems to be more readable.
Especially the multiple packages match seems quite weird to me.

E.g.:
foo.bar.**.foobar - matches all packages beginning with foo.bar and
ending with foobar
foo.bar.** - matches all packages beginning with foo.bar

If its very hard to decide which version to choose, maybe we could let
the individual user configure this in the rules file and provide one
of the syntax versions as default.

Any opinions?

Regards,
Ollie

Mike Nereson

unread,
Aug 4, 2008, 10:46:27 AM8/4/08
to architecture...@googlegroups.com
I went with .* and ..* because that's how Spring AOP (which uses AspectJ.) Spring is pretty widely used so I figured it was a safe bet to go with.

No doubt, ANT is also very widely used. I don't use it, so I was not familiar with .**

I suppose it would be possible to allow for either format to provide backwards compatibility. Anyone else have any other comments?

~ Mike Nereson


On Mon, Aug 4, 2008 at 9:03 AM, Oliver Gierke <oliver...@once-media.de> wrote:

As already mentioned here I'd like to suggest the ANT style wildcard

Oliver Gierke

unread,
Aug 4, 2008, 11:09:23 AM8/4/08
to architecture-rules-users
Mike Nereson wrote:
> I suppose it would be possible to allow for either format to provide
> backwards compatibility. Anyone else have any other comments?

That's a good point. Haven't thought of that before. Although I fear
intermingling both styles could confuse the one or the other.

Regards,
Ollie
Reply all
Reply to author
Forward
0 new messages