Review scope for dependencies in pom

Please review the scopes for dependencies in the poms. My project is inheriting some dependencies that I would not expect after declaring a RestEasy dependency. For example:

1. javax.servlet:servlet-api is provided by the Servlet container. As a result, the scope should be "provided".

2. I would think that you could get away with a provided scope for javax.annotation:jsr250-api and javax.activation:activation too since the container also provides this.

3. junit has a provided scope, but that is odd for a test framework. I would expect this to have a test scope.

4. For SLF4J, the org.slf4j:slf4j-api dependency should remain, but the org.slf4j:slf4j-simple dependency should be either removed, or declared with a test scope. (It is probably necessary for the unit tests to run.) As a rule, it should be the responsibility of the application to determine the SLF4J implementation (jdk, simple, log4j, logback, etc.), not a library dependency.

This should be low hanging fruit, and it would be great to see this included in the 1.0 release.