Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates
 66.249.82.231 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=GpGseueJybHgBnc4CFVJkgtKiBxgdS8VXJIfJUl/CO2oGE1Q9SGJjqQrtyE6XdX0hWp0C2sjFgBWH/wtEkLJhOTdhlrw68F+IDJeAmCR76ssBkia5Lbc12S4ygBk2HesFdaa4i2sjifQyKUk0QcaM6/kFu5xiaBOuHGEunEVMOk=
Message-ID: <74e15baa0609130430k2c0783f3i6a869de9e87fc943@mail.gmail.com>
Date: Wed, 13 Sep 2006 07:30:47 -0400
From: "Aaron Mulder" <ammulder@alumni.princeton.edu>
Sender: ammulder@gmail.com
To: dev@geronimo.apache.org
Subject: Re: How to get predictable moduleId when using
 DeploymentManager.distribute()
In-Reply-To: <AB4A1384-4C59-410F-86E7-EC04EA994AC8@planet57.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <AB4A1384-4C59-410F-86E7-EC04EA994AC8@planet57.com>

First, if you specify a module ID in your plan, that will be used (or
as much as you provide with defaults for the rest).  And you can pack
the plan in the module if you don't want to track it separately.

Second, you can undeploy using only the artifact ID (so in your
example, you could "undeploy test-ear-j2ee_1.4-1.2-SNAPSHOT") so long
as there aren't conflicts.  The default artifact ID is the JAR name
minus the extension.

Thanks,
     Aaron

On 9/13/06, Jason Dillon <jason@planet57.com> wrote:
> Anyone know how to get predictable moduleIds when using
> DeploymentManager.distribute()?
>
> I'd like to figure out how to get the moduleIds to be the same as the
> artifactId for the archive that is deployed, so that we can undeploy
> it after tests have been run.
>
> How can I do this?  Do I need to specify a plan for the archive to
> tie it to a specific moduleId?
>
> I have been playing with test-ear-j2ee_1.4.ear, and it keeps
> generating stuff like 'default/test-ear-j2ee_1.4-1.2-SNAPSHOT/
> 1158129807807/car' which is kinda hard to undeploy after that state
> has been lost.
>
> If I do need to specify a plan, can I tuck that into the .ear so that
> Maven does not need to worry about 2 artifacts for one deployment?
>
> --jason
>