felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <fmesc...@gmail.com>
Subject Should Sling itself provide the Enum for SlingFilterScope ? (was: [jira] Created: (FELIX-2665) getting error about SlingFilterScope not being applicable for <T extends Enum>)
Date Mon, 18 Oct 2010 07:33:41 GMT

Currently the SlingFilterScope is an scr-annotation-only Enum listing
two known scope values for filters registered with Sling.

As we are in the process of extending the potential values (and also
supporting multiple values) - in the current trunk and not yet released
- I wonder whether Sling should not provide an Enum of the possible
values and the scr-annotations should really refer to that enum.



On 15.10.2010 21:55, Justin Edelson (JIRA) wrote:
> getting error about SlingFilterScope not being applicable for <T extends Enum>
> ------------------------------------------------------------------------------
>                  Key: FELIX-2665
>                  URL: https://issues.apache.org/jira/browse/FELIX-2665
>              Project: Felix
>           Issue Type: Bug
>           Components: Maven SCR Plugin
>             Reporter: Justin Edelson
>          Attachments: FELIX-2665.patch
> with a current trunk (r1022936) build of scr annotations (1.3.1-SNAPSHOT) and scr plugin
(1.4.5-SNAPSHOT), building Sling errors out with an error about how SlingFilterScope isn't
applicable for <T extends Enum>. Sorry - I accidentially closed the window where I'd
pasted the error message, will add it in a comment later.

View raw message