If anything needs doing before the RC or the release please let me
know, I have some time. Unfortunately I cant help with the release
itself.
-Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
All of this sounds good, but I havent had a chance to test it myself as yet.
+1
-Corey
On 8/10/05, Eric Pugh [EMAIL PROTECTED] wrote:
Hi all,
I checked out 34056 (http://issues.apache.org/bugzilla/show_bug.cgi?
id=34056) and it doesn't seem bad. The one thing Henning highlighted:
-
Eric,
Firstly, welcome... Secondly... thanks.
There are two things that would like to suggest with your patch.
First:
Please try to break this patch down into discrete sections. i.e. one
patch for formatting and one for each of the other changes.
Second:
Please submit your patch(es) to the
+1 (not a comitter)
-CS
On Mon, 28 Feb 2005 22:58:37 -0800, Eric Pugh
[EMAIL PROTECTED] wrote:
Hi all,
The commons-email RC3 release has been available for a couple days, and
has isn't fundamentally changed from the RC2 release that has been out
for a couple months. I'd like to move
Commons Developers List; Corey Scott
Subject: Re: [Email] To release or not to release
I'm +1.
On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott
[EMAIL PROTECTED] wrote:
Can someone with commit priviledge please change
email over
from RC1to v.1.0
Can someone with commit priviledge please change email over from RC1 to v.1.0?
The RC has been out for quite a while now and so far there are no
complaints about this.
There are several other things waiting for this release, e.g. a
proposed change to the jelly email classes (change to Commons
Rory,
Has the plugin installed properly?
You could try to clear your cache directory MAVEN_HOME/cache and then
run this command:
maven plugin:download -DartifactId=maven-statcvs-plugin
-DgroupId=statcvs -Dversion=2.5
This should install it for you.
Cheers,
Corey
On Mon, 6 Dec 2004 17:30:14
Actually I had been looking at JTest and I know that there is no way
my company would pay for such a product. The impression I got from
their doco was that is was a 'nice' tool if you were doing what it
wanted you to do.
With all this in mind, I was thinking that a whole heap of my tests
(and
A quick question for the collective brains trust.
I have been looking into test (and code) generation and have come to a
unexpected results.
1) JUnitDoclet appears to be the only (reasonable) opensource product around
2) commerical equiv are incredibly expensive
3) JUnitDoclet seems extremely
or something?
Mark
On Tue, 30 Nov 2004 11:38:30 +0800, Corey Scott [EMAIL PROTECTED] wrote:
Sounds good to me, I have a stack of things waiting for the next version.
Also I think most of the bugs have been cleared off by your recent
commits so there shouldnt be any reason to stop us from
see anything else outstanding.
Maybe we should start a RC1 thread?
-Corey
On Tue, 30 Nov 2004 13:38:15 +0100, Mark Lowe [EMAIL PROTECTED] wrote:
What needs to be done for 1.0 then? Give me a list and i'll put some
time aside to pitch in.
On Tue, 30 Nov 2004 20:35:48 +0800, Corey Scott
: Sunday, November 28, 2004 4:04 PM
To: Commons dev list; Corey Scott
Subject: [email] Exceptions
The issue of exceptions has come up a few times, and heres a summary
of my understanding of whats been said and agreed and disagreed about.
The idea of throwing
]
Sent: Monday, November 29, 2004 3:19 PM
To: Corey Scott
Cc: Jakarta Commons Developers List
Subject: Re: [email] Exceptions
My thoughts on the test cases are that they should throw exception,
and then have the exception testing separate. This would make the
cases shorter also
a Release Candidate and then roll
1.0. We should also start thinking about what the next version will entail.
Eric
-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Monday, November 29, 2004 5:25 PM
To: Corey Scott
Cc: Jakarta Commons Developers List; [EMAIL
We appreciate all the help we can get :-)
-Corey
On Fri, 26 Nov 2004 11:35:04 -0800, Craig McClanahan [EMAIL PROTECTED] wrote:
On Fri, 26 Nov 2004 11:14:28 +0100, Eric Pugh [EMAIL PROTECTED] wrote:
But, it's not really a big deal. It's only a problem for the nightly build
based on Ant,
Well I like everyone else was spammed. That said, (i may be a
minority here, but), I am thankfull to Martin.
Good Job, good initiative, and as a side issue, the spam may actually
cause us to do something about this issue for the long term.
Just my 2 cents.
-Corey
Whoopsit must be later than I thought...sorry.
Kudos to Emmanuel
On Wed, 24 Nov 2004 10:59:15 -0800, Martin Cooper [EMAIL PROTECTED] wrote:
On Thu, 25 Nov 2004 02:48:21 +0800, Corey Scott [EMAIL PROTECTED] wrote:
Well I like everyone else was spammed. That said, (i may be a
minority
[email] is currently failing in gump, it complains about some dumbster
methods. Now I took a look at it (read I havent a clue re: gump) and
noticed that the build-gump.xml file is 2 years old. Does this mean
its not in use?
I run the maven gump goal and get a completely different output from
So the vote has passed right?
*in a hurry to celebrate and move on to making email better*
:-)
-Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I also had to recently do this, for the same reasons :-)
-Corey
On Thu, 18 Nov 2004 00:26:16 + (GMT), Stephen Colebourne
[EMAIL PROTECTED] wrote:
FYI, I recently had to write this same method to take
resource keys and make more human readable sentences.
So, maybe there is space for it in
I have taken a quick look at Jame, maybe someone might correct me, but
I cant see anything similar to this. I will be the first to admit
that I am not a domain expert in this particular area, but I am
definately interested and can see the use for a compact 'fake' mail
server, with decent error
Serge,
[Extract from the website http://quintanasoft.com/dumbster/]
The Dumbster is a very simple fake SMTP server designed for unit and
system testing applications that send email messages. It responds to
all standard SMTP commands but does not deliver messages to the user.
The messages are
...
-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Monday, November 15, 2004 8:45 AM
To: Corey Scott
Cc: Jakarta Commons Developers List
Subject: Re: DO NOT REPLY [Bug 32094] - [email] All exceptions seem to
be thrown as messagingExceptions
Opps.. I'd need
So back to the original problem.
Dumbster is currently used by the tests. The way I see it this leaves
us with a few options:
1) Remove it (and wait for the ok or change of license
2) Replace it (I havent seen an alternative, but I am willing to look)
3) Do it ourselves.
To be honest, my
I also like these ideas and am happy to help you implement them if you
would like. However there is one thing we may want to be aware of. I
dont think that the setCharset causes the UnsupportedCharsetException
to be throw, I believe that it doesn't check it and therefore allows
for any value to
Thanks Joe, it would be nice to not have to burden Eric so much with
committing all of Mark and my changes :-)
Regards,
Corey
On Sun, 14 Nov 2004 15:17:57 -0600, Joe Germuska [EMAIL PROTECTED] wrote:
I updated Email.java and added some notes at the bottom of
xdocs/examples.xml. I couldn't
Eric,
Do you know why the commons-email SNAPSHOT.jar is very old on the
maven repo? Do we have to do something to keep this up to date?
Thanks,
Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
: Corey Scott
Attachments: conversion_to_commons_email.txt
Attached is a proposed change to the jelly-tags:email component that converts
it to leverage of the (soon to be upgraded and released, hopefully)
commons-email. In particular the the HtmlEmail class. The commons-email
component
[ http://nagoya.apache.org/jira/browse/JELLY-162?page=history ]
Corey Scott updated JELLY-162:
--
Attachment: conversion_to_commons_email.txt
patch mentioned in improvement proposal
Proposed change/improvement to jelly-tags-email
[
http://nagoya.apache.org/jira/browse/JELLY-162?page=comments#action_55478 ]
Corey Scott commented on JELLY-162:
---
In appendum to this proposal. I am not very experienced with jelly, so any
help/hints in how to set up tests for this component would
Yes, this includes/superceeds all previous related changes.
-Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This may not the time (or the place), but I am going to ask anyway.
It would seem that at the moment, all around the world, people are
doing the same work over and over. Particularly in regard to certain
packages/functions, this to me seems a little (well a lot) redundant.
Specifically, there
Thanks Martin, I hadnt seem Lenya before.
Thanks to everyone else who commented. I didnt want to sound
anti-diversity. I agree with you all diversity is good. I was trying
to suggest developing something based on standards so that integration
would be it usual nightmare.
Obviously CMS was a
In addition to this (and to post to this list, what we have been
discussion privately). I have added a method to the dumbster which
takes a server socket as an input instead of a port number. The
advantage of this is that you can create the server socket using:
ServerSocket newSocket = new
As far as I know I dont use smtp.jar at all? Weird
Its not the project file, there is no lib dir. Have i missed something?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Is this a OSX only thing? (I have tested WinXp and Redhat only)
-Corey
On 4 Nov 2004 16:13:36 -, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
On Tue, 2 Nov 2004 20:42:03 -0800, Martin Cooper [EMAIL PROTECTED] wrote:
It's not a question of whether anyone could tell, or whether or not
you should have mentioned it. The point is that the ASF can not accept
LGPL derived code, for legal reasons.
Sorry I was kidding, guess i shouldnt have
Mark,
I have been trying to get this to work on my Redhat box, after quite a
bit of time the conclusion is it doesnt. I have created a Maven build
script for dumbster and the maven test goal doesnt run with the unit
test that come with the dumbster.
I am going to try to fiddle with the dumbster
-
From: Eric Pugh [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 03, 2004 7:49 AM
To: Jakarta Commons Developers List; Corey Scott
Subject: RE: Steps prior to graduating from Sandbox
Okay.. If dumbster doesn't work on *nix, then maybe we need to make it
more
I believe I might have the answer to our 'problem'.
Unless this article is out of date (i found the same statement
elsewhere and I can see no reason why it would have changed.
[excerpt]
On Unix systems (but not Windows or the Mac) your program must be
running as root to bind to a port between 1
There are two answers:
(Long answer)
We want to get the unit tests finalized and then we need to get the
promoted to commons-proper.
(short answer)
asap :-)
-Corey
On Wed, 3 Nov 2004 10:37:46 +0100, Emmanuel Venisse
[EMAIL PROTECTED] wrote:
Hi,
When do you plan to release an 1.0 version?
Maybe some kind of collated summary report for the both commons and
sandox. This would allow those not reading the commons-dev list or
having it heavily filtered to easily keep track of how active projects
are and what changes have been made recently
To whom might be interested,
I have developed an extension (sort of) to the JDiff maven plugin that
checks-out a version (defined by property ${maven.jdiff.javadoc.tag},
defaults to CURRENT) and then generates the javadoc.
The docs are generated in:
${docsDest}/apidocs/${maven.jdiff.javadoc.tag}
What is the process/thoughts on upgrading the depencies?
Eg. mail from 1.3 to 1.3.2
-Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
We can remove the validator now, I have already removed the need for
it, I forgot to submit a patch for thisSorry.
Also you may be interested to know, that the version of dumbster is
1.3 not 1.0.3, unfortunately the developer is not a Maven person
(yet). Should we make this change and
On Tue, 2 Nov 2004 12:55:43 +0100, Mark Lowe [EMAIL PROTECTED] wrote:
[snip]
or even provide me a
way of listing all bugs for [email] only and i can see what i can
pitch in with.
I dont know if this is correct, but I just set up a query in bugzilla
for [email] in the subject and then used the
On Tue, 2 Nov 2004 13:17:29 +0100, Mark Lowe [EMAIL PROTECTED] wrote:
[snip]
Could be the start stop fake server, is there a reason why the same
fake mail session couldn't be used throughout the tests?
To be honest, I made it start a fresh everytime just to make sure it
was clean and in a way
Scott,
Could you please send me a Junit test case for this so I try to fix it for you?
Thanks,
Corey
On Tue, 02 Nov 2004 07:29:14 -0500, Scott [EMAIL PROTECTED] wrote:
Hi,
Eric Pugh wrote:
Hi all,
I started updating the Status.html doc. I wanted to make sure we have a
Message-
From: Corey Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 02, 2004 1:25 PM
To: [EMAIL PROTECTED]
Subject: Re: [email] Steps prior to graduating from Sandbox
My 2 cents:
I dont use these files, but there are people that use ant. So maybe
we should make sure
Great,
Attached is the plugin.jelly file, as I said before, this is my first
one, so no guarantees to quality. Maybe someone could help me test
this and get it to where it needs to be?
Thanks,
Corey
PS. I have to acknowledge the fact that I 'borrowed' and modified the
jdiff code (thanks go
Maybe I should not have mentioned it?
All I did was checkout the jdiff maven plugin (plugin.jelly file) from
apache CVS, and use it as a base for the code for this. This was just
because I didnt really know what I was doing and this was the quickest
way. Looking at the code again, if I had
The last round/s of patches should have fixed this.
-Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Is anyone interested/upset if I propose that we change this to utilise
the Commons Sandbox Email project?
I happy to do the bulk of the work and add basic junit tests as required.
Is this a good idea or bad?
Open to opinions.
-Corey
Currently the doco (Configuration Factory Howto) suggests that you
should load resource from the classpath. IMHO i think this is a great
idea, although I had some trouble implementing it.
It recommends to use:
URL configURL = getClass().getResource(/config.xml);
I could not get this to work
Mark,
Can you please clarify regarding the unsupportedcharset exception, as
I have had no problem with this, except for this fact that the unicode
chars are not being submitted to the cvs nicely.
Thanks,
Corey
-
To
Guys,
I need some guidance. The test cases mentioned are failing for a
couple of reasons. The ones that are failing are doing so because the
personal names are still using ? instead of an invalid unicode
character, we can replace them with something like \uc5ec (this is
korean i believe) they
We have quite a few style violations that have crept back in, do you
mind if i fix those as well? Do you recommend a separate patch? If
it is ok with you, i would rather submit one patch for all of it cause
stuff keeps getting lost :-)
Thanks for the advice,
Corey
PS. I will try to take you
Ok, sounds good.
I will make sure I test the patch before sending it too you. Seeing
as we are both using eclipse, hopefully this will mean that I can be
sure that it applies before I send it.
Regards,
Corey
-
To unsubscribe,
It doesnt use smtp.jar, right?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
We may also find that the mail.jar has an API for retrieving messages
from a mail server, may be can use this rather than adding a new jar?
What do you feel about saving the output of the tests to a file (mail
messages) only. This way one could check the output without and
connection and without
Do you have anymore info on why the tests are failing?
If it the previous set of tests (before last nights updates) then it
is probably due to some validation that was missing in one of the
patches and should now be there.
Namely, throwing exceptions on bad inputs like a null message.
Other than
Ok... please ignore my previous message.
I have checked out the current source. An I do get 5 errors.
The errors are ALL caused by the same thing.
Now please let me try to explain what is causing this.
The error is tests are for invalid character sets in the personal
section of and email
Matthias,
I definately agree with you, inputs (emails in this case) should be
validated before submission to a low level api such as [email].
However I added the validation just to make sure. I guess you could
call it 'defensive' coding. I am happy to remove this and numerous
other input
I believe the code for email validation is not too much (certainly
less than the whole of validator package). Are you thinking of
duplicating it in place of the validation reference or removing the
validation from the functions and providing a validation function?
Either of which should not be
Is anyone interested in a set of wrapper classes around the rest of
the Mail API, naming for the receiving of email?
As email is intended to be small maybe this would consistute a new project?
Just interested to hear anyones thoughts (positive or negative welcome :-D)
-Corey
I definately don't want to create a mail server :-)
Actually I was thinking of something similar to a simple set of
functions similar to the way that PHP has wrappers on the IMAP lib
(ftp://ftp.cac.washington.edu/imap/)
Maybe James takes care of this already, I am not certain.
As to adding XML
I think this is a great idea!!
-Corey
Hi,
These ideas are all very interesting. I would just caution against
falling into the same pits experienced by [configuration] and [math]:
that is, endlessly debating/adding features, refactoring, etc, before
ever making a release. It might be good
I know this is outside of the limits of this list but I think that the
people here might be those that might be interested.
I have 3 gmail invitations free if anyone that hasn't already got a
gmail account and would like one. Its a first come, first served
deal.
Please dont flame me for posting
Is there a reason why a some of the commons sites have not been
updated for a few months? Isnt this giving people (outsiders) a false
sense of how active/inactive the projects are?
I thought that seeing as most sites are probably
auto-generated/updated using maven that someone would have cron'd
So have we reached a concensus on all of this?
To summarize:
-Validation should NOT be included in the current version
-This issue will be revisited after the release
-The current functionality is appropriate AS IS
-The major targets we have now prior to a first release are:
1) Complete the Unit
Forgive me if I am speaking out of turn, but would this only be a
matter of running the maven reports target against the release branch
of the cvs not the latest?
(this sound like something obtainable with a reasonably small amount of effort)
Then hacking together a menu which indicated this?
They are all gone now... thx for your interest.
Glad to be able to help :-)
Regards,
Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ok, I have the tests all up and running with Maven.
I have also made some minor mods, based on the tests or improving the
input checking (this is why some of the tests are failing, there where
against my changes not the HEAD version sorry)
So once we get this formatting issue sorted, I will
Ok, I will switch my build to maven from Ant (although Maven seemed
not to like dumbster too much last time I tried it). I will get the
get the tests going and resubmit.
I think I'm going to have to start again from the cvs, cause my code
tree is becoming too different from the committed one. I
to improve it? What is annoying about it?
2b) If not, why not? What doesn't it do that stops you from using it?
3) Any other suggestions?
All responses will be greatly appreciated.
Thanks,
Corey Scott
PS. It is not my intention to start a flame war, so please be honest
but not (too) brutal in any
Stephen,
Forgive me for asking for confirmation, but does this mean that you
are NOT in favor of changing the way that the Email library handles
configuration?
Meaning that the coder must still set all of the config vars?
I think this is fine, in fact I find that I use the config project for
I was actually considering a couple of functions:
1) where by you could input a HTML file and it would parse out all img
links and add the cids automatically (obvious problem with image
directories here).
2) maybe some small helper functions / wrappers around the existing
functions, eg. adding an
Has anyone managed to get maven and dumbster to work together?
I currently have a project which the unit test run fine (using eclipse
and ant) but when i run the same tests using maven it cannot find the
fake smpt server started by dumbster.
Anyone have any ideas?
Thanks,
Corey
{snip}
What I need is a Apache contrib for dummies HOWTO
I couldnt agree more with this. I am new here and I had somethings to
add to the email project recently but after searching the commons and
sandox project I was confused with exactly what to do and why. a
decent HOWTO would help
be a patch with both!
Eric
-Original Message-
From: Corey Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 19, 2004 5:48 AM
To: Jakarta Commons Developers List
Subject: Re: [EMAIL PROTECTED]: Project commons-email (in module
jakarta-commons-sandbox) failed
I
some of the project team directly but this appears
to be the wrong thing to do (my apologies), so can some please
tell me what I am to do with my contribution?
Many thanks,
Corey Scott
-
To unsubscribe, e-mail: [EMAIL
a hand.
Thanks,
Corey
On Mon, 18 Oct 2004 12:05:11 -0500, Joe Germuska [EMAIL PROTECTED] wrote:
At 12:40 AM +0800 10/19/04, Corey Scott wrote:
Firstly if this is the wrong place to send this then I am sorry but I
am having trouble finding exactly where I should be sending my emails?
:-)
I
Eric,
Sorry i realised that my coding style is not correct also, I will
change it and resubmit the patch. Thanks for changing the Mocks as
well (something I had completely not thought of doing. I will look
into Dumpster and will trying to make the ant file better (although
any suggestions would
I dont know how to fix this, but yes, I added email validation using
commons-validator and I believe this is the problem that is causing
the build to fail.
-Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
84 matches
Mail list logo
