I think we could make this optional. If meta data providers were pluggable (e.g. using java.util.ServiceLoader), the engine would just use those providers available. And only if the Jandex provider is around it would be used (and that module would have a dependency to the Jandex lib).

-1 or at least not a big fan of this. then we have to deal with two ways of processing annotations

I think it would only be worth if we could reuse the existing index from the container. In that case it should help performance-wise.

Performance is of course one reason. We don't have to rely on the container index either. In standalone mode we could safe the index ourselves and reload it. Performance is of course one thing, but I also like the API of Jandex and the clear separation of annotation discovery and annotation processing. Obviously we already have a good abstraction from the meta data source via MetaDataProvider.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira