1) For every dependency on <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.0_spec</artifactId> </dependency> change it into <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.0_spec</artifactId> <scope>provided</scope> </dependency> Note: not in the parent pom: the parent pom never declares <scope> 2) For every dependency on <dependency> <groupId>org.jboss.spec.javax.servlet.jsp</groupId> <artifactId>jboss-jsp-api_2.2_spec</artifactId> </dependency> change it into <dependency> <groupId>org.jboss.spec.javax.servlet.jsp</groupId> <artifactId>jboss-jsp-api_2.2_spec</artifactId> <scope>provided</scope> </dependency> 3) In dashboard builder (and potentially other projects), there are several modules with java imports of servlet/jsp stuff but don't have a direct dependency to it (instead they rely on it through a transitive dependencies - which is against maven conventions). Add a direct provided dependency on servlet and/or jsp for those to avoid compile errors. 4) The generic wars will no longer contain the servlet/jsp API's (that's a good thing). So it will be no longer needed to these exclude them in assembly-*.xml's. Remove this from those assembly xml files: <exclude>WEB-INF/lib/servlet-api-*.jar</exclude> <exclude>WEB-INF/lib/jboss-servlet-api_*.jar</exclude> <exclude>WEB-INF/lib/jsp-api-*.jar</exclude> <exclude>WEB-INF/lib/jboss-jsp-api_*.jar</exclude>
Note: as part of https://bugzilla.redhat.com/show_bug.cgi?id=999072 all javax.servlet:servlet-api dependencies were replaced with org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec dependencies.
Verified in BPMS 6.0.0.ER4 ... the dependencies aren't in WEB-INF/lib any more.