You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/12/05 18:41:43 UTC
FW: Enforcing use of mirrors for jakarta
Are other Committers subscribed to infrastructure@?
In any event, this appears to be a direction that the ASF would like us to
go. Should we take a look at it right after we've put out v2.1? Not that
we are much of a resource drain. :-)
--- Noel
-----Original Message-----
From: Justin Erenkrantz [mailto:jerenkrantz@apache.org]
Sent: Thursday, December 05, 2002 1:36
To: pmc@jakarta.apache.org
Cc: infrastructure@apache.org
Subject: Enforcing use of mirrors for jakarta
Hello Jakarta PMC,
As you may or may not be aware, there is an effort ongoing within the
ASF to increase the use of our mirrors for downloads. I believe
people have previously asked the Jakarta PMC for assistance, but, at
the time, the ASF did not have a set of guidelines for projects to
follow.
Now the infrastructure@ mailing list has come up with a set of
guidelines that can be used by projects. While it is not set in
stone, it should be enough to provide a guide for migrating Jakarta
projects over.
Please see:
http://www.apache.org/dev/mirrors.html
What assistance would you need from us (infrastructure-oriented
people) to get each Jakarta project to transition over to this? Note
that Ant has already begun the transition.
The highest priority should be getting Tomcat 4.0 releases mirrored.
Currently (according to Vadim's graphs[1]), ~25% of the HTTP traffic
is Tomcat 4.0 downloads. We'd need to move over all tomcat-4.0
downloads under the /dist/jakarta/... directories and start to use a
mirror-oriented download page. I'm not familiar who to work with on
the Tomcat team and would appreciate any assistance you can offer.
Thanks in advance! -- justin
[1] http://www.apache.org/~vgritsenko/stats/index.html
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: javamail 1.3.0
Posted by "Noel J. Bergman" <no...@devtech.com>.
Serge,
Thanks for that info. I don't believe that it will impact existing code, so
we'll stick with the release plan unchanged. As soon as we're shipped, we
can replace the javamail jar in the CVS, if you are representing that you
have tested it (we'll do so again, anyway, of course).
--- Noel
-----Original Message-----
From: Serge Sozonoff [mailto:serge@globalbeach.com]
Sent: Thursday, December 05, 2002 16:25
To: James Developers List
Subject: Re: javamail 1.3.0
Hi Noel,
> We're all tested and ready to go. I would put this off until after the
> release, then we can drop it in, re-test, and make it part of the next
> milestone build for people who need it.
I understand and agree here. IMHO We just need to make sure that javamail
1.3.0 makes it into the next release.
> What is the nature of the bug? Is there a workaround? Does it effect
> normal users with the current set of mailets?
Possibly my current problem is related to this bug which was fixed in 1.3.0:
- tolerate trailing semicolon in Content-Type header (requires JAF
1.0.2)
I am getting an error message like this when calling multipart.getCount() :
javax.mail.MessagingException: EOF skipping headers
My solution was to build JAMES 2.1a1cvs replacing javamail 1.2.0 with
javamail 1.3.0 in the build process
I don't know if it effects normal users with the current set of mailets
since I am not familiar with all of the
current mailets. My guess would be that is does not.
Thanks,
Serge
----- Original Message -----
From: "Noel J. Bergman" <no...@devtech.com>
To: "James Developers List" <ja...@jakarta.apache.org>
Sent: Thursday, December 05, 2002 9:24 PM
Subject: RE: javamail 1.3.0
> Serge,
>
> We're all tested and ready to go. I would put this off until after the
> release, then we can drop it in, re-test, and make it part of the next
> milestone build for people who need it.
>
> What is the nature of the bug? Is there a workaround? Does it effect
> normal users with the current set of mailets?
>
> --- Neol
>
> -----Original Message-----
> From: Serge Sozonoff [mailto:serge@globalbeach.com]
> Sent: Thursday, December 05, 2002 13:49
> To: James Developers List
> Subject: javamail 1.3.0
>
>
> Hi All,
>
> I brought this up a while ago and just thought I would mention it again as
a
> little reminder...
> I just ran into another javamail 1.2.0 bug when coding one of my mailets,
we
> really should upgrade to javamail 1.3.0.
>
> I guess this will have to wait till the next release.....?
>
> Serge
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: javamail 1.3.0
Posted by Serge Sozonoff <se...@globalbeach.com>.
Hi Noel,
> We're all tested and ready to go. I would put this off until after the
> release, then we can drop it in, re-test, and make it part of the next
> milestone build for people who need it.
I understand and agree here. IMHO We just need to make sure that javamail
1.3.0 makes it into the next release.
> What is the nature of the bug? Is there a workaround? Does it effect
> normal users with the current set of mailets?
Possibly my current problem is related to this bug which was fixed in 1.3.0:
- tolerate trailing semicolon in Content-Type header (requires JAF
1.0.2)
I am getting an error message like this when calling multipart.getCount() :
javax.mail.MessagingException: EOF skipping headers
My solution was to build JAMES 2.1a1cvs replacing javamail 1.2.0 with
javamail 1.3.0 in the build process
I don't know if it effects normal users with the current set of mailets
since I am not familiar with all of the
current mailets. My guess would be that is does not.
Thanks,
Serge
----- Original Message -----
From: "Noel J. Bergman" <no...@devtech.com>
To: "James Developers List" <ja...@jakarta.apache.org>
Sent: Thursday, December 05, 2002 9:24 PM
Subject: RE: javamail 1.3.0
> Serge,
>
> We're all tested and ready to go. I would put this off until after the
> release, then we can drop it in, re-test, and make it part of the next
> milestone build for people who need it.
>
> What is the nature of the bug? Is there a workaround? Does it effect
> normal users with the current set of mailets?
>
> --- Neol
>
> -----Original Message-----
> From: Serge Sozonoff [mailto:serge@globalbeach.com]
> Sent: Thursday, December 05, 2002 13:49
> To: James Developers List
> Subject: javamail 1.3.0
>
>
> Hi All,
>
> I brought this up a while ago and just thought I would mention it again as
a
> little reminder...
> I just ran into another javamail 1.2.0 bug when coding one of my mailets,
we
> really should upgrade to javamail 1.3.0.
>
> I guess this will have to wait till the next release.....?
>
> Serge
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: javamail 1.3.0
Posted by "Noel J. Bergman" <no...@devtech.com>.
Serge,
We're all tested and ready to go. I would put this off until after the
release, then we can drop it in, re-test, and make it part of the next
milestone build for people who need it.
What is the nature of the bug? Is there a workaround? Does it effect
normal users with the current set of mailets?
--- Neol
-----Original Message-----
From: Serge Sozonoff [mailto:serge@globalbeach.com]
Sent: Thursday, December 05, 2002 13:49
To: James Developers List
Subject: javamail 1.3.0
Hi All,
I brought this up a while ago and just thought I would mention it again as a
little reminder...
I just ran into another javamail 1.2.0 bug when coding one of my mailets, we
really should upgrade to javamail 1.3.0.
I guess this will have to wait till the next release.....?
Serge
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
javamail 1.3.0
Posted by Serge Sozonoff <se...@globalbeach.com>.
Hi All,
I brought this up a while ago and just thought I would mention it again as a
little reminder...
I just ran into another javamail 1.2.0 bug when coding one of my mailets, we
really should upgrade to javamail 1.3.0.
I guess this will have to wait till the next release.....?
Serge
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>