Jackson dependency in maven and developing in eclipse with JBoss EAP 6.3/6.4
<p>I'm using eclipse and developing some services with resteasy with jackson as json provider:</p>

<pre><code>    &lt;dependency&gt;
        &lt;groupId&gt;org.jboss.resteasy&lt;/groupId&gt;
        &lt;artifactId&gt;resteasy-jaxrs&lt;/artifactId&gt;
        &lt;version&gt;2.3.10.Final&lt;/version&gt;
        &lt;scope&gt;provided&lt;/scope&gt;
    &lt;/dependency&gt;

    &lt;dependency&gt;
        &lt;groupId&gt;org.jboss.resteasy&lt;/groupId&gt;
        &lt;artifactId&gt;resteasy-jackson-provider&lt;/artifactId&gt;
        &lt;version&gt;2.3.10.Final&lt;/version&gt;
        &lt;scope&gt;provided&lt;/scope&gt;
    &lt;/dependency&gt;
</code></pre>

<p>Those libs are actually supplied to the build path via <code>JBoss EAP 6.1+ runtime</code>. But I've to set some jackson specific options via a custom <code>ObjectMapper</code>. For this I added another dependency on jackson:</p>

<pre><code>    &lt;dependency&gt;
        &lt;artifactId&gt;jackson-mapper-asl&lt;/artifactId&gt;
        &lt;groupId&gt;org.codehaus.jackson&lt;/groupId&gt;
        &lt;version&gt;1.9.9&lt;/version&gt;
        &lt;scope&gt;provided&lt;/scope&gt;
    &lt;/dependency&gt;
</code></pre>

<p>Now this breaks my eclipse build because the server runtime only includes ee libs. Of course I can change the scope but that results in the artifact being included in the final war even if it's already packaged as a jboss module.</p>