[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

of gump is to give advance warning of upcoming > problems by building from the latest source. So if there were changes > in the smtp/wiser project that affected Commons email, you get advance > warning. Since as you say, its only a test dependency then its > probably not as important. >

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

pose of gump is to give advance warning of upcoming problems by building from the latest source. So if there were changes in the smtp/wiser project that affected Commons email, you get advance warning. Since as you say, its only a test dependency then its probably not as important. From a practica

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

at in other descriptors. > > Secondly the subethasmtp builds use JDK 1.5 to create standard jars > and then a ant task to produce JDK 1.4 compatible jar > flavours - which is what Commons Email needs - not sure if that > presents any issues for gump? To be clear, commons-email only u

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

reate standard jars and then a ant task to produce JDK 1.4 compatible jar flavours - which is what Commons Email needs - not sure if that presents any issues for gump? To be clear, commons-email only uses subethasmtp and wiser at test time; they are NOT runtime dependencies. For all practical purposes,

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

A couple of things: Firstly doing a svn checkout of subethasmtp requires a user/password - guest/guest works - but not sure how to configure the repository descriptor in gump for that as I couldn't find an subversion example of that in other descriptors. Secondly the subethasmtp builds use

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

"Stefan Bodewig" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Thu, 14 Jun 2007, Niall Pemberton <[EMAIL PROTECTED]> > wrote: >> On 6/14/07, Ben Speakmon <[EMAIL PROTECTED]> wrote: >>> Well, it works fine when I blow away my local m1 repository, so I'm >>> not sure what the pro

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

On Thu, 14 Jun 2007, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On 6/14/07, Ben Speakmon <[EMAIL PROTECTED]> wrote: >> Well, it works fine when I blow away my local m1 repository, so I'm >> not sure what the problem is. The problem is that nobody has updated the Gump descriptor with the new depe

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

.apache.org/gump/public/jakarta-commons/commons-email/gump_file/build.properties.html [2] http://svn.apache.org/repos/asf/gump/metadata/project/jakarta-commons.xml Ben Speakmon wrote: > Crap. > > Well, I say there's nothing wrong with the maven 1 project.xml. Any > suggestions? &

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

gump uses jar.override and none of the dependencies that were added in rev 480401 show up in gump's autogenerated build.properties [1]. I guess they have to be added in the gump metadata file [2]. HTH, -Lukas [1] http://vmgump.apache.org/gump/public/jakarta-commons/commons-

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

PROTECTED]> wrote: > > > > > > To whom it may engage... > > > > > > This is an automated request, but not an unsolicited one. For > > > more information please visit http://gump.apache.org/nagged.html, > > > and/or contact the folk at [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

quest, but not an unsolicited one. For > > more information please visit http://gump.apache.org/nagged.html, > > and/or contact the folk at [EMAIL PROTECTED] > > > > Project commons-email has an issue affecting its community integration. > > This issue affects 4 proje

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

lt;[EMAIL PROTECTED]> wrote: > > To whom it may engage... > > This is an automated request, but not an unsolicited one. For > more information please visit http://gump.apache.org/nagged.html, > and/or contact the folk at [EMAIL PROTECTED] > > Project commons-email has an iss

Re: [EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

e. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue affects 4 projects, and has been outstanding for 17 runs. The current state of this project is &#x

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

Re: [email] commons email: new method for HtmlEmail

Hi, create a bug in bugzilla [1] for commons-email and attach your patch to the bug: this is the easiest and safest way to post a patch. Bye Piero [1]http://issues.apache.org/bugzilla Alle 15:49, giovedì 20 aprile 2006, Zarkon ha scritto: > Hi! > > I've written a new "em

[email] commons email: new method for HtmlEmail

Hi! I've written a new "embed" method (simply but neccesary) for the HtmlEmail class. Where I can submit this method for studying if it can be incuyed in a future version of commons email? Many Thanks. - To unsu

Re: [email] commons email: email factory

Steven Paligo wrote: I have created a factory class that creates the SimpleEmail, HtmlEmail, and MultiPartEmail objects which have defaults set from a reloadable .properties file. Can I submit it as a patch or is something like that already being made? I would appreciate a response. External

commons email: email factory

I have created a factory class that creates the SimpleEmail, HtmlEmail, and MultiPartEmail objects which have defaults set from a reloadable .properties file. Can I submit it as a patch or is something like that already being made? I would appreciate a response. Thanks, Steven P. --

Re: [email] HtmlEmail fixes (wasRe: commons-email needs care)

apply. > > > > Bye > > Piero > > > > Alle 22:56, mercoledì 15 febbraio 2006, Dion Gillard ha scritto: > > > Tested and applied. > > > > > > On 2/16/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote: > > > > Hi Dion, all, > > >

[email] HtmlEmail fixes (wasRe: commons-email needs care)

uzzi <[EMAIL PROTECTED]> wrote: > > > Hi Dion, all, > > > > > > I'm still alive ;) > > > Attached you can find my reworked patch to fix many problems you can have > > > if using commons-email with a MailSession mainly caused by typos in > > &

Re: commons-email needs care

t; > > > I'm still alive ;) > > Attached you can find my reworked patch to fix many problems you can have > > if using commons-email with a MailSession mainly caused by typos in > > constant declaration or missing constant declaration. It fixes bugs 38538 > > and 38656

Re: commons-email needs care

Tested and applied. On 2/16/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote: > Hi Dion, all, > > I'm still alive ;) > Attached you can find my reworked patch to fix many problems you can have if > using commons-email with a MailSession mainly caused by typos in constant

DO NOT REPLY [Bug 38656] - [email] commons-email does not work using mailSession in tomcat

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 38656] - [email] commons-email does not work using mailSession in tomcat

gzilla/show_bug.cgi?id=38656 [EMAIL PROTECTED] changed: What|Removed |Added Summary|commons-email does not work |[email] commons-email does |using mailSess

Re: commons-email needs care

Hi Dion, all, I'm still alive ;) Attached you can find my reworked patch to fix many problems you can have if using commons-email with a MailSession mainly caused by typos in constant declaration or missing constant declaration. It fixes bugs 38538 and 38656 (just opened to hold the

DO NOT REPLY [Bug 38656] - commons-email does not work using mailSession in tomcat

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 38656] New: - commons-email does not work using mailSession in tomcat

gzilla/show_bug.cgi?id=38656 Summary: commons-email does not work using mailSession in tomcat Product: Commons Version: 1.0 Final Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Com

Re: commons-email needs care

Ping? On 2/12/06, Dion Gillard <[EMAIL PROTECTED]> wrote: > Hi Piero, > > some comments inline. > > On 2/9/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote: > > Hi Hen, > > > > many thanks for your answer. > > Here is a long mail on commons-email s

Re: commons-email needs care

Hi Piero, some comments inline. On 2/9/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote: > Hi Hen, > > many thanks for your answer. > Here is a long mail on commons-email status :) > > SVN Repository > The activity on SVN repository (speaking of the src/java dir) is stalle

[email] Re: commons-email needs care

Thanks Piero; great reply. Answering inline: On 2/9/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote: > Hi Hen, > > many thanks for your answer. > Here is a long mail on commons-email status :) > > SVN Repository > The activity on SVN repository (speaking of the src/jav

Re: commons-email needs care

Hi Hen, many thanks for your answer. Here is a long mail on commons-email status :) SVN Repository The activity on SVN repository (speaking of the src/java dir) is stalled about 5 month ago. What you can find in SVN repository compiles fine and looks like what has been released as 'Co

Re: commons-email needs care

On 2/8/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote: > Hi Chris, > > I already read URLs you proposed and they simply say to open a bug or send a > patch; in commons-mail bugzilla you can find about 10 open bugs many of them > with patch attached. > If you look at SVN commons-mail repository you c

Re: commons-email needs care

next week :) Mvgr, Martin Piero Ottuzzi wrote: Hi there, yesterday I used commons-email 1.0 and I found it is quite buggy (for the jakarta quality meter). I found many bugs fixed in bugzilla (not yet ported in SVN) and some more I fixed by myself. How can I help to improve this situation? It

Re: commons-email needs care

Piero > Cheers, > > recommended readings: > * http://jakarta.apache.org/site/getinvolved.html > * http://jakarta.apache.org/commons/patches.html > > Regards, > Chris > > Piero Ottuzzi wrote: > > Hi there, > > > > yesterday I used commons-email 1.

Re: commons-email needs care

Cheers, recommended readings: * http://jakarta.apache.org/site/getinvolved.html * http://jakarta.apache.org/commons/patches.html Regards, Chris Piero Ottuzzi wrote: Hi there, yesterday I used commons-email 1.0 and I found it is quite buggy (for the jakarta quality meter). I found many bugs

commons-email needs care

Hi there, yesterday I used commons-email 1.0 and I found it is quite buggy (for the jakarta quality meter). I found many bugs fixed in bugzilla (not yet ported in SVN) and some more I fixed by myself. How can I help to improve this situation? It really seems that commons-email needs care to fix

Re: [email] Re: Apache Jakarta Commons Email 1.0 released

On Mon, 2005-10-03 at 22:38 -0500, Eric Spiegelberg wrote: > There is no mention of the v1.0 release of Commons Email listed in the > "Latest Jakarta News" on http://jakarta.apache.org. It's not a big deal, > but it would be nice if it were

[email] Re: Apache Jakarta Commons Email 1.0 released

There is no mention of the v1.0 release of Commons Email listed in the "Latest Jakarta News" on http://jakarta.apache.org. It's not a big deal, but it would be nice if it were added. Henning Schmiedehausen wrote: The Commons Email team of the Jakarta Project of the ASF is ha

Apache Jakarta Commons Email 1.0 released

The Commons Email team of the Jakarta Project of the ASF is happy to announce the release of Commons Email 1.0. Jakarta Commons Email provides an API for sending email. It is built on top of the Java Mail API, which it aims to simplify. While this is the first official release for Commons Email

Re: [VOTE][RESULT] Release Commons Email 1.0

Eric Pugh <[EMAIL PROTECTED]> writes: >It looks like Commons Email 1.0 based on Henning's RC8 is go for launch! Thanks! Start rolling the release right now. Just in time for the Turbine 2.3.2 release. :-) Best regards Henning >The following people

[VOTE][RESULT] Release Commons Email 1.0

It looks like Commons Email 1.0 based on Henning's RC8 is go for launch! The following people voted +1 for the release: Dion Gillard +1 Stephen Colebourne +1 Henning Schmiedehausen +1 Eric Pugh +1 The following people voted +0 for the release: robert burrel donkin +0 phil steitz +0 There

Re: [VOTE][restarted] Release Commons Email 1.0

Get my +1 in the email record. [X ] +1 Release Email 1.0 based on RC8 [ ] +0 General support but not definitive [ ] -0 Unhappy about the release but not definitive (We want to see RC9, RC10, and R11 first!) [ ] -1 Do not release Email 1.0 based on RC8 Cheers, Eric Pugh On Sep 1, 2005,

Re: [VOTE][restarted] Release Commons Email 1.0

Phil Steitz <[EMAIL PROTECTED]> writes: >Agree with Robert's comments and am also +0, with three additional comments= >: >* The ant build depends javamail 1.3.2, while the maven POM references 1.3.= >3.=20 >The ant build should be updated to match the POM Ok, will do. >* It would be good to pro

Re: [VOTE][restarted] Release Commons Email 1.0

Agree with Robert's comments and am also +0, with three additional comments: * The ant build depends javamail 1.3.2, while the maven POM references 1.3.3. The ant build should be updated to match the POM * It would be good to provide some instructions in the README, release notes or web site on

Re: [VOTE][restarted] Release Commons Email 1.0

On Mon, 2005-09-12 at 14:31 -0400, Eric Pugh wrote: > I would like to restart the vote for Commons Email 1.0 based on RC8. > The various packaging/dependency issues have been resolved, and > Commons Email is working great on WebLogic. While this voting > process has dragged on,

Re: [VOTE][restarted] Release Commons Email 1.0

robert burrell donkin <[EMAIL PROTECTED]> writes: >i don't seem to be able to RC8 in >http://people.apache.org/~epugh/commons-email/. should i be looking >somewhere else? http://people.apache.org/~henning/commons-email/ :-) Best regards Henning

Re: [VOTE][restarted] Release Commons Email 1.0

i don't seem to be able to RC8 in http://people.apache.org/~epugh/commons-email/. should i be looking somewhere else? - robert On Mon, 2005-09-12 at 14:31 -0400, Eric Pugh wrote: > I would like to restart the vote for Commons Email 1.0 based on RC8. > The various packaging/depend

Re: [VOTE][restarted] Release Commons Email 1.0

+1. Release it already :-) On 9/13/05, Eric Pugh <[EMAIL PROTECTED]> wrote: > I would like to restart the vote for Commons Email 1.0 based on RC8. > The various packaging/dependency issues have been resolved, and > Commons Email is working great on WebLogic. While this votin

Re: [VOTE][restarted] Release Commons Email 1.0

Eric Pugh wrote: I would like to restart the vote for Commons Email 1.0 based on RC8. The various packaging/dependency issues have been resolved, and Commons Email is working great on WebLogic. While this voting process has dragged on, it has also led to a lot of polish being added, and

Re: [VOTE][restarted] Release Commons Email 1.0

Eric Pugh <[EMAIL PROTECTED]> writes: >I would like to restart the vote for Commons Email 1.0 based on RC8. >The various packaging/dependency issues have been resolved, and >Commons Email is working great on WebLogic. While this voting >process has dragged on, it has al

[VOTE][restarted] Release Commons Email 1.0

I would like to restart the vote for Commons Email 1.0 based on RC8. The various packaging/dependency issues have been resolved, and Commons Email is working great on WebLogic. While this voting process has dragged on, it has also led to a lot of polish being added, and reducing the

[email] commons-email 1.0-RC8 available

Due to the requests from Stephen, Niall and some remarks on the users list about using commons-email in J2EE environments, I've applied the patches that they contributed and verified that commons-email indeed builds and works with JDK 1.3.x and Javamail 1.2 using both the maven and the ant

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

[EMAIL PROTECTED]: Project commons-email (in module jakarta-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-email has an issue affecting its community integration. This issue

Re: Lang dependency [VOTE] Release Commons Email 1.0

Stephen Colebourne wrote: Henning P. Schmiedehausen wrote: Give us a patch. Code before words. As I said, I've looked into this and I might do some work for 1.1. Not for 1.0. I send this as a patch on Bugzilla today. The patches are now there. They remove the whole [lang] dependency by ad

Re: Lang dependency [VOTE] Release Commons Email 1.0

{ super.printStackTrace(out); if (cause != null && !HAVE_THROWABLE_CAUSE) { out.print("Caused by: "); cause.printStackTrace(out); } } } } diff -d -r -C2 commons-email.orig/src/java/org/apache/c

Re: Lang dependency [VOTE] Release Commons Email 1.0

robert burrell donkin <[EMAIL PROTECTED]> writes: >so, i'd suggest that email adopts a solution along those lines. the >simplest and quickest approach would be to simply copy the necessary >source and repackage it as org.apache.commons.email.lang. if people are >happy with this approach, i'd be wi

Re: Lang dependency [VOTE] Release Commons Email 1.0

Stephen Colebourne <[EMAIL PROTECTED]> writes: >Henning P. Schmiedehausen wrote: >> Give us a patch. Code before words. As I said, I've looked into this >> and I might do some work for 1.1. Not for 1.0. >I send this as a patch on Bugzilla today. Cool. Thanks. Regards Hen

Re: Lang dependency [VOTE] Release Commons Email 1.0

Henning P. Schmiedehausen wrote: Give us a patch. Code before words. As I said, I've looked into this and I might do some work for 1.1. Not for 1.0. I send this as a patch on Bugzilla today. Stephen - To unsubscribe, e-mai

  1   2   3   4   >