Hi,
I have a small proposal.
Usage scenario is as follows.
One generates a char array of data using some process and then
immediately this is consumed by another process.
There are two ways of doing the same now.
1. Use a CharArrayWriter to accumulate the data generated in the first
Ceki =?iso-8859-1?Q?G=FClc=FC?= [EMAIL PROTECTED] writes:
Log4j is slowly migrating to a model where there will be only a single
log4j.jar installed per Application Server. This single copy will be
installed under the ./common/lib or ./lib/ directories. See [1, 2, 3] for
further details.
This
Charles Daniels [EMAIL PROTECTED] writes:
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 26, 2004 11:24 AM
To: commons-dev@jakarta.apache.org
Subject: commons-logging auto-detection WAS: [logging]
Enterprise Common Logging... dare we say 2.0?
At 09:55 AM 12/27/2004, Henning P. Schmiedehausen wrote:
Ceki =?iso-8859-1?Q?G=FClc=FC?= [EMAIL PROTECTED] writes:
Log4j is slowly migrating to a model where there will be only a single
log4j.jar installed per Application Server. This single copy will be
installed under the ./common/lib or ./lib/
At 03:05 AM 12/27/2004, Charles Daniels wrote:
If I understand the JCL discovery mechanism correctly, it actually
should work just fine in the scenario you describe above. For it to
work, you would not set the org.apache.commons.logging.LogFactory system
property, because, as you pointed out,
roxspring2004/12/27 03:55:12
Modified:cli/src/test/org/apache/commons/cli2 CLITestCase.java
Log:
CLITestCase is now abstract to stop eclipse 3.1 complaining about it having
no tests
Revision ChangesPath
1.3 +1 -1
roxspring2004/12/27 04:42:38
Modified:cli/src/java/org/apache/commons/cli PosixParser.java
Added: cli/src/test/org/apache/commons/cli LongOptionWithShort.java
ArgumentIsOptionTest.java
Log:
Stops the PosixParser from bursting options unecessarily,
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=32525.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
roxspring2004/12/27 05:11:39
Modified:cli/src/test/org/apache/commons/cli2/jdepend
JDependTest.java
cli/src/java/org/apache/commons/cli Parser.java
cli/src/test/org/apache/commons/cli2
CommandLineTestCase.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=25044.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
roxspring2004/12/27 05:21:17
Modified:cli/src/java/org/apache/commons/cli Parser.java
Log:
Recommitted with the fix applied not commented out (whoops)
PR: 25044
Revision ChangesPath
1.17 +2 -3
jakarta-commons/cli/src/java/org/apache/commons/cli/Parser.java
roxspring2004/12/27 05:33:48
Modified:cli/src/test/org/apache/commons/cli BugsTest.java
Log:
Added test to demonstrate the 27635 has been fixed
PR: 27635
Revision ChangesPath
1.20 +69 -0
jakarta-commons/cli/src/test/org/apache/commons/cli/BugsTest.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=27635.
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=23515.
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=32533.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
roxspring2004/12/27 06:35:36
Modified:cli/src/test/org/apache/commons/cli BugsTest.java
cli/src/java/org/apache/commons/cli Parser.java
Log:
When extracting option values from properties, options with a single argument
can now be processed successfully.
BR:
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=31148.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
roxspring2004/12/27 06:51:38
Modified:cli/src/test/org/apache/commons/cli BugsTest.java
cli/src/java/org/apache/commons/cli HelpFormatter.java
Log:
Line separator as first char for helpformatter footer and header no longer
throws exception
BR: 21215
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=21215.
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=25044.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
roxspring2004/12/27 07:25:53
Modified:cli/src/test/org/apache/commons/cli BugsTest.java
Log:
Added test to demonstrate fix of 19383
BR: 19383
Revision ChangesPath
1.23 +18 -0
jakarta-commons/cli/src/test/org/apache/commons/cli/BugsTest.java
Index:
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=19383.
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=17662.
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=25018.
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=24045.
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=24040.
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=24039.
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=21304.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Mon, 27 Dec 2004 12:49:45 +0100, Ceki Gülcü [EMAIL PROTECTED] wrote:
At 03:05 AM 12/27/2004, Charles Daniels wrote:
If I understand the JCL discovery mechanism correctly, it actually
should work just fine in the scenario you describe above. For it to
work, you would not set the
roxspring2004/12/27 09:41:28
Modified:cli/xdocs/examples ant.xml
cli/src/test/org/apache/commons/cli2 DocumentationTest.java
Log:
Documented ant example
Revision ChangesPath
1.2 +266 -1jakarta-commons/cli/xdocs/examples/ant.xml
Index:
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=31464.
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=31284.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
roxspring2004/12/27 10:17:06
Modified:cli/xdocs/examples index.xml
Log:
Added examples overview documentation
Revision ChangesPath
1.2 +14 -1 jakarta-commons/cli/xdocs/examples/index.xml
Index: index.xml
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=32851.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Ceki Gülcü [EMAIL PROTECTED] wrote on 12/27/2004 05:49:45 AM:
At 03:05 AM 12/27/2004, Charles Daniels wrote:
If I understand the JCL discovery mechanism correctly, it actually
should work just fine in the scenario you describe above. For it to
work, you would not set the
Henning P. Schmiedehausen [EMAIL PROTECTED] wrote on 12/27/2004
02:57:45 AM:
Charles Daniels [EMAIL PROTECTED] writes:
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 26, 2004 11:24 AM
To: commons-dev@jakarta.apache.org
Subject:
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=24039.
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=24040.
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=24045.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
On Mon, 27 Dec 2004 12:41:56 -0600, Richard Sitze [EMAIL PROTECTED] wrote:
Ceki Gülcü [EMAIL PROTECTED] wrote on 12/27/2004 05:49:45 AM:
At 03:05 AM 12/27/2004, Charles Daniels wrote:
If I understand the JCL discovery mechanism correctly, it actually
should work just fine in the
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=31151.
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=32533.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Ceki Gülcü wrote:
At 03:05 AM 12/27/2004, Charles Daniels wrote:
If I understand the JCL discovery mechanism correctly, it actually
should work just fine in the scenario you describe above. For it to
work, you would not set the org.apache.commons.logging.LogFactory system
property, because, as
Martin Cooper [EMAIL PROTECTED] wrote on 12/27/2004 01:07:28 PM:
On Mon, 27 Dec 2004 12:41:56 -0600, Richard Sitze [EMAIL PROTECTED]
wrote:
Ceki Gülcü [EMAIL PROTECTED] wrote on 12/27/2004 05:49:45 AM:
At 03:05 AM 12/27/2004, Charles Daniels wrote:
If I understand the JCL
Not a huge issue for things like Lang which have no dependencies, but
for other things like Digester I think it would be a lot better if the
binary tar.gz contained the jars it depends on?
So when I download digester-1.6, the tar.gz contains jars for
logging-1.0.3 and beanutils-1.7. We're not
Henri Yandell wrote:
Not a huge issue for things like Lang which have no dependencies, but
for other things like Digester I think it would be a lot better if the
binary tar.gz contained the jars it depends on?
Just my HO, but to me that defeats the purpose of
ibiblio/java-repository. It also
roxspring2004/12/27 14:22:02
Modified:cli project.properties
Log:
Force 1.3 compatibility even when compiling under 5.0
Revision ChangesPath
1.12 +5 -0 jakarta-commons/cli/project.properties
Index: project.properties
On Mon, 27 Dec 2004 15:14:36 -0500, Phil Steitz [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
Not a huge issue for things like Lang which have no dependencies, but
for other things like Digester I think it would be a lot better if the
binary tar.gz contained the jars it depends on?
Just
I am with Henri here...
Oliver
On Mon, 27 Dec 2004 17:36:02 -0500, Henri Yandell [EMAIL PROTECTED] wrote:
On Mon, 27 Dec 2004 15:14:36 -0500, Phil Steitz [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
Not a huge issue for things like Lang which have no dependencies, but
for other things
Henri Yandell wrote:
On Mon, 27 Dec 2004 15:14:36 -0500, Phil Steitz [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
Not a huge issue for things like Lang which have no dependencies, but
for other things like Digester I think it would be a lot better if the
binary tar.gz contained the jars it
Matt,
JCL exists mainly for the purpose of libraries wishing to *integrate*
with the logging API chosen by the user by deferring the selection of
the logging impl to runtime. The author of library net.sf.morph
probably does *not* wish to impose any logging related property on the
end-user.
It would certainly be helpful to our users to include the dependencies in
the distro. Otherwise, it's like trying to drive a car without the
wheels.
David
--- Henri Yandell [EMAIL PROTECTED] wrote:
Not a huge issue for things like Lang which have no dependencies, but
for other things like
I'm +1 to Henri's idea for this reason:
When I'm using a package that requires other jars, I typically install the
package on my development platform way ahead of the time when I'll be running
maven. On some projects I never even run maven on the development box. Having
the dependent jars as
At 2004-12-16 16:51:31, Richard Sitze wrote:
I do not advocate a fail-on-no-config or fail-on-ambiguous-config.
I advocate a *warn* or *error* on either, using the simple default logger.
The warning will be visible on the console, which suffices for my
immediate concerns. How that
On Mon, 27 Dec 2004 16:38:03 -0500, Henri Yandell [EMAIL PROTECTED] wrote:
Not a huge issue for things like Lang which have no dependencies, but
for other things like Digester I think it would be a lot better if the
binary tar.gz contained the jars it depends on?
So when I download
On 2004-12-16 18:09:36, Richard Sitze wrote:
ok, without going back to review exactly what I said in an earlier note, I
had in mind something like:
commons-logging-core.jar - core interface factory class, NO config
commons-logging.jar- core + all helpers, NO config
I think often JCL will be used as you describe, but not always.
For example, let's say I am developing a component that monitors
database activity and monitors usage statistics (this is a hypothetical
example). The main purpose of this component is to log messages to be
processed later by a
polx2004/12/27 17:39:23
Modified:jelly/src/java/org/apache/commons/jelly/impl
StaticTagScript.java TagScript.java
jelly/src/java/org/apache/commons/jelly JellyContext.java
polx2004/12/27 17:46:36
Modified:jelly/src/test/org/apache/commons/jelly/core
BaseMemoryLeakTest.java
Log:
The tagHolderMap size was reported way too often...
paul
Revision ChangesPath
1.2 +5 -5
The test is failing for me. Is that to be expected?
[EMAIL PROTECTED] wrote:
polx2004/12/27 17:39:23
Modified:jelly/src/java/org/apache/commons/jelly/impl
StaticTagScript.java TagScript.java
jelly/src/java/org/apache/commons/jelly JellyContext.java
brett 2004/12/27 17:59:41
Modified:jellyproject.xml
jelly/jelly-tags/xml project.xml
Log:
bump version
Revision ChangesPath
1.158 +1 -1 jakarta-commons/jelly/project.xml
Index: project.xml
I just updated the Jelly dependency on Maven's CVS HEAD from beta-4
(which I verified as working) to the latest and got a failure. Going
back, I found the same problem with Jelly RC1.
The call to output.flush() currently on line 242 of TagScript.java is
throwing a NullPointerException. Any
It appears the call to output.flush() was added and output was always null.
I've added an if(output !=null) around the flush call - can someone let
me know if this isn't a valid state and requires further investigation.
THanks,
Brett
Brett Porter wrote:
I just updated the Jelly dependency on
On Mon, 27 Dec 2004 15:48:00 -0800, Martin Cooper [EMAIL PROTECTED] wrote:
Not me. Doing this will lead to people having multiple copies of
various component jars lying around on their disks, and will
unnecessarily increase the amount of stuff that people need to
download.
Definitely
Rob,
Thanks for applying all of the patches and getting CLI into shape. I
will supply a test case for 32533. I have been working on an XMLBuilder
that uses an XML document to describe Options, Arguements, and Groups.
Hopefully it will be useful to CLI. While working on this I found that
not all
brett 2004/12/27 20:07:34
Modified:jelly/src/java/org/apache/commons/jelly/impl TagScript.java
Log:
allow output to be null
Revision ChangesPath
1.48 +4 -2
jakarta-commons/jelly/src/java/org/apache/commons/jelly/impl/TagScript.java
Index: TagScript.java
This seems fine.
On Tue, 28 Dec 2004 13:48:22 +1100, Brett Porter [EMAIL PROTECTED] wrote:
It appears the call to output.flush() was added and output was always null.
I've added an if(output !=null) around the flush call - can someone let
me know if this isn't a valid state and requires
67 matches
Mail list logo
