Got it, thanks!
On Wed, 20 Jul 2016 at 14:01 Carsten Ziegeler <[email protected]> wrote:
> > Hi,
> >
> > I'm not sure if options 2 + 4 work together without changing the API yet
> > one more time when / if we decide to also support regex (albeit just a
> > minor increase). I have nothing against supporting them from the
> beginning
> > - unfortunately we don't have a clear separation between API and
> > implementation here and the API has to anyways state what it supports.
> >
> > This means that a ResourceChangeListener will support the following ways
> > for defining a matcher:
> >
> > 1. explicit paths, absolute or relative to search paths
> > 2. '.' , for the cases when the listener is interested in all changes
> under
> > the search paths
> > 3. limited glob pattern matching ('*', '**'), by prefixing the pattern
> with
> > 'glob:'
> > 4. regex matching, by prefixing the pattern with 'regex:'
> >
> > Did I miss something?
> >
>
> Looks good, as stated previously I would prefer to not support regex:
> for now. We can add it in a later version if really required. And by
> using the prefixes we can add it without breaking existing configurations.
>
> Carsten
>
