Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of ted.husted@gmail.com
 designates 209.85.146.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        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=Iu1GbOwzSlGqi/yfMSoTMh+pdY2GBvkX/7kue2xm8kSJcUTJ7kUjvn/Zzs4jkySAboNU9a9b+rbEOewUR+GkOcJ1f/Mf76t6kLF3A77LXbgABbfKa2ZBbP8XahGPsfb+dbbvW7W5iCxMXir6evHr4snUtsXgoBElu/6rmbb7eTo=
Message-ID: <8b3ce3790709111757w6c244f24q493b8d75a117abf4@mail.gmail.com>
Date: Tue, 11 Sep 2007 20:57:53 -0400
From: "Ted Husted" <husted@apache.org>
Sender: ted.husted@gmail.com
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: Hold 2.0.10
In-Reply-To: <aae96ca0709110057w43e98bd6vce805d85e346dd5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46CE56D9.5090500@fdar.com>
	 <d8bdeb6f0708241020t417b3385pc2983c607e17bcb7@mail.gmail.com>
	 <d8bdeb6f0708241652y6848b57dld435950121a22f12@mail.gmail.com>
	 <aae96ca0708290144k5fa2f568j37e0d580d452cfc5@mail.gmail.com>
	 <d8bdeb6f0708290607j10ef23eam92debbfd65700a4a@mail.gmail.com>
	 <8b3ce3790709051342u1247e01ej3578f03cc2e0f69a@mail.gmail.com>
	 <8b3ce3790709100633v5aa3814fv6c2cdbf29ec748f3@mail.gmail.com>
	 <aae96ca0709100751q56c62251j8eaf6b8f2d07ce6e@mail.gmail.com>
	 <8b3ce3790709101729y4490124x9932d3e523bc844a@mail.gmail.com>
	 <aae96ca0709110057w43e98bd6vce805d85e346dd5@mail.gmail.com>

On 9/11/07, Antonio Petrelli <antonio.petrelli@gmail.com> wrote:
> I don't know if it is useful, but it seems that the parameter is "
> gpg.passphrase" and not "passphrase".

I appreciate the suggestion, but that didn't work either. I'm sure the
plugin will work out fine, it's just that my system is whacked when it
comes to gpg.

I tried to move forward by switching my working copy to the
"struts2-parent-2.0.10" tag, to get the updated POMs. At first it
failed because the assembly/pom.xml still referred to the
2.0.10-SNAPSHOT. Then, it failed because it couldn't fnd the
struts2-portlet.war.

Looking in the portlet application POM, we've set the artifact name
to "struts2-portlet-branch" in the 2_0_X branch. Is that intentional?

Anyway, I'll plan on deleting the 2.0.10 tag tormorrow and trying
again the old-fashioned way.

I am glad that we are working on getting the release plugin in place,
since I'm sure it will help in the long run.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org