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 4D5DE7F7D for ; Tue, 6 Sep 2011 19:19:05 +0000 (UTC) Received: (qmail 1116 invoked by uid 500); 6 Sep 2011 19:19:02 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 1004 invoked by uid 500); 6 Sep 2011 19:19:02 -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 992 invoked by uid 99); 6 Sep 2011 19:19:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2011 19:19:01 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of delali.dzirasa@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2011 19:18:55 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R11AI-00037Q-Dx for users@maven.apache.org; Tue, 06 Sep 2011 12:18:34 -0700 Date: Tue, 6 Sep 2011 12:18:34 -0700 (PDT) From: dizzyd To: users@maven.apache.org Message-ID: <1315336714419-4775657.post@n5.nabble.com> In-Reply-To: <6B971D57-AA52-40E6-945A-228897C34F09@maven.org> References: <1315317547302-4774500.post@n5.nabble.com> <6B971D57-AA52-40E6-945A-228897C34F09@maven.org> Subject: Re: Maven Jetty Plugin won't honor webAppSourceDirectory MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org A follow up. We have a very large and complex system that is being deployed to jetty 6.1.22, so I'd like to try to keep things a close to the same as possible with the plugin. One issue I am running into is that, the config isn't being honored for: > > org.mortbay.jetty > maven-jetty-plugin > 6.1.22 > > > ${basedir}/src/main/webapp2 > ${basedir}/src/main/webapp2/WEB-INF/web.xml > > when I do a mvn: jetty:run looks like it is looking for the newest version of the plugin and defaulting to the "jetty-maven-plugin" (the newest one) and skipping this configuration all together. I think this has something to do with my plugin groups declaration in my settings.xml file: ... org.mortbay.jetty ... to get it to actually use the 6.1.22 version I have to use the fully qualified plugin name as such: mvn org.mortbay.jetty:maven-jetty-plugin:run This uses the correct version of the plugin, but why? What setting is telling maven to use the newer one when I call jetty:run? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Jetty-Plugin-won-t-honor-webAppSourceDirectory-tp4774500p4775657.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