Hmm, thanks, Robert.
The Sun docs' example makes a better case for their way of doing it than the
Apache example does. In particular "Implementation-Version" boils down to
basically a build number which is not clearly shown in the Apache example.
Of course we don't use these in Commons-net an
On 22 Jan 2004, at 06:07, Steve Cohen wrote:
I see.
After looking further into this matter, I begin to doubt the
correctness of
the http://jakarta.apache.org/commons/releases/prepare.html
instructions.
hi steve
IIRC this point has been talked about at a little length in the past. i
see to re
I see.
After looking further into this matter, I begin to doubt the correctness of
the http://jakarta.apache.org/commons/releases/prepare.html
instructions. They recommend this line in the manifest
Implementation-Title: "org.apache.commons.foo"
The existing maven system produces
Package: "or
I used what maven put in there.
> On Wed, 21 Jan 2004 14:29:04 -0600, Steve Cohen <[EMAIL PROTECTED]> said:
> I am now working on preparing release 1.1.1 of jakarta-commons/net
> and I have come to the point of working on the jar manifest as
> detailed in:
> http://jakarta.apache.org/common
I am now working on preparing release 1.1.1 of jakarta-commons/net and I have
come to the point of working on the jar manifest as detailed in:
http://jakarta.apache.org/commons/releases/prepare.html
What we now have in the jar manifest does not fit this pattern, and I am
wondering where the cur
