<name>Java.net Promoted Repositories</name>
for a web application, we end up with non desired and/or obsolete dependencies in the resulting WEB-INF/lib area with:
1- jersey-client 2.0 ? Why I want a server!
2-asm-all-repackaged-2.1.88: why? First this is the old ASM 3.x non compatible with Java 7, then it is NOT repackaged at all, so any Web App cannot use ASM4.x and Jersey 2.0 together...This would be a blocker for Java 7 support, and not being repackaged is very serious
3- osgi-resource-locator: Why OSGI in a pure JAX-RS simple App?
4 javax.inject-2.1.88 : what is this 2.1.88 version? Is it ancient? Modern? Why tight to hk2?
5 guava-14.0.1.jar: what will happen if/when there is guava15 and my Web App Needs to depend on it, but Jersey is not upgraded?
A Maven nightmare.
Key ones are: ASM not being 4.1 so not being Java 7 compatible (stack map frame processing for bytecode 51) and Guava should be repackaged to be a private implementation.
Look at the jarjar tools that does that.
Hint: You can use the NetBeans Maven graph viewer on a very simple pom have my 2 entries and you'll see the