|
| Re: Oomph filter explanation [message #1725165 is a reply to message #1725079] |
Tue, 01 March 2016 10:25  |
 Ed Merks
Messages: 33218
Registered: July 2009 |
Senior Member |
|
|
Mikael,
There was a bug that I fixed yesterday, so is only available in a
nightly build at the moment:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=487872
That caused exceptions to be thrown which made the filters never ever
match (to exclude everything). Filters are inclusive, i.e., the filter
must match (be true) for the task to be enabled. Perhaps you're running
into that problem. You'd see the exceptions in the log...
Filters are implemented using exactly p2's filtering mechanism (and
implementation):
https://wiki.eclipse.org/Equinox_P2_Resolution#Enablement_filter
https://tools.ietf.org/html/rfc1960
So I think (filter.me==true) or (!(filter.me==false)) depending on how
you want to treat the absent value by default.
On 29.02.2016 15:49, Mikael Karlback wrote:
> So I am trying to use the new oomph filter functionality but I am
> failing to get i t to work. So I have a few questions..
>
> Are the filters including or excluding?
>
> what is the syntax?
> Putting (1==1) seems to exclude the content but (!(1==1)) gives me the
> same result so I am a bit confused.
> How would I match an environment variable? I.e. putting
> -Dfilter.me=false in the eclipse ini and trying to use it in an oomph
> configuration.
> would the syntax be something like (${filter.me}) ?
>
> How about putting something like -Dfilter.name=filtername in the
> eclipse.ini how would I use that in the filter?
>
> BR Mikael Karlbäck
>
>
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.04397 seconds
] 
Search
Help
Register
Login
Home
