Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 63763B185 for ; Fri, 20 Jan 2012 16:53:29 +0000 (UTC) Received: (qmail 16624 invoked by uid 500); 20 Jan 2012 16:53:26 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 16536 invoked by uid 500); 20 Jan 2012 16:53:26 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 16528 invoked by uid 99); 20 Jan 2012 16:53:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2012 16:53:25 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mwalsh@chartwelltechnology.com designates 216.82.254.51 as permitted sender) Received: from [216.82.254.51] (HELO mail144.messagelabs.com) (216.82.254.51) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 20 Jan 2012 16:53:18 +0000 X-Env-Sender: mwalsh@chartwelltechnology.com X-Msg-Ref: server-3.tower-144.messagelabs.com!1327078311!81779256!1 X-Originating-IP: [64.141.41.132] X-StarScan-Version: 6.4.3; banners=chartwelltechnology.com,-,- X-VirusChecked: Checked Received: (qmail 6055 invoked from network); 20 Jan 2012 16:51:51 -0000 Received: from mail.chartwelltechnology.com (HELO mail.chartwelltechnology.com) (64.141.41.132) by server-3.tower-144.messagelabs.com with SMTP; 20 Jan 2012 16:51:51 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Difference between compile and provided scope for jar artifacts Date: Fri, 20 Jan 2012 09:52:54 -0700 Message-ID: <8F850C918DCDBF4891A6C99A6B7668330739B4BF@cacgex01.calgary.chartwelltechnology.com> In-Reply-To: <440D69AA5A6A81428BD620AEA5AC918118A38FBC54@MX33A.corp.emc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Difference between compile and provided scope for jar artifacts Thread-Index: AczXkrMBraq9HJSDTyCXct3dthuXVwAAKSrQ References: <440D69AA5A6A81428BD620AEA5AC918118A38FBC54@MX33A.corp.emc.com> From: "Matt Walsh" To: "Maven Users List" X-Virus-Checked: Checked by ClamAV on apache.org Makes more sense in terms of a WAR. Compile scope jars are copied to WEB-INF/lib. Provided scope jars aren't. For example, the servlet-api would be "provided" by the servlet container. Matt > -----Original Message----- > From: Chad.Davis@emc.com [mailto:Chad.Davis@emc.com] > Sent: Friday, January 20, 2012 9:45 AM > To: users@maven.apache.org > Subject: Difference between compile and provided scope for jar > artifacts >=20 > 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 missing something? ______________________________________________________________________ This message, including any attachments, is confidential and contains info= rmation intended only for the person(s) named above. Any other distributio= n, copying or disclosure is strictly prohibited. If you are not the intend= ed recipient or have received this message in error, please notify us imme= diately by reply email and permanently delete the original transmission fr= om all of your systems and hard drives, including any attachments, without= making a copy. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org