[
https://issues.apache.org/jira/browse/EMAIL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472592
]
Piero Ottuzzi commented on EMAIL-62:
Hi Dion, all,
commons-email 1.0 is quite broken and I think we need to move
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 "embed" method (simply but
u can't get to it in the next few days, I will:-)
>
> On 2/18/06, Piero Ottuzzi <[EMAIL PROTECTED]> wrote:
> > Hi Dion, all,
> >
> > I created a patch against HtmlEmail as you proposed in you comment to bug
> > 37344 (using the class provided in the same bug
email client.
Let me know what you think about this patch and if you like it please 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,
&g
patch): please have a
look and let me know.
Probably tomorrow I will test what is in the repository.
Thanks for your attention
Bye
Piero
> Ping?
>
> On 2/12/06, Dion Gillard <[EMAIL PROTECTED]> wrote:
> > Hi Piero,
> >
> > some comments inline.
> >
> >
Hi Chris,
I was thinking that something like
Compress.getInstance(String compressorType);
like Crypto would be nice.
This way you can get a unique "entry point" for every compression algorithm
that can provide its own methods to compress/decompress/add files etc etc.
Bye
Piero
Alle 10:58, marte
lue=&product=Commons&component=Email&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cm
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.
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