Bill Barker wrote:
I mostly favor keeping the JavaMail support, since removing it (or even
making it a separate download) is likely to generate a flood of BZ reports
from people that can't be bothered to read the docs :). It has been there
since TC 4.0.0, so a lot of people are going to expect t
Costin Manolache wrote:
Yes, that's a good option if we want to keep this feature as part of
the core and not
modularize it.
I don't see any reason to ship javamail binaries.
What about having 2 distros of tomcat - a minimal container, and a
bloated one with
all the features bundled. Lazy peo
On 4/11/06, Bill Barker <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: Costin Manolache [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, April 11, 2006 9:36 AM
> > To: Tomcat Developers List
> > Subject: Re: svn commit: r392872 - /tomc
> -Original Message-
> From: Costin Manolache [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 11, 2006 9:36 AM
> To: Tomcat Developers List
> Subject: Re: svn commit: r392872 - /tomcat/tc6.0.x/trunk/build.xml
>
> On 4/11/06, Remy Maucherat <[EMAIL PROTE
On 4/11/06, Remy Maucherat <[EMAIL PROTECTED]> wrote:
> Costin Manolache wrote:
> > What about: keep them excluded in the build target for tomcat, but add a
> > separate target to build only javamail-dependent classes, and package them
> > in
> > a separate jar.
> >
> > That would keep 'core' tomc
Costin Manolache wrote:
What about: keep them excluded in the build target for tomcat, but add a
separate target to build only javamail-dependent classes, and package them in
a separate jar.
That would keep 'core' tomcat clean, and would work for other kind of
modules that have external deps.
I
What about: keep them excluded in the build target for tomcat, but add a
separate target to build only javamail-dependent classes, and package them in
a separate jar.
That would keep 'core' tomcat clean, and would work for other kind of
modules that have external deps.
It would be even better if
Bill Barker wrote:
My patch does nothing, unless you specify the jars specifically in the
build.properties file. There was a good reason that I didn't patch
build.properties.default as well.
I'm +1 to use the Geronimo implementations of JavaMail, +0 to using the
optional configuration that I
"Remy Maucherat" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> [EMAIL PROTECTED] wrote:
>> Author: billbarker
>> Date: Sun Apr 9 18:36:19 2006
>> New Revision: 392872
>>
>> URL: http://svn.apache.org/viewcvs?rev=392872&view=rev
>> Log:
>> Restore the ability to build with the Mai
[EMAIL PROTECTED] wrote:
Author: billbarker
Date: Sun Apr 9 18:36:19 2006
New Revision: 392872
URL: http://svn.apache.org/viewcvs?rev=392872&view=rev
Log:
Restore the ability to build with the Mail Resources
Sorry, I am not going to accept these dependencies on proprietary code
anymore. I ma
10 matches
Mail list logo
