I agree with you, I'd rather avoid black-listing jar from their names.
I was actually thinking about reducing the search scope to the project sources only (assuming that the JAX-RS API annotations are present is the classpath).
Or at least, provide a property for the plugin to limit the search scope or include the whole classpath.
I'm actually not sure that most of the users have custom JAX-RS resources/providers in jars anyway.
Pete: any thought about this ?
Max,
I agree with you, I'd rather avoid black-listing jar from their names.
I was actually thinking about reducing the search scope to the project sources only (assuming that the JAX-RS API annotations are present is the classpath).
Or at least, provide a property for the plugin to limit the search scope or include the whole classpath.
I'm actually not sure that most of the users have custom JAX-RS resources/providers in jars anyway.
Pete: any thought about this ?
Thanks
Xavier