[X] +1 - Fix it
[ ] -1 - Send a patch
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I've run into this exact same problem with Xerces-J 2.x (not a Jakarta
project but it is a major "world-wide" jar).
The problem I had was this: A 3rd party company that we partner with
uses Xerces, fair enough and so does our software. When using this 3rd
party s/w we are stuck with the older vers
Packages look like
com.some_domain.org.apache.xerces...
gg
-Original Message-
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 16, 2004 1:44 PM
To: Jakarta Commons Developers List
Subject: Re: AW: [proposal] avoiding jar version nightmares
On Thu, 16 Dec 2004
"Sorry for the silence from me. As I've probably said a million times,
baby happened."
Congratulations!
"Gary seems to have taken care of
http://issues.apache.org/bugzilla/show_bug.cgi?id=32625. Is it ready
for closure Gary? Despite Matt Blum's comment on a work-around, it
still sounds like a fin
Hello,
First look at what is in CVS or the nightly-build. For example, in CVS
now:
SystemUtils.USER_COUNTRY : String
SystemUtils.USER_DIR : String
SystemUtils.USER_HOME : String
SystemUtils.USER_LANGUAGE : String
SystemUtils.USER_NAME : String
SystemUtils.USER_TIMEZONE : String
Then you should r
Hello,
I notice that [IO] 1.1-dev in CVS must be compiled with Java 1.4. Is
this intentional? It was not the case for 1.0.
This locks my real work out from using it since we have customers that
still have 1.3.1 as their requirement.
Gary
+1
Gary
-Original Message-
From: robert burrell donkin
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 2:49 PM
To: Jakarta Commons Developers List
Subject: [logging][PROPOSAL] 1.0.5 release
IMO the first step before any work can begin on any improvements is to
release the c
I've not installed Subclipse yet but being force to use a command-line
interface would be a great disincentive for me.
Gary
-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 19, 2005 5:12 PM
To: Jakarta Commons Developers List
Subject: Re: [al
-0
I'd prefer to wait until we know Eclipse support (Subclipse or
otherwise) is on par with CVS support.
Gary
-Original Message-
From: Tim O'Brien [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 22, 2005 10:31 AM
To: Jakarta Commons Developers List
Subject: [all][VOTE] svn migration
Hello Ezra:
Yes, it would be great if you could provide a unit test patch when you
submit a bug report. This is more effective than me or another codec
volunteer recreating the issue from scratch.
It would be best to for you to create a Bugzilla issue when you want to
report an issue in ord
Hello All:
I just noticed it's been about a month since the last 2.1 ponderings.
Where do we stand now?
Curious,
Gary
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Friday, December 17, 2004 7:22 PM
To: Jakarta Commons Developers List
Subject: [lang] 2.1...
Sorr
Richard:
You might find the attached GIF handy ;-)
Gary
-Original Message-
From: Richard Sitze [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 25, 2005 11:41 AM
To: Jakarta Commons Developers List
Subject: Re: [logging] Enterprise Common Logging... dare we say 2.0?
Well now... that IS
Waiting after 2.1: +1.
"Release early, release often" ;-)
Gary
-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2005 2:07 AM
To: Jakarta Commons Developers List
Subject: Re: [lang] new method on ClassUtils
Can we not leave this until af
Personally, I've always liked the following numbering scheme:
Major.Minor.Maintenance.
Gary
-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Monday, February 07, 2005 2:08 PM
To: Jakarta Commons Developers List
Subject: Re: [lang] release strategy
Personally
Also, providing a unit test patch with a test is, IMHO, essential. I
like to apply the unit test patch, watch the test fail, apply the patch,
watch the test pass.
Cheers,
Gary
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 15, 2005 5:26 AM
To: Ja
at org.apache.tools.ant.Main.startAnt(Main.java:188)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
but runs fine on Java 1.4.2_07.
Any ideas?
Gary Gregory
Senior Software Engineer
Seagull So
Hello [lang]:
For the software I work on, Java 1.4.2 is the base requirement, so
talking about 1.5 is not an option (yet). We revisit the issue from time
to time, but the bottom line is that our customers have not moved to
Java 1.5, so we cannot.
We could do this in a first stage and say that [la
Hello: Steinar:
The current DoubleMetaphone implementation (released and SVN) allows for
Spanish and Germanic characters, so adding support for other languages
in the same class seems to be in the spirit of the current
implementation.
I would also say that having language-specific implementation
In my mind, name vs. name2 makes sense seems for a next generation based
on new code rather than a next version.
Thank you,
Gary
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sandy
> McArthur
> Sent: Monday, October 30, 2006 9:41 AM
> To: Jakarta C
> -Original Message-
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: Saturday, November 04, 2006 3:01 AM
> To: Jakarta Commons Developers List
> Subject: [collections-generics] [PROPOSAL] Remove all author and since
version
> tags
>
> As this is a 'new' project, I propose that
Hello All:
The [lang] file default.properties points to Junit 3.8.1.
Is there any reason we should not use the current 3.8.2 version?
Also, the file reads:
junit.jar = ${junit.home}/junit-3.8.1.jar
I would expect it to read:
junit.jar = ${junit.home}/junit.jar
The the jar file Junit deliver
Hi All:
Interesting and I do see your POV. IMO, it also depends on what tools
you use do to your work. I use the Eclipse Javadoc view which presents
the Javadoc comment in a formatted HTML view. I never bother to use the
source of Javadocs to understand what the comments "say" as there
usually is
Hi All:
The release notes state that [lang-69] is fixed, it is not.
I do have a fix in progress but we should probably push this one back to
3.0 unless we want to delay 2.3. If we really want this one fix, I can
take some time to complete this within a week or so.
Thank you,
Gary
> -Origin
Hi:
The release notes should state that [LANG-102] has been fixed.
Thank you,
Gary
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 02, 2007 5:37 PM
> To: Jakarta Commons Developers List
> Subject: [ang] pre 2.3 build
>
> Using:
>
> "jvm 1.3
: [ang] pre 2.3 build
>
> You resolved that one as fixed saying:
>
> "Fix already in CVS. Please see
> HashCodeBuilderTest#testReflectionObjectCycle(). "
>
> Sounds like it needs to be reopened?
>
> Hen
>
> On 1/2/07, Gary Gregory <[EMAIL PROTEC
Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 02, 2007 9:16 PM
> To: Jakarta Commons Developers List
> Subject: Re: [ang] pre 2.3 build
>
> Check LANG-69's Change History:
>
> Change by Gary Gregory [29/Sep/06 12:5
Good idea, +1 here.
Gary
> Dennis Lundberg wrote on Thursday, January 04, 2007 10:34 PM:
>
> > Hi
> >
> > Before I dive head-first into this I thought I'd ask first.
> > I'd like to
> > unify the M2 generated sites for all sandbox components, by
> > making use
> > of commons-skin. This would mea
+1.
Builds and tests successful on Windows XP Pro SP2 + current patches
with:
-Sun Java 1.4.2_13, Ant 1.6.5, Maven 1.0.2
-Sun Java 1.4.2_13, Ant 1.7.0, Maven 1.0.2
-Sun Java 1.5.0_10, Ant 1.6.5, Maven 1.0.2
-Sun Java 1.5.0_10, Ant 1.7.0, Maven 1.0.2
I used:
ant clean dist test testjar
and:
ma
Hello Xinzi:
I've created this JIRA ticket to track your issue:
[IO-112] NPE in FileUtils.openOutputStream(File) when file has no parent in
path.
http://issues.apache.org/jira/browse/IO-112
I've also committed a fix in SVN. You can rebuild from the SVN sources yourself
or wait for the next nig
+1
Tested with:
- Windows XP Pro SP2 + current patches
- Sun Java 1.4.2_13
- Ant 1.6.5
- Maven 1.0.2
Gary
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 09, 2007 5:44 PM
> To: Jakarta Commons Developers List
> Subject: [VOTE] IO 1.3.1 (RC3)
The following worked for me:
- Windows XP Pro SP2 + current patches
- Sun Java 1.6.0, 1.5.0_10 and 1.4.2_13
- Ant 1.6.5
- Maven 1.0.2
- ant clean dist test
- maven clean site:generate
Gary
> -Original Message-
> From: Oliver Heger [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 10,
+1.
Tested with:
- Windows XP SP2 + current patches
- Ant 1.6.5: ant clean dist test
- Maven 1.0.2: maven clean site:generate
- Sun Java 1.3.1_15 :ant ok
- Sun Java 1.4.2_13: ant & maven
- Sun Java 1.5.0_10: ant & maven
- Sun Java 1.5.0_11: ant & maven
- Sun Java 1.6.0: ant ok
Maven failures:
-
Hi All:
Any guesses on the release schedule?
Thank you.
Gary Gregory
Senior Software Engineer
Seagull Software
[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
www.seagullsoftware.com<http://www.seagullsoftware.com>
+1 here
(Selfish POV: The product I work on now requires Java 1.4 already)
Thank you,
Gary
> -Original Message-
> From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 15, 2007 8:05 PM
> To: Jakarta Commons Developers List
> Subject: [IO] Move to a minimum of JDK 1.4?
>
> T
+1 to your +1; Release early, release often!
Thank you,
Gary
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 15, 2007 12:43 PM
> To: Jakarta Commons Developers List
> Subject: Re: RfC: Release commons-io-1.3.2
>
> +1 to the idea. Release early, rel
It seems like a nice coincidence that IO 1.3 is based on JRE 1.3, and we could
have IO 1.4 based on JRE 1.4, IO 1.5 on JRE 1.5 ;)
Thank you,
Gary
> -Original Message-
> From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 18, 2007 1:10 PM
> To: Jakarta Commons Developers Lis
s prohibited. If you are not the intended recipient,
please contact the sender and destroy all copies of the original
message.
Gary Gregory (JIRA) wrote:
[
https://issues.apache.org/jira/browse/LANG-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1249753
Hello Torsten:
Where is the site that matches this build?
Thank you,
Gary
> -Original Message-
> From: Torsten Curdt [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 24, 2007 4:22 PM
> To: Jakarta Commons Developers List
> Subject: [jci] RC2 available
>
> On every release you (try to) do
I'm all for it.
Gary
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 04, 2007 9:50 PM
> To: Jakarta Commons Developers List
> Subject: [cli] Minimum JDK version for 1.1?
>
> I'd like to move the minimum JDK version for CLI up to 1.4 for the CLI
> 1
Are we sure we do not want to call this 1.4 since the only change is a _new_
class as opposed to maintenance updates?
Thank you,
Gary
> -Original Message-
> From: Jochen Wiedmann [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 12, 2007 12:27 PM
> To: Jakarta Commons Developers List
> Sub
Hello [io]:
+1
I tested the source distribution with Ant 1.7.0 using: "ant clean dist test
testjar" and got "BUILD SUCCESSFUL"s using the following Java Dev Kits:
java version "1.4.2_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_14-b05)
Java HotSpot(TM) Client VM (build 1.4.
> 1) Why not deprecate the public fields in HelpFormatter rather than
> making them private?
Or calling the release 2.0 with the understanding that a breaking compatibility
is under the charter of major release.
Thank you,
Gary
> -Original Message-
> From: Niall Pemberton [mailto:[EMAIL
+1, I would also like to see commons project releases say with each release if
they adhere to this charter (as an extra checks and balances thing)
Thank you,
Gary
> -Original Message-
> From: Phil Steitz [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 12, 2007 11:19 PM
> To: Jakarta Comm
Right +1 from me as noted in [1].
Indeed I did comment about maintenance releases needing to be binary compatible
without new features as Apache guidelines note. In this case, I am happy to let
the release manager make the call. I am also happy with the XP "release early,
release often." I thin
It seems odd that the site (http://jakarta.apache.org/commons/io/) is live but
not [announce]'d and the links point to 1.3.1 downloads but are labeled 1.3.2.
Thank you,
Gary
> -Original Message-
> From: Jochen Wiedmann [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 02, 2007 12:14 PM
> T
Hello:
I agree with Steven on naming. One kind of usage, logging, should not be
reflected in the API name.
Gary
> -Original Message-
> From: Steven Caswell [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 13, 2005 4:57 AM
> To: Jakarta Commons Developers List
> Subject: Re: [lang] Exce
Hello:
I am wondering if a "toXXX" name is not more appropriate since you are
converting rather than getting:
ExceptionUtils.toMessageNoStackTrace(ex)
Or simply:
ExceptionUtils.toMessage(ex)
Also, I wonder if 'Short' is really useful, if I give it 1000 lines,
it's not short. I think you just o
ject: Re: [lang] ExceptionUtils methods
>
> I like these suggestions for method naming.
>
> On 11/13/05, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > Hello:
> >
> > I am wondering if a "toXXX" name is not more appropriate since you
are
> > converting r
I am against it. That's what JSR-166 is for, which is built-in to Java 5
and available as add-ons for Java 1.3.1 and and 1.4.
>From the spec author, this version, runs on both Java 1.3.1 and 1.4.2:
http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/int
ro.html
The backport-util
ff. I just needed these two specific methods.
>
> -Original Message-
> From: Gary Gregory [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 17, 2005 1:17 PM
> To: Jakarta Commons Developers List
> Subject: RE: [lang] Concurrency Classes...
>
> I am against it. That
I agree; this is a case where we need to eat our own dog food.
I can imagine that some people might cry foul in terms of performance
but I am still in favor of re-use.
Gary
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 17, 2005 1:07 PM
>
Hi Glauber:
Feel free to propose an implementation. You can create a bugzilla ticket
and attach a patch for the code and unit tests.
Cheers,
Gary
> -Original Message-
> From: Glauber Pires [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 30, 2005 10:36 AM
> To: commons-dev@jakarta.apac
Hello Andrea:
I have your patch installed on my machine but I want to make sure I
understand the intent. In your example:
public class MyException extends Exception {
public MyException(String msg) {
super(msg);
}
public MyException(String msg, Throwable cause) {
super(msg);
not
including
> commons-lang in the other commons-* components and leverage the power
of
> lang.builder.*, lang.enums.*, lang.exception.* packages and so on?
> IMHO in most cases the commons-lang code is more reliable than the
> equivalent ad-doc imported or written code in the other
Stephen:
I am still on Maven 1.0.2. Which version do you use?
If 2.0 is now needed, will it fix this?:
BUILD FAILED
File.. C:\Documents and
Settings\ggregory.SSSI\.maven\cache\maven-xdoc-plugin-1.8\plugin.jelly
Element... attainGoal
Line.. 687
Column 48
No goal [maven-cobertura-plug
Sounds good Tim.
What about the Zip file?
Gary
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tim O'Brien
> Sent: Saturday, January 07, 2006 12:18 PM
> To: commons-dev@jakarta.apache.org
> Subject: [codec] invalid source tarball on www.apache.org/dist
>
> This
xt
> >
> >
> > maven plugin:download
> > -DgroupId=maven-plugins
> > -DartifactId=maven-cobertura-plugin
> > -Dversion=1.1.1
> >
> > Stephen
> >
> >
> >
> > Gary Gregory wrote:
> >> Stephen:
> > > I am sti
> What JDK version are you using?
>
> -
> [ ] JDK 1.2
> [ ] JDK 1.3
> [X] JDK 1.4
> [ ] JDK 1.5 (or JDK 5)
> -
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Hello Chris:
Welcome to Codec development.
One obvious thing: Make sure you start with latest from SVN:
https://svn.apache.org/repos/asf/jakarta/commons/proper/codec/trunk
(as opposed to the 1.3 sources)
You mention unit test failures? When I run:
ant clean jar test
All unit tests pass.
I
Hello:
Where in SVN (or still in CVS) do we keep our clover.license file?
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ant clean jar test
>
> Gives me a failure on SoundexTest. I am junning Sun Java 1.4.2_08_b03.
>
> I am curious as to why it would fail for me but not you, only
> differences are java version and perhaps junit version (I am using
> v3.8.1).
>
> Best,
> Chris
>
> Gary Gre
Hello:
I am currently using Maven 1.0.2.
Has anyone been using Maven 2.to build Codec or Lang?
Thanks,
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
elopers List
> Subject: Re: [all] clover.license file?
>
> svn:committers/donated-licences/clover/
>
> On 2/15/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > Hello:
> >
> > Where in
To: Jakarta Commons Developers List
> Subject: Re: [all] clover.license file?
>
> On 2/16/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > Hello:
> >
> > (It is not in https://svn.apache.org/repos/asf, right?)
> >
> > Would that be in the repos-private di
; From: Rahul Akolkar [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 16, 2006 2:16 PM
> To: Jakarta Commons Developers List
> Subject: Re: [all] clover.license file?
>
> On 2/16/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > Hello Rahul:
> >
> > I am ope
Seems like a good idea. Since PADDING is private, the change will not
create an incompatibility.
Gary
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 05, 2006 11:34 PM
> To: Jakarta Commons Developers List
> Subject: [lang] lazy load of PADDING i
Hello:
Can we take care of this PADDING issue and think of a release? It's been
too long IMO. Are there any roadblocks?
Gary
> -Original Message-
> From: Henri Yandell [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 05, 2006 11:34 PM
> To: Jakarta Commons Developers List
> Subject: [lang
ably on the
formatter.
>
> Stephen
>
>
> Gary Gregory wrote:
> > Hello:
> >
> > Can we take care of this PADDING issue and think of a release? It's
been
> > too long IMO. Are there any roadblocks?
> >
> > Gary
> >
> >
> >>-
As a reference, here is a thread about this class:
http://marc.theaimsgroup.com/?t=11230087692&r=1&w=2
Gary
> -Original Message-
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 07, 2006 3:04 PM
> To: Jakarta Commons Developers List
> Subject: [lang] Variab
Hello:
Personally, I like the VariableFormatter class and plan on using it in
production. For me, this class is what is motivating me to push for a
2.2 release (3.0 seems like release inflation ;)
I agree that VariableFormatter appears complex, but that is OK to me
given the flexibility it provid
Hello:
This could be a religious issue... look out!
In our product code bases, we use the "this.foo()" convention. The
argument being, that in object oriented programming, a message is sent
to an object, always.
How does the list feel about cleaning up foo()'s to this.foo()'s?
I am willing to d
ge()" syntax.
Gary
> -Original Message-
> From: James Ring [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 07, 2006 3:46 PM
> To: Jakarta Commons Developers List
> Subject: Re: [lang] this.foo() vs. foo()
>
> Hi Gary,
>
> On Wednesday 08 March 2006 10:35, Gar
> hate it :)
Joke and emotion aside, I am interested in what makes programmers take
an opinion on topics like this.
Could you describe what you like about the one syntax?
Could you categorize your POV, perhaps one of:
- I do like change
- I like foo() because:
- I like this.foo() because:
-
CTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sandy
> McArthur
> Sent: Tuesday, March 07, 2006 4:03 PM
> To: Jakarta Commons Developers List
> Subject: Re: [lang] this.foo() vs. foo()
>
> On 3/7/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > In our product code bases, we use t
> Subject: Re: [lang] this.foo() vs. foo()
>
> On 3/7/06, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > On 3/7/06, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > > On 3/7/06, Sandy McArthur <[EMAIL PROTECTED]> wrote:
> > > > On 3/7/06, Gary Gregory <[
Hello:
IMO, WONTFIX them all.
- http://issues.apache.org/bugzilla/show_bug.cgi?id=27643
I am happy to drop this and revisit in the future a method by method
evaluation of newInstance methods (for example: newInstanceOrNull-type
of methods)
- http://issues.apache.org/bugzilla/show_bug.cgi?id=338
I am a fan of eliminating redundancies. I would be +1 with deprecating
[lang]'s Fraction class and point to [math]. This would have to benefit
of keeping [lang] focused.
Gary
> -Original Message-
> From: Phil Steitz [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 09, 2006 10:10 AM
> To:
Hello:
> [X] -1 I do not support this release because...
The Maven build will fail [1] if you do not have commons-build
installed.
The documentation makes no note of this dependency (or I could not find
it.) IMO, this needs to be mentioned in the following places:
http://people.apache.org/~sco
ment this yourself. Please lets not add to the
barriers/bureaucracy
> of
> > releasing unless we absolutely have to.
>
> +1 - and this is documented in
> http://jakarta.apache.org/commons/building.html, which is linked from
> the [io] pages.
>
> Phil
>
> >
> &
TECTED]
> Sent: Saturday, March 11, 2006 5:18 AM
> To: Jakarta Commons Developers List
> Subject: RE: [VOTE] Release IO 1.2
>
> On Fri, 2006-03-10 at 22:50 -0500, Gary Gregory wrote:
> > Hello:
>
> hi gary
>
> > > [X] -1 I do not support this release because...
Ant 1.6.5 and Maven 1.0.2 builds work for me on Window XP SP2 on Sun
Java 1.4.2_10.
On Sun Java 1.3.1_15, I get:
internal-test:
[mkdir] Created dir:
C:\temp\commons-io-1.2-RC3-src\build\test-reports
[junit] Running org.apache.commons.io.CopyUtilsTest
[junit] java.lang.NoClassDefFoundE
FWIW. The current version of JUnit 3 is 3.8.2.
Gary
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 12, 2006 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: svn commit: r385299 -
> /jakarta/commons/proper/io/trunk/project.xml
>
> Author: scolebou
Based on RC4:
I can do a Maven build with Sun Java 1.4.2_10 on Windows XP SP2.
I get a Maven build failure using Java 1.3.1_15 (See below).
It tuens out that Cobertura requires Java 1.4:
"Also, Cobertura 1.2 (and 1.1, and maybe 1.0) requires a 1.4 or newer
JVM."
The above is from the 16 March
+1
Tested building with Ant 1.6.5 and Maven 1.0.2 on Sun Java 1.4.2_11 on
Windows XP SP2.
Gary
PS:
Checkstyle nits:
Error Line
Error Unused import - java.io.UnsupportedEncodingException. 26
Error Unused @throws tag for 'UnsupportedEncodingException'. 868
Error Unused @throws tag for
I see that the JDiff report is marked "Between IO_1_1 and CURRENT". I
imagine that the Maven build will be re-run after a IO_1_2 is created?
Just checking... ;)
Gary
> -Original Message-
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 14, 2006 4:16 PM
> To: Jak
This is not so great: 0% unit test coverage on:
http://people.apache.org/~scolebourne/commons-io/site/cobertura/org.apac
he.commons.io.input.ProxyReader.html
and
http://people.apache.org/~scolebourne/commons-io/site/cobertura/org.apac
he.commons.io.output.ProxyWriter.html
Gary
> -Original
> On Thu, 2006-03-16 at 10:02 -0500, Rahul Akolkar wrote:
> > Suggestions:
> >
> > a) Lets indicate the closure on voting threads (helps those who
cannot
> > watch a particular vote constantly, and also helps the archives).
> > Accordingly, I have posted to the older IO 1.2 vote threads.
+1
> > b
Hello:
This seems reasonable but I wonder if it wouldn't be nice to have API
names that are similar to BigInteger (and AtomicInteger.) For example,
we could have "add" and "substract", instead of "addValue" and
"substactValue".
Gary
> -Original Message-
> From: Stephen Colebourne [mailto
> -Original Message-
> From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 21, 2006 11:26 AM
> To: Jakarta Commons Developers List
> Subject: Re: [pool] Announcing Release Candidate 1 for Pool 1.3
>
> I have a few comments on RC1
>
> 1) Its not obvious how to find the
Hi there:
When I build from the latest from SVN with Maven I get the error:
jdiff:
[mkdir] Created dir: C:\svn-store\jakarta\commons\pool\target\jdiff
[mkdir] Created dir:
C:\svn-store\jakarta\commons\pool\target\docs\jdiff
[mkdir] Created dir:
C:\svn-store\jakarta\commons\pool\target
Hi:
It looks like some of this code depends on Java 1.4. Code like:
assert Thread.holdsLock(pool);
Java 1.4 as a dependency is fine with me but is that really what [pool]
should depend on?
Thanks,
Gary
> -Original Message-
> From: robert burrell donkin
[mailto:[EMAIL PROTECTED]
> S
gned off
>
> On 3/22/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > It looks like some of this code depends on Java 1.4. Code like:
> >
> >assert Thread.holdsLock(pool);
> >
> > Java 1.4 as a dependency is fine with me but is that really what
[pool]
>
Hello:
I've done some [codec] work over the years and there are probably enough
little fixes for a minor release but I've not seen anything to motivate
me for a major release.
Frankly, copying code from one project to another is not a motivation
for me and actually it is not something I want to
-
> From: Chris Black [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 22, 2006 10:07 PM
> To: Jakarta Commons Developers List
> Subject: Re: [codec] crypto-compat BigInt patch, no feedback for one
month
>
> Gary Gregory wrote:
>
> >Hello:
> >
> >I've
This build works fine with our application.
My only wish would be to make BaseObjectPool.isClosed() public.
Gary
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sandy
> McArthur
> Sent: Wednesday, March 22, 2006 5:03 PM
> To: Jakarta Commons Develope
+1
Build ok with:
- Ant 1.6.5
- Maven 1.0.2
- Sun Java 1.4.2_11
- Windows XP SP2
Gary
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sandy
> McArthur
> Sent: Wednesday, March 22, 2006 5:03 PM
> To: Jakarta Commons Developers List; Jakarta Commons Us
10 PM
> To: Jakarta Commons Developers List
> Subject: Re: [pool] BaseObjectPool.isClosed() visibility [was:
Announcing
> Release Candidate 2 for Pool 1.3]
>
> On 3/23/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > This build works fine with our application.
> &g
avior() test (about
> 45% down the file) and let me know if a pool that passes that test
> meets your needs. Here's a link to the trunk version of that file:
>
http://svn.apache.org/viewcvs.cgi/jakarta/commons/proper/pool/trunk/src/
te
> st/org/apache/commons/pool/TestObjectPool.jav
t
> Subject: Re: [pool] BaseObjectPool.isClosed() visibility [was:
Announcing
> Release Candidate 2 for Pool 1.3]
>
> On 3/24/06, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > Sandy:
> >
> > I see this comment in the unit test:
> >
> > // The following
Hello:
FWIW, we use "Enum" as a postfix, for example JmsPropertyEnum. To me, a
type, is an interface or a class, or a data-type. "Type" does not convey
to me the idea that the object has a limited pre-defined set of values.
Gary
> -Original Message-
> From: Stephen Colebourne [mailto:[EM
1 - 100 of 863 matches
Mail list logo
