On Wed, 11 Sep 2002, Scott Carlson wrote:
> Date: Wed, 11 Sep 2002 10:12:08 -0700 (PDT)
> From: Scott Carlson <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Let's include version information in Manifest (Was: Packaging
> Error)
>
> How about using attributes in the Manifest?
>
All the commons packages do this already. In particular, see the
"Implementation-Version" attribute.
Craig
>
> Date: Wed, 11 Sep 2002 11:56:45 -0400
> From: Donald Ball <[EMAIL PROTECTED]>
> Subject: Packaging error
> Content-Type: text/plain; charset="ISO-8859-1"
>
>
> On 9/11/2002 at 8:47 AM Craig R. McClanahan wrote:
>
> >Ceki,
> >
> >It was nothing wrong with Log4J -- the person who built the Struts release
> >built commons-logging.jar from scratch, but without Log4J in his build
> >environment (so the Log4J wrapper classes weren't included).
> >
> >The final Struts release will include final releases of the Commons
> >packages it relies on, and we'll verify that everything is there.
>
> On that note, could I register a small vote for including some sort of
> version information in the commons (and other) jars? I, at least, use a
> couple of other packages that rely on jakarta commons jars, and it's
> difficult to tell offhand which version is more recent. I'd suggest
> appending datestamps to the jar names if version numbers are not available:
>
> commons-digester-2002-09-11.jar
>
> - donald
>
> __________________________________________________
> Yahoo! - We Remember
> 9-11: A tribute to the more than 3,000 lives lost
> http://dir.remember.yahoo.com/tribute
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
