It should be.. However, I found it a real pain.. I think I need to really
sit down and learn JNDI.. Write some unit tests of parsing the tree etc..
I thought it would be a simple matter, ended up not being. Not, I think,
because of complexity, but just my own knowhow of JNDI. Does anyone
I really like the nutshell on Java's treatment of JNDI. It is a great
job, I think.
Jack
On Wed, 27 Oct 2004 08:44:06 +0200, Eric Pugh [EMAIL PROTECTED] wrote:
It should be.. However, I found it a real pain.. I think I need to really
sit down and learn JNDI.. Write some unit tests of
Hi all,
Running into some annoying Maven problems w/ [email]. Dug into it and
discovered that the jakarta-commons/commons-build is quite different from
jakarta-commons-sandbox/sandbox-build files. This means that a project
graduating from sandbox will build differently then expected.
I'd like
epugh 2004/10/27 02:53:46
Modified:email/src/test/org/apache/commons/mail HtmlEmailTest.java
EmailTest.java MultiPartEmailTest.java
SimpleEmailTest.java
email/src/java/org/apache/commons/mail MultiPartEmail.java
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31901.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
epugh 2004/10/27 02:58:58
Modified:email/src/java/org/apache/commons/mail HtmlEmail.java
email/xdocs changes.xml
Log:
Bug 31904 Inline attatchment encoding was incorrect
Revision ChangesPath
1.11 +3 -3
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31904.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
epugh 2004/10/27 03:02:49
jakarta-commons-sandbox/email/conf - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
epugh 2004/10/27 03:02:53
Added: email/conf HEADER.txt checkstyle.xml
Log:
add checkstyle files
Revision ChangesPath
1.1 jakarta-commons-sandbox/email/conf/HEADER.txt
Index: HEADER.txt
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30634.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31881.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27699.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
epugh 2004/10/27 03:16:38
Modified:emailproject.properties
Log:
specify to use internal checkstyle
Revision ChangesPath
1.5 +4 -2 jakarta-commons-sandbox/email/project.properties
Index: project.properties
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30634.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
To whom it may satisfy...
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-xo *no longer* has an issue.
The current state of this project is
Should these test cases work (after editing the EmailConfig test class)?
I had most of them working yesterday enough to mail me the test mails,
but today i cant get them doing anything. I have an smtp service
running locally, but is this being done by this dumpster thing now?
Anything you could
To whom it may satisfy...
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-resources *no longer* has an issue.
The current state of this project
All but the EmailTest should run.. Dumbster [1] fakes out your SMTP
server, so you don't even need one. Of course, I am not sure what happens
if you have a real smtp server running on port 25 and you use Dumbster.
I assume you are running under Maven? Run maven test and most should
work.
The problem is I need to check output, the stuff that Junit cant do.
So the easiest way is having teh emails mailed from the test cases..
test:test:
[junit] Running org.apache.commons.mail.DefaultAuthenticatorTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.964 sec
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
After discussion and more tests in the Slide group I have abandoned
the approach.
All this does not work for realistic scenarios and realistic sizes.
Main problem is that if the keys do not share much common prefixes the
size of states gets enormously and impracticably high.
Sources still can be
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31901.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31901.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31918.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
All the errors (not failures) I get are
javax.mail.NoSuchProviderException: smtp ..
It could be a misconguration on my part. If I had a better idea I'd
enter a bug.
Mark
P.S. Thanks!! For the gmail address.
On Wed, 27 Oct 2004 22:23:00 +0800, Corey Scott [EMAIL PROTECTED] wrote:
Ok... please
How about after applying the memory leak patch and the XMLOutput flush
patch, we make it a release candidate for 1.0?
On Tue, 26 Oct 2004 23:49:22 -0400, Hans Gilde [EMAIL PROTECTED] wrote:
We're not entirely sure if the big memory leak is gone, how about an interim
release for Servlet users
Oliver Heger wrote:
Hmm, navigating through a tree based on a configuration key, creating
missing nodes if necessary and finally storing the value...
Similar code is contained in HierarchicalConfiguration and I suppose in
XMLConfiguration, too, to update the internally used DOM tree. I wonder
Corey Scott wrote:
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
dion2004/10/27 10:39:41
Modified:jelly/src/java/org/apache/commons/jelly/impl TagScript.java
Added: jelly/src/test/org/apache/commons/jelly outputBad.jelly
TestXMLOutput.java outputGood.jelly
Log:
Jelly-138. character data flushed XMLOuput while
dion2004/10/27 10:40:39
Modified:jelly/xdocs changes.xml
Log:
Jelly-138. character data flushed XMLOuput while XML data doesn't
Revision ChangesPath
1.21 +1 -0 jakarta-commons/jelly/xdocs/changes.xml
Index: changes.xml
[ http://issues.apache.org/jira/browse/JELLY-138?page=history ]
dion gillard resolved JELLY-138:
Resolution: Fixed
Fix Version: 1.0
Committed patch
character data flushed XMLOuput while XML data doesn't
On Wed, 27 Oct 2004 11:15:25 +0200, Eric Pugh wrote:
Hi all,
Running into some annoying Maven problems w/ [email]. Dug into it and
discovered that the jakarta-commons/commons-build is quite different from
jakarta-commons-sandbox/sandbox-build files. This means that a project
graduating
Okay.. I will go ahead and make the changes.. I think, so that you don't
have to check out both, that they are seperate. But, they should still be
pretty simiar in terms of what the basic POM offers.
ERic
-Original Message-
From: Tim Reilly [mailto:[EMAIL PROTECTED]
Sent:
Hi,
I've not fully understood what this is good for. I thought the main problem is to
invalidate/remove subtrees in a cache.
This could be achieved quit simple, doesn't it?
Or have I missed something...
Cheers,
Daniel
Jakarta Commons Developers List [EMAIL PROTECTED] schrieb am 27.10.04
Having groups you can invalidate? Or anything else? Groups would work,
I more or less persued this for fun...
Oliver
On Wed, 27 Oct 2004 22:09:23 +0200, Daniel Florey [EMAIL PROTECTED] wrote:
Hi,
I've not fully understood what this is good for. I thought the main problem is to
dion2004/10/27 14:49:28
Added: jelly/src/java/org/apache/commons/jelly/impl
WeakReferenceWrapperScript.java
jelly/src/java/org/apache/commons/jelly/util TagUtils.java
Log:
Add classes for Jelly-148, with a little refactoring to remove
dion2004/10/27 14:50:07
Modified:jelly/src/java/org/apache/commons/jelly TagSupport.java
Log:
Use TagUtils class
Revision ChangesPath
1.35 +3 -19
jakarta-commons/jelly/src/java/org/apache/commons/jelly/TagSupport.java
Index: TagSupport.java
dion2004/10/27 14:50:53
Modified:jelly/src/java/org/apache/commons/jelly/impl TagScript.java
Log:
Use WeakReferenceWrapperScript for Jelly-148
Revision ChangesPath
1.46 +3 -2
jakarta-commons/jelly/src/java/org/apache/commons/jelly/impl/TagScript.java
dion2004/10/27 14:51:13
Modified:jelly/jelly-tags/xml/src/java/org/apache/commons/jelly/tags/xml
TransformTag.java
Log:
Use WeakReferenceWrapperScript for Jelly-148
Revision ChangesPath
1.6 +58 -4
dion2004/10/27 14:57:50
Modified:jelly/xdocs changes.xml
Log:
Docs for Jelly-148
Revision ChangesPath
1.22 +1 -0 jakarta-commons/jelly/xdocs/changes.xml
Index: changes.xml
===
RCS
[ http://issues.apache.org/jira/browse/JELLY-148?page=comments#action_54713 ]
dion gillard commented on JELLY-148:
I have applied the patches with some small changes:
- I've moved the invokeNestedTagsOfType(WeakReferenceWrapperScript, Class,
Similar but separate sounds good to me.
Stephen
- Original Message -
From: Eric Pugh [EMAIL PROTECTED]
Okay.. I will go ahead and make the changes.. I think, so that you don't
have to check out both, that they are seperate. But, they should still be
pretty simiar in terms of what
I was just going to suggest that.
-Original Message-
From: Dion Gillard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 27, 2004 10:38 AM
To: Jakarta Commons Developers List
Subject: Re: [jelly] interim release for testing memory use?
How about after applying the memory leak patch
to the people of thinking of releaseing email:
I think a lot more work is in net's smtp package such as simple emailer.
So, maybe build on that,that is a superset.
just in case you missed it.
.V
-
To unsubscribe, e-mail: [EMAIL
I have to say that I'm not so thrilled with LoopTagStatus in the head
version of ForEachTag.
I know that it's the standard but it adds yet another library as a
dependency, which is pretty annoying for embedded jelly.
I forget, why not use a clone with identical methods?
Hans
psteitz 2004/10/27 20:02:34
Modified:math/src/test/org/apache/commons/math/linear
MatrixUtilsTest.java
Log:
Removed empty loop.
Revision ChangesPath
1.3 +1 -4
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31932.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31933.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31933.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31933.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31933.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
52 matches
Mail list logo
