baliuka 2003/03/01 01:55:07
Modified:logging STATUS.html
logging/src/java/org/apache/commons/logging LogFactory.java
logging/src/java/org/apache/commons/logging/impl
LogFactoryImpl.java
Added:
I now went into the ant taglib sourcecode, to track down the problem of
[jelly] problem: setting Map property on bean?
http://www.mail-archive.com/[EMAIL PROTECTED]/msg17993.html
I found out that there are two bugs in there:
1. any non-string attribute is converted to string:
rdonkin 2003/03/01 03:23:14
Modified:betwixt project.xml
Log:
Fixed site:deploy
Revision ChangesPath
1.26 +3 -0 jakarta-commons/betwixt/project.xml
Index: project.xml
===
RCS file:
rdonkin 2003/03/01 03:39:45
Modified:digester build.xml
digester/src/conf MANIFEST.MF
Log:
Preparations for 1.4.1 release
Revision ChangesPath
1.37 +2 -2 jakarta-commons/digester/build.xml
Index: build.xml
If you are going to include the entry ending in the same regular expression that you
use to break the entries down you either have to
1) parse the whole thing as you are breaking apart the entries, essentially doing away
with the idea of not creating the FTPFile entries right away
OR
2) parse
That was easy enough.
I added the ORO dependency back in (and also an entry in the get-deps target to pull
it in) and all those problems went away.
However, I then found, that with moving the tests into src/test as I had planned to
do, simply having junit brought in through maven doesn't fully
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17043.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
While I am a committer in the commons I've never worked with the collections
project before so I thought I'd float this idea before committing anything.
I have developed a useful queue implementation that allows threads to
communicate to each other. The queue methods block when the queue is
Steve I never had these issues when the ftp2 code was in the source tree.
The xml-parsing jars should be present when the test goal is run, we never had that
dependency in the POM.
Also you shouldn't be modifying the ant build file by hand, but
instead generate a new one with maven:
maven ant
Steve Cohen [EMAIL PROTECTED] writes:
If you are going to include the entry ending in the same regular
expression that you use to break the entries down you either have to
1) parse the whole thing as you are breaking apart the entries,
essentially doing away with the idea of not creating
I guess that can work. Perhaps the simple regex for could merely look for an
expression in parentheses to delimit entries, assuming that every entry really does
end that way. Even the closing parenthesis might be enough to key off. But we'd need
to find some real-world sites or a good spec
Jeff - I hadn't known that I wasn't supposed to touch build.xml directly. I didn't
know maven could generate it for me. That's a cool feature. Simply adding oro to the
dependency list as you indicated does get it into the build file and allows the
project to build.
However, the xml-parsing
Does using maven fail running the tests also?
maven java:jar
There may be a problem with the ant build.xml generation. If using
maven for builds can get you buy for now, once you check in I'll try
to see if maven's ant plugin needs to be altered. Otherwise if you
don't/can't use maven for
Looking further into it, Jeff, I find in
http://jakarta.apache.org/turbine/maven/reference/user-guide.html#POM%20Processing
that
The properties files in Maven are processed in the following order:
${maven.home}/bin/driver.properties
${project.home}/project.properties
Whoa, that works! I had been running simply
ant test
so maven java:jar works
but
ant test
doesn't. I think there IS a problem with the ant build.xml generation.
Oh well, at least I am on the right track. This maven stuff is mostly pretty new to
me.
-Original Message-
From:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14120.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=14759.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Thu, 2003-02-27 at 21:29, Daniel Walsh wrote:
What library are you using to parse 'multipart/form-data'
formatted requests?
We actually have our own classes to parse a multipart/form-data formatted
request. I guess they could be a bit outdated at this point, or possible
never were
Ross,
Currently HTTP/1.0 is supported on per request (method) basis. We
realize this is an architectural deficiently and are planning to support
HTTP versioning on per connection basis in the future
Currently HttpCliet can be configured to fall back onto HTTP/1.0 in the
following way:
HttpClient
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17563.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=17563.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=17563.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=17563.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hey after a full week it works!! The server would not accept a HTTP/1.1
post. Setting each Get or Post Method to HTTP/1.0 works like a dream! I
didn't notice that function tucked into the MethodBase. Thanks for all your
help Oleg with this and all my other questions. I would love to buy you a
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17569.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=17569.
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://nagoya.apache.org/bugzilla/show_bug.cgi?id=17569.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
27 matches
Mail list logo
