Return-Path: 
 <user-return-5483-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-user-archive@www.apache.org
Received: (qmail 63639 invoked from network); 21 Dec 2006 22:58:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 21 Dec 2006 22:58:31 -0000
Received: (qmail 56749 invoked by uid 500); 21 Dec 2006 22:58:35 -0000
Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org
Received: (qmail 56674 invoked by uid 500); 21 Dec 2006 22:58:34 -0000
Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@geronimo.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@geronimo.apache.org>
List-Post: <mailto:user@geronimo.apache.org>
Reply-To: user@geronimo.apache.org
List-Id: <user.geronimo.apache.org>
Delivered-To: mailing list user@geronimo.apache.org
Received: (qmail 56644 invoked by uid 99); 21 Dec 2006 22:58:34 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Dec 2006 14:58:34 -0800
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of daniel.ramagem@gmail.com
 designates 209.85.132.248 as permitted sender)
Received: from [209.85.132.248] (HELO an-out-0708.google.com) (209.85.132.248)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Dec 2006 14:58:24 -0800
Received: by an-out-0708.google.com with SMTP id b38so764338ana
        for <user@geronimo.apache.org>; Thu, 21 Dec 2006 14:58:03 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=oLmlkOTbcyRzK9Tj76/mAjSEsA6Ls5iSNe/fnP3/bnLNqSEwq8c5VSBnnVpXT1Y9M9rN59btrBY7M0whGKLwsd4GcCxrT+PPe3kVcrSG8whpRQyLZuLv0McQXCcP7Fz/hHlhx6HFNUSGiA8+9hmtJaKZ8/7JHEq2HsZeWbX00dM=
Received: by 10.100.152.9 with SMTP id z9mr7151431and.1166741883802;
        Thu, 21 Dec 2006 14:58:03 -0800 (PST)
Received: by 10.100.95.8 with HTTP; Thu, 21 Dec 2006 14:58:03 -0800 (PST)
Message-ID: <584f6cce0612211458r5cab4a03y5c987b71c71e5f4a@mail.gmail.com>
Date: Thu, 21 Dec 2006 17:58:03 -0500
From: "Daniel Bloomfield Ramagem" <daniel.ramagem@gmail.com>
To: user@geronimo.apache.org
Subject: Specifying SNAPSHOT Versions of Modules
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4346_5407454.1166741883727"
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_4346_5407454.1166741883727
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've got a Module A that depends on version 1.0 of Module B.  Module B is in
version 1.0 and has been deployed to the server.  Everything works fine (A
deploys fine).  But then I make a change to B and want to *keep* the
1.0version number.  I redeploy B to the server but then A is stopped
by the
deployment process. I must now manually start A back up.

I tried using the Maven SNAPSHOT tag in the "version" tag in both the
deployment plans of A and B:

Module A:
...
<dependency>
  <groupId>mygroup</groupId>
  <artifactId>moduleB</artifactId>
  <version>1.0-SNAPSHOT</version>
</dependency>
...

Module B:
...
<environment>
  <moduleId>
    <groupId>mygroup</groupId>
    <artifactId>moduleB</artifactId>
    <version>1.0-SNAPSHOT</version>
  </moduleId>
</environment>

This made no difference.  Redeploying B stops A, which needs to be manually
started again.

Any hints on how I could get A to restart automatically when the same
version (or a development version) of a dependent module is being updated?

Thanks,

Daniel.

------=_Part_4346_5407454.1166741883727
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;ve got a Module A that depends on version 1.0 of Module B.&nbsp; Module B is in version 1.0 and has been deployed to the server.&nbsp; Everything works fine (A deploys fine).&nbsp; But then I make a change to B and want to *keep* the 
1.0 version number.&nbsp; I redeploy B to the server but then A is stopped by the deployment process. I must now manually start A back up.&nbsp; <br><br>I tried using the Maven SNAPSHOT tag in the &quot;version&quot; tag in both the deployment plans of A and B:
<br><br>Module A:<br>...<br>&lt;dependency&gt;<br>&nbsp; &lt;groupId&gt;mygroup&lt;/groupId&gt;<br>&nbsp; &lt;artifactId&gt;moduleB&lt;/artifactId&gt;<br>&nbsp; &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;<br>&lt;/dependency&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
<br>...<br><br>Module B:<br>...<br>&lt;environment&gt;<br>&nbsp; &lt;moduleId&gt;<br>&nbsp;&nbsp;&nbsp; &lt;groupId&gt;mygroup&lt;/groupId&gt;<br>&nbsp;&nbsp;&nbsp; &lt;artifactId&gt;moduleB&lt;/artifactId&gt;<br>&nbsp;&nbsp;&nbsp; &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
<br>&nbsp; &lt;/moduleId&gt;<br>&lt;/environment&gt;<br><br>This made no difference.&nbsp; Redeploying B stops A, which needs to be manually started again.&nbsp; <br><br>Any hints on how I could get A to restart automatically when the same version (or a development version) of a dependent module is being updated?
<br><br>Thanks,<br><br>Daniel.<br>

------=_Part_4346_5407454.1166741883727--