On Tue, 2005-07-05 at 11:11 +1000, Dion Gillard wrote:
Is everyone ok with me doing a distribution for 1.0-RC5 and placing it
up for public consumption on people.apache.org/~dion ?
I'm currently going through
http://jakarta.apache.org/commons/releases/prepare.html and making
sure it's all
On Sun, 2005-07-03 at 14:56 -0700, Phil Steitz wrote:
I can't see anything missing or incorrect in release contents.
Checked maven and ant builds on sun linux jdk 1.4.2_06, 08, 1.5.0_04.
Tests failed compile for me under both maven and ant using 1.3.1_14
(sun linux) with
error: compiler
On Sun, 2005-07-03 at 18:35 +0100, robert burrell donkin wrote:
The second candidate for the Betwixt 0.7 release is now available for
download (http://people.apache.org/~rdonkin/commons-betwixt/). The
documentation can be viewed online
(http://people.apache.org/~rdonkin/commons-betwixt/site/).
On Sun, 2005-07-03 at 10:28 -0700, Phil Steitz wrote:
An initial release candidate for commons-math 1.1 is available for review
here:
http://people.apache.org/~psteitz/commons-math/1-1-rc1/
Release notes, summarizing the changes from version 1.0, are here:
Hi Dion,
How are things going with the 1.0 release of email?
I see dumbster-1.6 is now on ibiblio/maven, and is compiled with java
1.3. And as far as I can see you've already addressed all of the issues
raised during the review of RC4.
Is there any other issue holding up RC5 that I could help
On Sat, 2005-07-02 at 21:29 +0200, J.Pietschmann wrote:
Simon Kitching wrote:
This is only a *compile-time* dependency.
Currently there is a single utility class provided in the standard
logging jar which can be used to avoid memory leaks when using
commons-logging in servlet
Hi Mario,
On Wed, 2005-06-29 at 21:52 +0200, Mario Ivankovits wrote:
Hi!
The commons vfs community is happy to announce the availability of
commons-vfs 1.0 RC1.
Please find the RC at
http://people.apache.org/~imario/vfs
The site can be reviewed at
On Thu, 2005-06-30 at 11:50 +0200, Ceki Gülcü wrote:
At 12:00 AM 6/30/2005, robert burrell donkin wrote:
anyone strongly object to me making the dependency on the servlet api
optional (by altering the build script)?
There are both advantages and disadvantages to each approach.
Making
On Wed, 2005-06-29 at 21:52 +0200, Mario Ivankovits wrote:
Hi!
The commons vfs community is happy to announce the availability of
commons-vfs 1.0 RC1.
Please find the RC at
http://people.apache.org/~imario/vfs
The site can be reviewed at
On Thu, 2005-06-30 at 20:02 +0200, Mario Ivankovits wrote:
Hi Simon!
Thanks for taking the time to check this all!!
Perhaps you could post your public GPG/PGP key so the signatures could
be checked too?
Did you mean the KEYS file within the distribution? Or any other place?
Either
On Tue, 2005-06-28 at 22:32 +0100, robert burrell donkin wrote:
The problem is that people won't be referring to it in the normal way,
via an import in their code (at least it's *theoretically* possible, but
I can't imagine anyone actually subclassing Log4JLogger.
IMHO we should have
Hi All,
Quite a few of the JCL unit tests need to be run with specific
classloader hierarchies set.
The current solution is to avoid running the standard
junit.textui.TestRunner class and instead run the
org.apache.commons.logging.Wrapper class which sets up any custom
classpath needed then
On Wed, 2005-06-29 at 23:00 +0100, robert burrell donkin wrote:
anyone strongly object to me making the dependency on the servlet api
optional (by altering the build script)?
I would prefer to go the other way and make all of the compile-time
dependencies mandatory.
Currently the build.xml
On Thu, 2005-06-30 at 10:02 +1200, Simon Kitching wrote:
Sorry, please make this:
If we make all compile dependencies mandatory then
People who want customised versions of commons-logging jar files with
only some classes present can then unpack the resulting jar, delete the
unwanted files
[aargh - top-posting!]
It is true that SVN HEAD has a new dependency on servletapi.jar. But I
don't think that's the problem that spikesource are reporting.
The log file shown indicates a failure to compile the optional jar.
This might have been because:
(a) the version# is now included in the
On Wed, 2005-06-29 at 17:51 -0400, Noel J. Bergman wrote:
anyone strongly object to me making the dependency
on the servlet api optional
I'd object if you DIDN'T.
This is only a *compile-time* dependency.
Currently there is a single utility class provided in the standard
logging jar which
On Wed, 2005-06-29 at 22:31 +0100, robert burrell donkin wrote:
On Wed, 2005-06-29 at 23:53 +1200, Simon Kitching wrote:
snip
What do people think about this?
big +1
Should I:
* commit this
* commit this to a branch for review
* rethink because of ...
commit it on HEAD
On Wed, 2005-06-29 at 01:38 +0200, Emmanuel Bourg wrote:
Dumb question, why do we even need a VariableResolver interface ? A
String-Object association is a common job for a Map after all. We
should be able to build a sophisticated resolver system in
[configuration] with a simple
On Tue, 2005-06-28 at 22:55 +0100, robert burrell donkin wrote:
i've been cutting a release (the first i've cut for quite a while) so i
thought it'd be a good idea to try to improve the release documentation.
i came up with some improvements to the preparation document. i've
deployed a
Hi,
I'm looking at fixing some issues with commons-logging unit tests by
adding a couple of classes that enhance junit. In one case this means
copying-and-pasting a dozen lines from junit.framework.TestSuite into a
local class.
JUnit is published under the Common Public License 1.0
On Mon, 2005-06-27 at 00:20 +0200, Dennis Lundberg wrote:
BUILD FAILED
/x1/gump/public/workspace/jakarta-commons/logging/build.xml:295:
destination directory
/x1/gump/public/workspace/jakarta-commons/logging/target/classes does not
exist or is not a directory
On Sun, 2005-06-26 at 20:56 +0100, robert burrell donkin wrote:
i think that the next release should be a 1.1 release in any case.
however, i would prefer retaining Log4JLogger so that it can be properly
deprecated.
The problem is that people won't be referring to it in the normal way,
via an
The votes to elect Brian Stansberry as a committer for
jakarta-commons-logging are as follows:
+1 Dion Gillard
+1 Phil Steitz
+1 Robert Donkin
+1 Yoav Shapira
+1 Emmanuel Bourg
+1 Henri Yandell
+1 Simon Kitching
Brian is therefore elected (Brian has indicated privately that he is
willing
On Sat, 2005-06-25 at 20:52 +0200, Stefan Bodewig wrote:
On Sat, 25 Jun 2005, Stefan Bodewig [EMAIL PROTECTED] wrote:
After that split the commons-logging project defintion in Gump into
three, one compiling against Log4J HEAD, one agains the 1.2 branch
and the third bundling up the jar.
On Sat, 2005-06-25 at 18:29 +0200, Dennis Lundberg wrote:
Here's a patch that also makes the warning messages easier to read.
Thanks Dennis; I have made the changes you suggested.
In future, could you please try to trim quoted text in reply emails to
contain only the necessary information to
On Sat, 2005-06-25 at 21:34 -0700, Phil Steitz wrote:
Before I roll an RC, I need consensus on how we should be doing this.
I see three alternatives, with the PITA level increasing in order:
1. Don't worry, be happy - just set maven.compile.target=1.3 and use
maven dist under 1.4 (or 1.5)
I'm willing to do some work on this. I'll need to see what's in lang at
the moment though...at least some of the code came originally from
Digester so I feel responsible for knocking it into shape for lang!
Cheers,
Simon
On Fri, 2005-06-24 at 06:34 -0400, Steven Caswell wrote:
Though I don't
On Fri, 2005-06-24 at 10:20 +0200, Torsten Curdt wrote:
My vote would be to just remove it. There wasn't a huge amount of
interest and if I'll be the only community on something, it's much
easier for me to have it sitting in osjava. It's always available for
the ASF if anyone is ever
On Fri, 2005-06-24 at 10:37 +0200, Mario Ivankovits wrote:
Hi!
There is one feature left I would like to add to VFS after fixing the
webdav stuff (yes Torsten, its your last bugzilla ticket). It looks like
he really need it now and so I will satisfy his wish.
But then I really will
On Wed, 2005-06-22 at 22:22 +1000, Dion Gillard wrote:
What usually goes in that for 1.0?
The changes from the most recent pre-1.0 release (ie distribution
available via the official downloads page).
Email, of course, has never made a release of any sort. However I would
still document any
On Wed, 2005-06-22 at 13:36 +, [EMAIL PROTECTED] wrote:
-siteAddressjakarta.apache.org/siteAddress
+siteAddresscvs.apache.org/siteAddress
Just for the future, there was an email discussion a little while ago,
and the general consensus (my interpretation anyway) was that
On Wed, 2005-06-22 at 13:50 +, [EMAIL PROTECTED] wrote:
Modified:
jakarta/commons/proper/email/trunk/src/java/org/apache/commons/mail/Email.java
URL:
On Thu, 2005-06-23 at 19:57 +0100, robert burrell donkin wrote:
The first release candidate for the 0.7 release of Betwixt is now
available here: http://people.apache.org/~rdonkin/commons-betwixt. The
Javadocs are available here:
http://people.apache.org/~rdonkin/commons-betwixt/site/.
This
On Fri, 2005-06-24 at 08:59 +1200, Simon Kitching wrote:
One unit test failed with Java 1.3 (debian sarge):
Testcase:
testIntrospectionTimeTypeWrite(org.apache.commons.betwixt.io.read.TestBindTimeTypeMapping):
FAILED
(Unequal node names) expected:call but was:latinName
On Fri, 2005-06-24 at 09:37 +1200, Simon Kitching wrote:
On Fri, 2005-06-24 at 08:59 +1200, Simon Kitching wrote:
One unit test failed with Java 1.3 (debian sarge):
Testcase:
testIntrospectionTimeTypeWrite(org.apache.commons.betwixt.io.read.TestBindTimeTypeMapping):
FAILED
(Unequal
On Thu, 2005-06-23 at 21:08 -0400, Henri Yandell wrote:
On 6/22/05, Torsten Curdt [EMAIL PROTECTED] wrote:
Hm... what about creating a new sandbox project for
it then?
We could move it there and then prepare the release
of commons io?
WDYT?
My vote would be to just remove it.
On Fri, 2005-06-24 at 06:22 +0100, robert burrell donkin wrote:
i'm very unhappy with the introduction of the servlet API as a full core
dependency. IIRC i stated before that this has a very detrimental effect
on dependency management tools. i strongly believe that JCL's core
dependencies need
Hi,
Currently the Log4JLogger code in svn has this horrible stuff all
through it:
if (is12) {
...
} else {
...
}
This is to handle the fact that log4j versions 1.2 and 1.3 are expected
to be binary incompatible in both directions, ie code compiled against
1.2 won't work against 1.3
[AARGH - I hate top-posting!!]
It certainly seems like email is generally ready for release.
I think one more RC and a new VOTE thread would be a good idea, as the
vote thread from december last year really can't be continued now :-).
Besides there are a few minor things that need fixing:
===
the following votes have been posted
in reply to the email on pmc:
+1 Dion Gillard
+1 Phil Steitz
+1 Robert Donkin
+1 Yoav Shapira
+1 Simon Kitching
Please add your vote.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On Mon, 2005-06-20 at 22:46 -0700, Brian Stansberry wrote:
Maybe a little bit good? ;-) With the latest JCL I
was able to remove the JBoss filter of JCL and get
logkit logging working for both webapp classes and
Tomcat's JSPServlet by following the standard steps --
On Tue, 2005-06-21 at 21:57 -0700, Brian Stansberry wrote:
Since log4j is on the classpath, they'd have to do
use
commons-logging.properties anyway.
Well, I have a patch to propose which will change
that :-)
Related to the comment you just added to
LogFactoryImpl?
Yes. I had
Hi,
Currently the Log4JLogger class has this kind of thing all through it:
if(is12) {
getLogger().log(FQCN, (Priority) Level.DEBUG, message, null );
} else {
getLogger().log(FQCN, Level.DEBUG, message, null );
}
This code is intended to deal with the fact that log4j1.3 is
Hi Brian,
On Sun, 2005-06-19 at 16:22 -0700, Brian Stansberry wrote:
Had a chance to check this out, and the problem is
because JBoss/Tomcat uses commons-logging.jar instead
of the commons-logging-api.jar used by standalone
Tomcat. When a webapp is deployed JBoss also deploys
container code
On Thu, 2005-06-16 at 23:09 -0700, Brian Stansberry wrote:
donkin wrote:
But I don't think the weakref stuff does any harm
either (as long as
there are no bugs in it!). So I'd be -0 to including
it, not -1.
If the WeakHashtable stuff is going to stay, I'm
wondering if it should
On Fri, 2005-06-17 at 02:53 -0700, Ted Husted wrote:
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-logging has
On Wed, 2005-06-15 at 10:09 -0400, Henri Yandell wrote:
http://wiki.apache.org/jakarta/JakartaBoardReport-June2005
Need subreports for:
Transaction probably needs to be added to this list.
A Transaction 1.1 release went out in early January.
Regards,
Simon
Hi All,
I can't think of much left to do on commons-logging. Perhaps it's time
to start planning for a release?
I think we should wait for log4j to get a release out the door that
supports the TRACE level. Despite debating this at great length, there
still isn't a release out that implements
On Tue, 2005-06-14 at 23:31 -0700, Brian Stansberry wrote:
Re the InvocationTargetException for LogKitLogger:
Does it actually matter whether
ExceptionInInitializerError or
InvocationTargetException occurs for LogKitLogger?
[snip]
Depends on how we resolve the issue of whether to ever
Hi All,
There are a number of awkward beanutils bugzilla entries that I would
like someone to review. I don't wish to push forward on any of these
until at least one other pair of eyes has checked my logic and agreed
with it.
The issues are:
* 23815 [setNestedProperty]
Patches committed,
Hi,
I notice that although the transaction 1.1 release is out, there is no
news item on the jakarta site. I think it would be nice to put one
there. See
http://jakarta.apache.org/commons/releases/release.html
for instructions if you need them.
Cheers,
Simon
On Tue, 2005-06-14 at 15:24 +1000, Brett Porter wrote:
Firstly, I still believe if you've got sufficient testing, this isn't
really necessary, and this discussion is getting a little carried away.
The problem is that testing is supposed to be done by the unit tests.
But the unit tests won't
On Sun, 2005-06-12 at 13:27 +1000, Brett Porter wrote:
Hi,
There are release candidates here:
http://people.apache.org/~brett/commons-jelly-1.0-RCs/
In commons-jelly-1.0-rc4.tar.gz, file bin/jelly has dos line-endings.
This means the file cannot be run:
output
[EMAIL
On Mon, 2005-06-13 at 20:37 +0530, Bindul Bhowmik wrote:
Now, to my original problem: since brutus is out of action, where do I
get nightly builds for commons-email (if it is getting built at all)?
http://cvs.apache.org/builds/jakarta-commons/nightly/
Regards,
Simon
On Tue, 2005-06-14 at 10:24 -0300, Ramiro Pereira de Magalhaes wrote:
Well, that's quite bad... :(
Isn't anyone with managing powers interested in pushing email towards
a release? I can checkout this project and start fixing anything by
myself as (if) needed but this way I'll be working
On Wed, 2005-06-15 at 01:31 -0300, Ramiro Pereira de Magalhaes wrote:
Craig,
after having some fight with the commons-email project I discovered the
problem that breaks it: you're compiling the project with the
javamail_path/lib/mailapi.jar package instead of
javamail_path/mail.jar
On Wed, 2005-06-15 at 15:18 +1000, Dion Gillard wrote:
I think it's a bit pessimistic to say it's a dead horse.
I should have some free time for email later this week
Ah .. sorry, Dion. Good to know you're still interested.
Regards,
Simon
On Sun, 2005-06-12 at 22:12 -0400, Hans Gilde wrote:
Well, targeting the 1.3 class file definition won't prevent it from using
the rt.jar in your 1.5 JDK... thus possible compiling against an API that is
in 1.3. In fact, this is not the case and I tried it... but just pointing it
out.
Just a
On Mon, 2005-06-13 at 13:12 +0100, Stephen Colebourne wrote:
--- Simon Kitching [EMAIL PROTECTED] wrote:
An option is to put something like this in the
project.properties:
maven.junit.fork=true
maven.junit.jvm=/path/to/jvm12/bin/java
The code then gets compiled with the very best
On Mon, 2005-06-13 at 13:15 +0100, Stephen Colebourne wrote:
--- Simon Kitching [EMAIL PROTECTED] wrote:
[snip theorectical example of problem using
PrintStream]
One real example is StringBuffer.append(StringBuffer)
as I said before. The problem is exactly as Simon
described, around
On Tue, 2005-06-14 at 09:59 +1000, Brett Porter wrote:
I'll also point out I have limited time to work on this now, and
starting with JavaOne I'll be away for 3 weeks - so either this is out
this week, someone else steps up to finish it, or it waits until August.
I'm not in anyway trying to
On Tue, 2005-06-14 at 13:12 +1200, Simon Kitching wrote:
And
the lack of bugzilla entries and user/development questions also implies
that Jelly is fine as-is.
umm .. the lack of Bugzilla entries is probably because Jelly uses
Jira :-(.
Jira has quite a few bug entries (73).
It looks like
So looking at possible solutions...
The current situation is:
interface Foo
class Impl implements Foo
Is it possible to do this?
interface ExtendedFoo implements Foo
class Impl implements ExtendedFoo
In this way, Foo doesn't change, but new code can pass objects around as
ExtendedFoo in
Hi All,
Version 1.7 of commons-digester has now been released.
This is a minor bugfix and maintenance release. A few small features
have been added. New projects are encouraged to use this release of
digester, but there is no urgency for existing projects to upgrade;
Digester 1.6 has proven to
Hi All,
Having now done a release, I have a couple of suggestions/questions
about the release procedure.
===
The dist directories currently have symbolic links named ..current..
that point to the actual files in the binary and source subdirs.
Is there actually any justification for keeping
On Sun, 2005-06-12 at 18:32 -0700, Martin Cooper wrote:
On 6/12/05, Simon Kitching [EMAIL PROTECTED] wrote:
Hi All,
Having now done a release, I have a couple of suggestions/questions
about the release procedure.
===
The dist directories currently have symbolic links named
, was third parties implementation broken because of this interface
change? No. The Stub provides continued backward compatibility for the
thirdparty implementation.
-Mark
Stephen Colebourne wrote:
Simon Kitching wrote:
So looking at possible solutions...
The current situation
On Mon, 2005-06-13 at 14:47 +1200, Simon Kitching wrote:
Hi Mark,
In the example below, I would regard this change as being an
incompatible change anyway. Code using the new API isn't compatible with
code implementing the old API because an exception can be thrown when
invoking a normal
On Mon, 2005-06-13 at 13:08 +1000, Brett Porter wrote:
Hi Hans,
This is exactly what I meant. Thanks for confirming that it has worked
this time on JDK 1.3. The question I'm still uncertain of is whether it
is possible that JDK 1.5, with -target 1.3 but it's own rt.jar, would
ever
On Sat, 2005-06-11 at 07:41 +, [EMAIL PROTECTED] wrote:
--- jakarta/commons/proper/jelly/trunk/project.properties (original)
+++ jakarta/commons/proper/jelly/trunk/project.properties Sat Jun 11 00:41:11
2005
@@ -24,6 +24,8 @@
maven.compile.debug = on
maven.compile.optimize = off
On Sat, 2005-06-11 at 10:25 +0100, Stephen Colebourne wrote:
Some jar files are build with JDK1.5 (according to the manifest).
commons-jelly-1.0.jar/commons-jelly-tags-xml-1.1.jar.
Is that a problem if maven.compile.target is set? I wouldn't think so...
Another nice to have would be the
On Sat, 2005-06-11 at 18:45 +1000, Brett Porter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
There are release candidates here:
http://people.apache.org/~brett/commons-jelly-1.0-RCs/
Hi Brett,
Here are some comments..hope they are useful.
After unpacking the
On Sat, 2005-06-11 at 18:45 +1000, Brett Porter wrote:
The site is not changed, so I have not published a version to my home
directory. However, if the release is approved I will go through and
change references to release candidates, download links, etc.
Ok. Please don't forget to update
On Sat, 2005-06-11 at 19:50 -0400, Steven Caswell wrote:
Just one question about the jar:
The manifest indicates the jar was built with JDK 1.5. Does this
present any issues with running against previous Java versions?
File project.properties contains this:
# generate .class files that can
Hi All,
The vote to release commons-digester 1.7 has passed:
+1 Phil Steitz
+1 Steven Caswell
+1 Simon Kitching
I will therefore be posting the official release shortly.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL
votes so we can get this
release out the door. So *please* take a few minutes to check that the
right procedures have been followed, then add your +1 vote so the
release can be completed.
Thanks,
Simon
On Wed, 2005-06-08 at 12:19 +1200, Simon Kitching wrote:
Hi,
As we've had two release
On Thu, 2005-06-09 at 21:24 +0100, robert burrell donkin wrote:
the latest betwixt code contains a number of (relatively minor) semantic
incompatibilities with the last release as well as quite a number of new
features. after recent discussions, i think it best to release the code
as 1.7
On Thu, 2005-06-09 at 16:03 -0400, Steven Caswell wrote:
I'm planning to cut the 2.1 release this weekend if there aren't any -1s
before then, and I've never done one of these, so I'm wondering if there is
any doc anywhere I can look at for steps/guidelines/etc. Failing that, is
there
On Thu, 2005-06-09 at 20:08 +0100, robert burrell donkin wrote:
On Wed, 2005-06-08 at 15:08 +1200, Simon Kitching wrote:
On Mon, 2005-06-06 at 22:35 +0100, robert burrell donkin wrote:
The first public release candidate (RC3) for Betwixt 0.6.1 is now
available for download:
http
On Thu, 2005-06-09 at 20:29 +0100, robert burrell donkin wrote:
On Thu, 2005-06-09 at 10:41 +1200, Simon Kitching wrote:
On Wed, 2005-06-08 at 22:21 +0100, robert burrell donkin wrote:
===
Maven reports:
I would suggest disabling this report. Firstly, a log of the last 30
Umm.. Brent, did you follow the official procedure for creating this
release?
I don't remember seeing any VOTE thread on this, and it is definitely
*not* permitted to perform a release without an official VOTE thread
having been passed. There's a whole lot of other stuff that is certainly
On Wed, 2005-06-08 at 22:21 +0100, robert burrell donkin wrote:
===
Maven reports:
I would suggest disabling this report. Firstly, a log of the last 30
days isn't of much use. And secondly, due to the import into SVN of
back-dated CVS changes, date-based selection on the apache
On Wed, 2005-06-08 at 23:22 +0100, robert burrell donkin wrote:
=== other
The src distro builds fine with Java1.5 on Linux (debian 3.1).
Unfortunately, there are ?? unit test failures when using java 1.3.1:
TEST
On Thu, 2005-06-09 at 09:09 +1000, Brett Porter wrote:
Sorry.
I saw square brackets, release and +1's from the jelly developers and
saw that as a green light. My mistake.
First, I should point out that all stuff below is *just my personal
opinion*.
The only emails I can find about
On Mon, 2005-06-06 at 22:35 +0100, robert burrell donkin wrote:
The first public release candidate (RC3) for Betwixt 0.6.1 is now
available for download:
http://people.apache.org/~rdonkin/commons-betwixt/. Please check and
report any problems ASAP.
Hi Robert,
Here's some stuff re the
Hi,
As we've had two release candidates, and there have been no major issues
raised, I would appreciate your votes to approve an official release.
Phil Steitz raised a couple of minor points for RC2 that have been
addressed; the changes since RC2 are:
* removed tabs from unit-test and example
On Mon, 2005-06-06 at 22:35 +0100, robert burrell donkin wrote:
The first public release candidate (RC3) for Betwixt 0.6.1 is now
available for download:
http://people.apache.org/~rdonkin/commons-betwixt/. Please check and
report any problems ASAP.
I've run clirr to analyse the differences
Hi Phil,
Thanks very much for having a look at this.
*** Reports from anyone else would still be very welcome***
On Sun, 2005-06-05 at 15:50 -0400, Phil Steitz wrote:
* download and unpack the src and bin distributions, and
verify that the contents are all as expected
Looks good.
On Mon, 2005-06-06 at 19:40 -0400, Steven Caswell wrote:
Now that RC8 (http://www.apache.org/~stevencaswell/commons-lang-2.1) has
been up for a few days with no issues, I propose it becomes the 2.1 release.
+1
-
To
Hi,
As you may have seen from the commit email, I have created a branch
allow-flawed. This contains an attempt to implement fallback as
described in this bugzilla entry:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34661
The code in this branch passes all unit tests, and 100% of the
On Fri, 2005-06-03 at 07:11 -0400, James Carman wrote:
All,
This may be a dumb question, but how do we generate the emails that are sent
when someone checks in a change to our CVS repository? I was thinking of
maybe instituting something like that at work. Is it pretty easy to set up?
On Wed, 2005-06-01 at 23:12 -0700, Brian Stansberry wrote:
snip
from:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34661
--- Additional Comments From
[EMAIL PROTECTED] 2005-05-31 07:49 ---
I still don't understand that bit with the else
around the log4j discovery.
Hi Phil/Ryan,
In general this proposal sounds like an excellent idea to me.
I expect the mathematics community is the sort that would be willing to
form a self-supporting community around a tool once it has shown itself
to be useable. So the issues of having developers around to
Hi All,
Release Candidate #2 of commons-digester-1.7 is now available at:
http://people.apache.org/~skitching/digester-1.7/
It would be greatly appreciated if interested parties would
* download and test the jar file with their applications
* download and unpack the src and bin
On Wed, 2005-06-01 at 01:55 -0400, Gary Gregory wrote:
Simon:
You probably need to copy junit.jar to %ANT_HOME%\lib
Yep, that will make things work. But I'm questioning whether it is
reasonable for the lang 2.1 build process to require users to do this.
What is wrong with the old way of
On Tue, 2005-05-31 at 22:38 -0400, Steven Caswell wrote:
Commons-lang 2.1 release candidate 8 is available at
http://www.apache.org/~stevencaswell/commons-lang-2.1/
Primary change is Gary's working out the oddball build and class loading
issue that only seems to happen on Windows XP (SP2)
On Tue, 2005-05-31 at 17:59 +1200, Simon Kitching wrote:
The test doesn't set up its own clean classpath?! I thought that was
what the AppClassLoader private class was all about - though of course
it's hard to tell as there aren't any comments on it.
If the unit test doesn't properly set up
Hi All,
Release Candidate #1 of commons-digester-1.7 is now available at:
http://people.apache.org/~skitching/digester-1.7/
It would be greatly appreciated if interested parties would
* download and test the jar file with their applications
* download and unpack the src and bin
On Tue, 2005-05-31 at 15:09 -0700, Dakota Jack wrote:
Something must be missing from this thread. All we got from Simon was
this reference to a WebDav project. How that relates to what you are
doing is not clear to me, Frank. Simon must have sent something else
in addition that you have not
And +1 on a separate commons for webapp stuff from me too.
Having projects in this commons is best done when there are already a
fair number of commons committers who would be interested in
contributing, or at least keeping an eye on the new project.
But there are many developers here (like me)
301 - 400 of 787 matches
Mail list logo
