java - Jackson dependency in maven and developing in eclipse with JBoss EAP 6.3/6.4 -
i'm using eclipse , developing services resteasy jackson json provider:
<dependency> <groupid>org.jboss.resteasy</groupid> <artifactid>resteasy-jaxrs</artifactid> <version>2.3.10.final</version> <scope>provided</scope> </dependency> <dependency> <groupid>org.jboss.resteasy</groupid> <artifactid>resteasy-jackson-provider</artifactid> <version>2.3.10.final</version> <scope>provided</scope> </dependency>
those libs supplied build path via jboss eap 6.1+ runtime
. i've set jackson specific options via custom objectmapper
. added dependency on jackson:
<dependency> <artifactid>jackson-mapper-asl</artifactid> <groupid>org.codehaus.jackson</groupid> <version>1.9.9</version> <scope>provided</scope> </dependency>
now breaks eclipse build because server runtime includes ee libs. of course can change scope results in artifact being included in final war if it's packaged jboss module.
updating jboss tools 4.3 , adding src/main/webapp/web-inf/jboss-deployment-structure.xml
did trick:
<jboss-deployment-structure> <deployment> <dependencies> <module name="org.jboss.resteasy.resteasy-jackson-provider" export="true" /> <module name="org.codehaus.jackson.jackson-core-asl" export="true" /> <module name="org.codehaus.jackson.jackson-mapper-asl" export="true" /> </dependencies> </deployment> </jboss-deployment-structure>
Comments
Post a Comment