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 007E9DDDD for ; Tue, 12 Mar 2013 07:25:44 +0000 (UTC) Received: (qmail 159 invoked by uid 500); 12 Mar 2013 07:25:41 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 99693 invoked by uid 500); 12 Mar 2013 07:25:40 -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 99660 invoked by uid 99); 12 Mar 2013 07:25:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 07:25:39 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of apachemaven0@gmail.com designates 74.125.83.44 as permitted sender) Received: from [74.125.83.44] (HELO mail-ee0-f44.google.com) (74.125.83.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2013 07:25:32 +0000 Received: by mail-ee0-f44.google.com with SMTP id l10so2631528eei.31 for ; Tue, 12 Mar 2013 00:25:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=0ZmuDKEtqLH0Clf5RXcooP6HSN+Nxg19rgeQYp1zR4E=; b=u16mGYPvmI/sSewtwM4J9Sm8pM8QovPgqN0XZ7tbNTycV/5mIj+cGNW0zThSuJTBRB p/3dQy+2TTOYmx0C5/G9BazPrluL7Z9HUhWdu7Z21pDRSBCNv/zq27AEARVNs8M48Pu3 /ISCBMQpY8JkjhbG4KSAhJhJAWmGOOyJLvS8mIWDfNR57l9nUMFOih6nEU94ePy+Sp5A GEegFOU+5D6wmDJ6O7cD0aQAm3qM2SklpwDIT6N8OMjtILExGDhLrkzyKR8sKNfCWemk YPCJTCNBcMyJ0zQQgarFuMOZ3S1/CLPqB0EuK9/Y1AOxdLs88751jyZ9G9F8g3ih41eA 2dFQ== X-Received: by 10.14.173.67 with SMTP id u43mr45200026eel.22.1363073112513; Tue, 12 Mar 2013 00:25:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.15.21.74 with HTTP; Tue, 12 Mar 2013 00:24:32 -0700 (PDT) From: maven apache Date: Tue, 12 Mar 2013 15:24:32 +0800 Message-ID: Subject: effective practice for web application development using maven To: users@maven.apache.org Content-Type: multipart/alternative; boundary=047d7b621fbaaccf2e04d7b53037 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b621fbaaccf2e04d7b53037 Content-Type: text/plain; charset=ISO-8859-1 Hi everyone: I am using maven3 as my J2EE application build tool. Now I meet some problem during my development --- I found it is so inflexible to do the test or debug in the multiple modules. For example, I have a parent maven project whose pom.xml is like this: app-common app-webapp And the app-common/pom.xml: jar the app-webapp/pom.xml: war ${project.groupId} app-common ${project.version} app org.mortbay.jetty maven-jetty-plugin 10 foo 9999 Now,the app-common project hold all the classed for the whole application,and the app-webapp is responsible for the presentation. As you can see I use the jetty to set up the web application. However, each time I make some change inside the project app-common, the jetty can not detect it which means that I have to run the "mvn install" under the parent project,and restart the jetty to see the update. This is too inflexible. So I wonder how do you guys do this kind of development? --047d7b621fbaaccf2e04d7b53037--