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 (asf.osuosl.org: domain of ted.husted@gmail.com designates
 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DB/VL8o9kz73sXhHMiANtF0dtO5sC09zYjY1I8xGn0P9X51Y4OjxlRM7H2hnCwBW7mySBLzz6NLDuMBCmbZh7H7XacPiGmmwUFcNodGogbez2STusLMpY4JRL0UVEUHgQ12UpXE6wUzte9vkwxUj+EbaOWJQZR/GPAsmNOCTZBE=
Message-ID: <8b3ce3790602171622q11d0405ej357eccfb8a81ac44@mail.gmail.com>
Date: Fri, 17 Feb 2006 19:22:27 -0500
From: "Ted Husted" <ted.husted@gmail.com>
Reply-To: husted@apache.org
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: [VOTE] Confirm the Struts Action Library 1.3.0 release plan
In-Reply-To: <16d6c6200602171530t773aa68l5d0d94bc87c5bdfc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8b3ce3790511211818p7143385aw5f6cd417ed13daf7@mail.gmail.com>
	 <8b3ce3790602161639p4043f131sd285d753d5bec7c6@mail.gmail.com>
	 <8b3ce3790602170645s38de056cp6f589372b1108e76@mail.gmail.com>
	 <adba96190602170819v526ce9a3ndc4be2aa3e8b1ce0@mail.gmail.com>
	 <A920BF57-E2B6-47CE-88E2-21911D36D884@apache.org>
	 <adba96190602170845u2d3b38c8s5495a1c0eb65afc8@mail.gmail.com>
	 <8b3ce3790602170953m7d708b17rc0fb071a20747db0@mail.gmail.com>
	 <dt5ala$8c2$1@sea.gmane.org>
	 <8b3ce3790602171513y7dd8dfafg16921e6744f9ab@mail.gmail.com>
	 <16d6c6200602171530t773aa68l5d0d94bc87c5bdfc@mail.gmail.com>

On 2/17/06, Martin Cooper <martinc@apache.org> wrote:
> Is the Struts Action Library what the Struts Classic release page on the
> wiki is about? If not, I'm now quite confused about what Struts Action
> Framework, Struts Action Library and Struts Classic are.

>From the release plan:

* Struts Classic 1.3.0 is a "bootstrap" initiative to extract  seven
new Struts subprojects from Struts 1.2.8.

* Each subproject will be available as an independant distribution

* The set of JARs created or used by all seven subprojects will be
available in one convenient ZIP archive.

* When a subproject has a new GA release, the library distribution
would be updated, and the version counter incremented.

> IMO, such a tag is going to be the only reliable way to connect the versi=
on
> number to its precise content.

Per the release plan, the Library is not going to be "versioned". The
releases underlying the JARs already have releases. We decided to give
it a counter instead.

The Library is *not* a a release. It's a set of compatible
dependencies. Many people don't need or want the full distribution.
All they want is the JARs, and so that's what the Library provides:
Just the JARs. It's really no different than the Library distribution
that we provide with 1.2 and prior.

If someone wants to setup such a tag, feel free. I don't see that it
would have any practical value.

-Ted.

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