Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of eljotpl@gmail.com designates
 66.249.82.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=FFc63iImU5l/i4uslrGHXy6Uwl7jmU5DUpZJTtYeZEOCKATMtGvVxGNSRo+RIJSHXUbnAs2wcn8RY66loIeVdqFuAI18EER1cx5vXzrCYLhjkzqLcVBitVEyVAypBudzgb8mJMKDqk4gNMWcKDAUTDhz6sKsi+Sg8Y1OC6wg+FQ=
Message-ID: <1b5bfeb50602270150u329a0e21u@mail.gmail.com>
Date: Mon, 27 Feb 2006 10:50:41 +0100
From: "Jacek Laskowski" <eljotpl@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: Need exception to be chained in deployment commands
In-Reply-To: <c278ac970602270142w3cc554d9qa9d81a7bcfb537d3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <c278ac970602270142w3cc554d9qa9d81a7bcfb537d3@mail.gmail.com>

2006/2/27, Prasad Kashyap <goyathlay.geronimo@gmail.com>:
> In the directory,
> geronimo\modules\deploy-jsr88\src\java\org\apache\geronimo\deployment\plu=
gin\local\
>
> StartCommand.run()
> CommandSupport.doFail()
>
> both trap exceptions and print out their stacktraces. Since the
> exception doesn't bubble up, I'm unable to use them in a mojo.

Well, I won't help you much, but what about creating a JIRA issue so
that it won't slip our attention? Others would surely benefit from it,
too as the task is easier to follow.

> I didn't want to mess with these files without talking to it's
> creator/custodian.

Why not? It's an open source project and anybody can step up and
change whatever they think is appropriate. The issue is whether or not
it's committed, but that's another story ;)

> Would they please advise how they want me to handle this ? I'd also
> like to channel their output to the printstream of my choice for
> logging purposes.

I think you can do it with commons-logging we're using very easily.
So, provided the exception is logged, you can route it to whatever
output stream you wish.

> Prasad

Jacek

--
Jacek Laskowski
http://www.laskowski.org.pl