Hello, no (IMHO) you are on the right track. Consider that one of the benefits deploying on a javaee app server, is that you already have a set of libraries bundled on your runtime. You dont have to 'increase' the size of your app, by bundling more or less the same libs or slightly different.
It would be wise, to spend some time and check the versions. For JBoss/ Wildfly for example you can check under the /modules folder and see the specific versions of prebundled libraries. For standard (javaEE spec) stuff, it is easier and cleaner to add single dependency towards the API like this one http://mvnrepository.com/artifact/javax/javaee-api/7.0 . For extra libraries that might already bundled by the app server, for example Wildfly/Jboss has already a module for Google Guava (version 1.6.) there is no need IMHO to add the same jar on your war/ear. So, yes it is worth spending some time and fixing the dependencies. It wont take too long I suppose. You can derive the versions of the libs from pages related to the specific version, on Jboss web sites. Keep the provided way. -- View this message in context: http://maven.40175.n5.nabble.com/Using-scope-provided-tp5838808p5839030.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
