Ah - I'd missed that! I just added that now, so at least this issue is
avoided for jersey-scala - thanks!
> I liked your solution, we discussed a while ago, for a single
> META-INF/services file that contains a list of classes.
>
> Strictly speaking it is not necessary to have a META-INF/services file
> specific to the interface of what is being implemented. It is sort of a
> hangover from how things were initially implemented.
I wonder if we had something like a text file containing package names called
META-INF/services/jersey-packages
which Jersey could then load all of them it can see on the classpath
and use them to search through for resource beans & entity providers
and whatnot?
Then in effect the packages listed in each
META-INF/services/jersey-packages file are concatenated with whatever
the user configures in the com.sun.jersey.config.property.packages
property?