When I build a jar file, the compile dependencies are not packaged into the
jar. So, this means that they are expected to be provided somewhere else in
the run time environment, doesn't it? Which means that it doesn't seem like
there's a difference between compile and provided . . . am I
, 2012 9:45 AM
To: users@maven.apache.org
Subject: Difference between compile and provided scope for jar
artifacts
When I build a jar file, the compile dependencies are not packaged
into
the jar. So, this means that they are expected to be provided
somewhere else in the run time environment
Am 20.01.2012 17:44 schrieb chad.da...@emc.com:
When I build a jar file, the compile dependencies are not packaged into
the jar. So, this means that they are expected to be provided somewhere
else in the run time environment, doesn't it? Which means that it doesn't
seem like there's a
[mailto:ansgar.konerm...@googlemail.com]
Sent: Friday, January 20, 2012 9:57 AM
To: Maven Users List
Subject: Re: Difference between compile and provided scope for jar
artifacts
Am 20.01.2012 17:44 schrieb chad.da...@emc.com:
When I build a jar file, the compile dependencies are not packaged
20, 2012 9:57 AM
To: Maven Users List
Subject: Re: Difference between compile and provided scope for jar
artifacts
Am 20.01.2012 17:44 schrieb chad.da...@emc.com:
When I build a jar file, the compile dependencies are not packaged
into
the jar. So, this means
If you want to include all dependencies into jar, you can use maven
assembly plugin. You can integrate it to build process, see:
http://stackoverflow.com/a/589111/121143
I have done this for creating full-blown jar with test which can be
easily uploaded to Amazon micro instance for load
