Using scope provided

[Dishant Anand <di...@techblue.co.uk>]

Hi Community,

Just wondering , We are using jboss for deploying our application and 
recently we decided to upgrade the jboss , now most of the projects has 
defined the dependency with scope of provided .
Now with this jboss version upgrade most of the projects will require 
inspections to see which jars are no longer available in the container .

So my question is Should we pack all the jars into the war and make it 
bulky ? or should we make use of scope = > provided ?

Thanks,
Dishant anand

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Using scope provided

[javapapo <ja...@mac.com>]

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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org