Thanks Jörg, It makes sense. How about for "compile" scope? What is the best practices to deploy them into runtime along with application code? Thanks.
regards, Lin On Mon, Apr 6, 2015 at 6:09 PM, Jörg Schaible <[email protected]> wrote: > Lin Ma wrote: > > > Hi Maven expert, > > > > I think Maven is good for build, and not sure if cover runtime deployment > > well. Wondering what is the best practices for deploy "provided" scope > > jars? > > > > Currently, I either build a fat jar, or manual copy external dependencies > > jars into class path. > > > > And better solutions is appreciated. > > Don't declare them as "provided". > > See, "provided" means, such a dependency is already present in the target > environment of the application. E.g. a web application can assume that the > application server provides servlet-api if it is compliant with the > specification. > > Otherwise, "provided" is simply wrong. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
