To whom it may engage...
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-collections has an issue affecting its community integration.
This issue
http://issues.apache.org/jira/browse/JELLY
as given in the website.
paul
Le 24 mars 05, à 06:22, A Leg a écrit :
Hi Paul
It can sound stupid but I don't know how to submit an issue.
Can you guide me or point to a guide?
Andre
Paul Libbrecht wrote:
Dear Andre,
can you submit an issue for this and
SOunds good. I do think if we go for 1.4 though, we should probably include
some of the smaller issues in BZ that would be easy to fix as well, and maybe
get some of those cleaned up. IIRC, most of the smaller bugs include patches or
source listings.
SOunds good. I do think if we go for 1.4 though, we should probably include
some of the smaller issues in BZ that would be easy to fix as well, and maybe
get some of those cleaned up. IIRC, most of the smaller bugs include patches or
source listings.
This format is from the default FTP server daemon configuration that
came with Debian:
Connected to stf.
220 stf FTP server (Version 6.4/OpenBSD/Linux-ftpd-0.17) ready.
Name (stf:neeme): neeme
331 Password required for neeme.
Password:
230- Linux stf 2.6.11 #1 SMP Wed Mar 2 14:08:21 CET 2005 i686
Well, as I wrote in my previous email, timezone setting does help, but I
would like to take it one step further.
When just using plain timezone difference calculation, you are still
comparing server time to the local time and those usually are out-of-sync.
I would like to have it 100% precise:
Sorry I didn't read far enough.
This is more properly a discussion for the Ant list. All we handle here
is the raw FTP. Ant's FTP task depends on commons-net, though, and
until we release the timezone-using version of commons-net, ant will not
have the tools to do what you need.
I may be
Very good news that Debian is going to an all-numeric date format.
After mucking around in this mess for a couple of years, I often
wondered why standard unix ftp bothered with the abbreviations at all.
NT does not and does unix really want to take a back seat to NT in
matters such as this?
Rory Winston wrote:
SOunds good. I do think if we go for 1.4 though, we should probably include
some of the smaller issues in BZ that would be easy to fix as well, and maybe
get some of those cleaned up. IIRC, most of the smaller bugs include patches or
source listings.
Could we come to some consensus on this item in Bugzilla? I have already
put my $0.02 in as a comment. But, this one is somewhat easy either way we
go with it. If the decision is to not include it, then that's a no-brainer.
If we decide to include it, then it's not much effort to do that
I meant when you did the last release, of course.
Steve Cohen wrote:
Rory Winston wrote:
SOunds good. I do think if we go for 1.4 though, we should probably
include some of the smaller issues in BZ that would be easy to fix as
well, and maybe get some of those cleaned up. IIRC, most of the
--- James Carman [EMAIL PROTECTED] wrote:
Could we come to some consensus on this item in
Bugzilla? I have already
put my $0.02 in as a comment. But, this one is
somewhat easy either way we
go with it. If the decision is to not include it,
then that's a no-brainer.
If we decide to
ok, clear enough.
I'll look into the source code of the ftp task and play around with it a
bit.
Another suggestion for that task is to allow retry-in-case-of-failure,
not just abort or ignore as in the current version. But I'll take those
issues up on Ant list.
My use case is simple: I'm using
Ok, then I'm a +0. I wouldn't want to veto it. I guess I should read up on
the voting rules. I didn't realize that a -1 was so powerful. Then again,
I'm not an official committer yet, so my vote doesn't count anyway. :-)
Could we try to come up with a more valid use case, then? I don't see
The last release was from CVS. The docs were (are? - haven't checked) very
CVS-centric. I haven't attmepted to try a release from SVN yet, however I
presume it wouldn't be too arduous a task, given the ease of substitutability
between CVS/SVN. I fixed the issue with missing JUnit tests - they
Hello,
I was looking for a generics-capable version of commons-collections,
however everything I could find were to small threads on the mailing list.
Instead of complaining I decided to work on it myself.
The first thing I did was creating a generics-version of the various
interfaces provided
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=32748.
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=34165.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://collections15.sourceforge.net/
michael
On Thu, 24 Mar 2005, Thomas Klaeger wrote:
Hello,
I was looking for a generics-capable version of commons-collections,
however everything I could find were to small threads on the mailing list.
Instead of complaining I decided to work on
Hello Thomas,
You're right. There was a brief discussion about a Java 5.0 port of
collections. The upshot was the project that Michael has pointed out on
SourceForge. There are two people working on this at the moment - myself
and Mauro Franceschini. After an initial bout of work on this
Matthias Wessendorf wrote:
Hi Kevin,
sorry for bothering you, but I started looking at sources for
[feedparser] and saw lot's of import java.xxx.*
and also unused importstatements.
Are you interessted in structuring them?
I liked the remove unused import statements patch. How did you find
this
After fixing a packaging issue with NOTICE.txt and a few minor updates I
have created the third release candidate of the commons-configuration
1.1 release.
The files are available for inspection at
http://www.apache.org/~oheger/commons-configuration-1.1rc3
The name of the tag is
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=34140.
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=34165.
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=34142.
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=34142.
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=34103.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi,
Over on the log4j mailing list, we've been discussing an interesting idea
for the next-generation commons-logging-type component, and wanted to run
the idea by the commons-dev crew for feedback. This is just informal at
this point, soliciting opinions.
First, as background:
-
Hi,
Over on the log4j mailing list, weve been discussing an interesting idea for
the next-generation commons-logging-type component, and wanted to run the idea
by the commons-dev crew for feedback. This is just informal at this point,
soliciting opinions.
First, as background:
- Jakarta
Author: oheger
Date: Thu Mar 24 11:38:52 2005
New Revision: 158940
URL: http://svn.apache.org/viewcvs?view=revrev=158940
Log:
Tag for 1.1RC3
Added:
jakarta/commons/proper/configuration/tags/CONFIGURATION_1_1RC3/
- copied from r158939, jakarta/commons/proper/configuration/trunk/
On Thu, 24 Mar 2005 14:37:28 -0500, Yoav Shapira [EMAIL PROTECTED] wrote:
Hi,
Over on the log4j mailing list, we've been discussing an interesting idea
for the next-generation commons-logging-type component, and wanted to run
the idea by the commons-dev crew for feedback. This is just
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=33190.
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=34165.
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=34171.
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=34142.
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=34171.
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=30686.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
4-6 weeks sounds reasonable.
Rory Winston wrote:
The last release was from CVS. The docs were (are? - haven't checked) very
CVS-centric. I haven't attmepted to try a release from SVN yet, however I
presume it wouldn't be too arduous a task, given the ease of substitutability
between CVS/SVN. I
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=34173.
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=34173.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
James Carman wrote:
Could we try to come up with a more valid use case, then? I don't see
including something if we can't even fathom a reasonable use case for it.
Off the top of my head, I can't think of a use for this technique. That
doesn't mean there isn't one. Maybe I've just never
Rory Winston writes:
As regards a timeline, I'm also pretty swamped over the next couple of weeks (
starting a new role, etc), so it will be tight for me until then. If I do get
a chance in the next couple of weeks I will look at fixing some of the more s
traightforward issues in BZ. It would be
Hi
I post a few weeks ago a bad_record_mac error.
With Steve, Brad and Oleg help I solved it.
My appli was working good until now. I have added
((SSLSocket)socket).setEnabledProtocols(new String[] {SSLv3});
((SSLSocket)socket).setUseClientMode(true);
In my custom
43 matches
Mail list logo
