On 7/24/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
On 7/24/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> Thanks Phil :)
>
NP. Impressive response time by Brett. Almost as impressive as the
spammers. Now if I can just determine which commons component will
help this poor
[
https://issues.apache.org/jira/browse/FILEUPLOAD-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell reopened FILEUPLOAD-140:
--
Reopening as there's a post-close comment on there.
> Means to prese
Thanks Phil :)
On 7/23/07, Brett Porter <[EMAIL PROTECTED]> wrote:
swapped :)
On 24/07/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
> I will do this.
>
> Phil
>
> On 7/23/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > Is there anyone who could volu
Yeah, our work CI also found it. Linux box.
On 7/24/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
On 7/24/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> Can anyone else reproduce this failure?
>
Yes (XP, Tiger, m102).
-Rahul
> -dain
>
> On Jul 24, 2007, at 3:03 AM, Phil Steitz wrote:
>
> >
[
https://issues.apache.org/jira/browse/FILEUPLOAD-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell reopened FILEUPLOAD-141:
--
(Reopening as closed issues with ongoing conversations are too easy to lose
track of
Is there anyone who could volunteer to moderate the list?
I'm looking to share the load and get off of commons-dev moderating :)
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 7/23/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
When issues are complete, do you close or resolve them? I have been
closing them, but just noticed that may are resolved.
I close em.
Also, should I create a DBCP 1.4 and move the issues (like max time
limit for pooled objects) we aren't
SVN and JIRA karma granted.
On 7/20/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
Please join us in welcoming Dain Sundstrom as a new Commons committer.
Dain is an apache committer active on multiple ASF projects who has
been contributing patches to [dbcp] faster than we can commit them :)
We are
Jump right in. :)
I've an urge for such a thing to exist here, but after changing jobs a
while back my itch went away.
On 7/19/07, Matt Benson <[EMAIL PROTECTED]> wrote:
Announcing my intent to commit in [csv]. I'll be
starting small...
---
I've moved this issue over to the Torque JIRA project, rather than
closing and asking the user to open one there.
Hen
On 7/20/07, Henri Yandell (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/DBCP-53?page=com.atlassian.jira.plugin.system.issueta
[
https://issues.apache.org/jira/browse/DBCP-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated DBCP-53:
--
Summary: 'not supported' error given against Firebird DB (was: [dbcp]
commons dbcp does no
So sounds like we need an older version of Ant.
Do the Security errors happen on more modern JVMs? Are they new tests?
On 7/19/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Anyone?
Dennis Lundberg wrote:
> Hi
>
> I'm trying to put together an an script that will do nothing more than
> run the
On 7/19/07, Sullivan, Sean <[EMAIL PROTECTED]> wrote:
Are there plans to release Commons Logging 1.1.1?
I am eager to see Commons Logging 1.1.1 because JCL 1.1 throws
exceptions when running in a Java applet sandbox. (This bug is already
fixed: https://issues.apache.org/jira/browse/LOGGING-10
[
https://issues.apache.org/jira/browse/DAEMON-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed DAEMON-101.
Resolution: Fixed
Thanks Tim, both have been fixed in SVN.
> Javadoc typo, says "avfter
[
https://issues.apache.org/jira/browse/LANG-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-349:
---
Fix Version/s: 2.3.1
First step - attempt a reproduction. If that fails, then dig into the code and
[
https://issues.apache.org/jira/browse/DIGESTER-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated DIGESTER-111:
---
Fix Version/s: 1.8.1
> Null InputStream leads to MalformedURLExceptions under JDK
[
https://issues.apache.org/jira/browse/DIGESTER-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed DIGESTER-117.
--
Resolution: Fixed
Fix Version/s: 1.8.1
Emulating the changes in DBCP/Beanutils (I
[
https://issues.apache.org/jira/browse/DIGESTER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed DIGESTER-89.
-
Resolution: Fixed
Fix Version/s: 1.8.1
svn ci -m "Applying Petteri Räty's
[
https://issues.apache.org/jira/browse/DIGESTER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed DIGESTER-109.
--
Resolution: Won't Fix
Closing as WONTFIX, as with the validator issue this links to.
[
https://issues.apache.org/jira/browse/DIGESTER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated DIGESTER-114:
---
Fix Version/s: 1.8.1
> SetPropertyRule throws /java.lang.IllegalArgumentException: No n
[
https://issues.apache.org/jira/browse/DIGESTER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated DIGESTER-115:
---
Fix Version/s: 1.8.1
> Digester depends on BeanUtils copies of Collections clas
[
https://issues.apache.org/jira/browse/DIGESTER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513723
]
Henri Yandell commented on DIGESTER-115:
Note, it only directly depends on ArrayStack. Buffer and
So, with a mind to getting a beta out pretty soon, here's what it
looks like to me:
1] Close BEANUTILS-91
2] Fold the separate optional source back into the main codeline.
3] Check binary compatibility, close BEANUTILS-280
4] Tag as 1.8.0-beta1
5] Create a distribution from the tag using Maven2.
On 7/17/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 7/17/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On 7/17/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > My view is that we have the following options:
> >
> > 1) Merge em back in and just r
On 7/11/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
One thought I had was to do a 1.8.0 Beta release first to (hopefully)
get wider te
[
https://issues.apache.org/jira/browse/BEANUTILS-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513318
]
Henri Yandell commented on BEANUTILS-35:
You mentioned pushing this one out to 1.8.x on IM - I'm in f
[
https://issues.apache.org/jira/browse/BEANUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513317
]
Henri Yandell commented on BEANUTILS-92:
I've committed a modified version of your patches as r55700
On 7/14/07, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
> One area for discussion is the split between the optional Collections
> component and the 'Core' beanutils. Do we maintain that, or should we
> just fold the code back together?
>
&g
[
https://issues.apache.org/jira/browse/BEANUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513305
]
Henri Yandell commented on BEANUTILS-92:
Unit test comments:
* You don't need to catch the Thro
On 7/15/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
I have cleaned up some of my performance / load test code for [dbcp]
and [pool] and would like to commit it somewhere so others can use and
improve it. There is some common load generation code that should be
factored out and I don't want to clu
[
https://issues.apache.org/jira/browse/LANG-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-52:
--
Fix Version/s: 3.0
> [lang] Validate.notNull should throw NullArgumentExcept
[
https://issues.apache.org/jira/browse/LANG-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell reopened LANG-52:
---
Reopening this issue for 3.0 - backwards compatible changes might be acceptable
then.
> [l
[
https://issues.apache.org/jira/browse/LANG-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed LANG-343.
--
Resolution: Won't Fix
Fix Version/s: (was: 2.3.1)
> Validate: Throw NullArgumentE
[
https://issues.apache.org/jira/browse/LANG-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-347:
---
Fix Version/s: (was: 2.3.1)
> DateUtils' new addWeekdays
[
https://issues.apache.org/jira/browse/LANG-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512691
]
Henri Yandell commented on LANG-346:
Digging into this - I can definitely reproduce the error with the test case
On 7/13/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Dain Sundstrom wrote:
> Are snapshot jars for commons (specifically commons-dbcp) published
> anywhere? I expected to see them here
> http://people.apache.org/repo/m2-snapshot-repository/
Almost none of the commons components use Maven 2 to
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code back together?
1.7.0 shipped three versions:
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.7.0.jar
commons-beanutils-collections-1
[
https://issues.apache.org/jira/browse/BEANUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512669
]
Henri Yandell commented on BEANUTILS-142:
-
As we dig into it at the same time :)
So...
3) Use Niall&#
[
https://issues.apache.org/jira/browse/BEANUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512666
]
Henri Yandell commented on BEANUTILS-142:
-
Definitely two issues.
On your fix; it turns out that I was
[
https://issues.apache.org/jira/browse/LANG-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512515
]
Henri Yandell commented on LANG-348:
Logically it would be:
public static String repeat(String str, char
[
https://issues.apache.org/jira/browse/BEANUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated BEANUTILS-142:
Attachment: Play.java
Test case for this bug. It shows that there is a problem with
[
https://issues.apache.org/jira/browse/BEANUTILS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed BEANUTILS-281.
---
Resolution: Won't Fix
Marking as WONTFIX for the reasons above - please feel fr
[
https://issues.apache.org/jira/browse/BEANUTILS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512281
]
Henri Yandell commented on BEANUTILS-281:
-
Interestingly, the Harmony version of Introspector/BeanInfo
[
https://issues.apache.org/jira/browse/BEANUTILS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512268
]
Henri Yandell commented on BEANUTILS-281:
-
Just to follow up more on this issue, the type of which I&#x
[
https://issues.apache.org/jira/browse/DBCP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed DBCP-227.
--
Resolution: Fixed
Fix Version/s: 1.3
svn ci -m "Applying my patch from DBCP-227 - it&#
[
https://issues.apache.org/jira/browse/BEANUTILS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511973
]
Henri Yandell commented on BEANUTILS-18:
I'm +1 to the view that this is a bug and not a back
e Maven 1 conventions and released new versions under the
naming conventions for Maven 2. Because developers must modify their POM
to update the version number anyway, editing the groupId is a trivial
additive.
Paul
Henri Yandell wrote:
> On 7/9/07, Wendy Smoak <[EMAIL PROTECTED]> wrot
On 7/9/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 7/9/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> For development of new releases, should the commons-* folders be forgone
> and use org.apache.commons now?
Check the list archives for some past discussion... it has to be
handled carefully w
[
https://issues.apache.org/jira/browse/DBCP-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511461
]
Henri Yandell commented on DBCP-229:
This would be a cool debug mode to have, though I wonder if it would get used
[
https://issues.apache.org/jira/browse/CLI-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed CLI-136.
-
Resolution: Won't Fix
The (about to be released) 1.1 project.xml has a test set.
Both the project.xm
Binding +1s from:
Henri Yandell
Dion Gillard
Jörg Schaible
Phil Steitz
Rahul Alkolkar
and +1s from the barely different RC2:
Torsten Curdt
Oliver Heger
I'll go ahead and make the release, thanks for all the feedback and help.
Hen
On 7/4/07, Henri Yandell <[EMAIL PROTECTED]> w
On 7/6/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
So my proposal is that any ASF committer who wishes to become a
commons committer just needs to make that request here on the
commons-dev mailing list and they will granted karma for both commons
proper and commons sandbox. Expectation is of cou
[
https://issues.apache.org/jira/browse/LANG-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-344:
---
Fix Version/s: 3.0
Setting for 3.0 consideration.
> CollatorUtils - equivalent of StringUtils,
[
https://issues.apache.org/jira/browse/LANG-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-340:
---
Fix Version/s: 3.0
Setting for investigation in 3.0 (though if anyone wants to dig into it, please
[
https://issues.apache.org/jira/browse/LANG-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-342:
---
Fix Version/s: 2.3.1
Setting fix version to 2.3.1 so the javadoc can be added. Then it should be
[
https://issues.apache.org/jira/browse/LANG-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-346:
---
Fix Version/s: 2.3.1
> Dates.round() behaves incorrectly for minutes and seco
[
https://issues.apache.org/jira/browse/LANG-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated LANG-341:
---
Fix Version/s: 3.0
Setting fix version to 3.0 for consideration there.
A unit test would be much
On 7/6/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 7/6/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I would like to commit to commons validator and commons i18n to enhance
> them for Struts. For validator, I want to add and finish some issues in
> the current snapshot, and, respectively,
I'm +1 btw :)
Hen
On 7/4/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
I've updated the release notes to match the website page:
http://people.apache.org/~bayard/commons-cli/1.0-rc3/
with the site in:
http://people.apache.org/~bayard/commons-cli/1.0-rc3/site/
One quirk to n
Done.
On 7/6/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
Can someone with karma karma pls set Paul up?
It would be great to get i18n promoted to proper and released. Any
other volunteers to help with this?
Phil
On 7/5/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I would like to commit to co
[
https://issues.apache.org/jira/browse/BEANUTILS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed BEANUTILS-287.
---
Resolution: Fixed
Fix Version/s: 1.8.0
New "test" target added; ie) I
I've updated the release notes to match the website page:
http://people.apache.org/~bayard/commons-cli/1.0-rc3/
with the site in:
http://people.apache.org/~bayard/commons-cli/1.0-rc3/site/
One quirk to note. The site is from trunk while the release is from
the 1.0.x branch.
[ ] +1, before 6 y
[
https://issues.apache.org/jira/browse/DIGESTER-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510005
]
Henri Yandell commented on DIGESTER-117:
Either run 'maven ant', or replace the existing test
[
https://issues.apache.org/jira/browse/BEANUTILS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509962
]
Henri Yandell commented on BEANUTILS-287:
-
Either we should 'maven ant' it, or replace all the
[
https://issues.apache.org/jira/browse/DBCP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated DBCP-227:
---
Attachment: DBCP-227.patch
Attachment: Tests added in, uses junit, fixes commons logging property
On 7/1/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
+1 from me
Would be nice to have more keys in the KEYS file though.
Thinking about it - don't even need the KEYS file anymore. We merged
all the Commons ones together. So now testing should involve getting
the central KEYS file and making sur
On 7/1/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
+1 from me.
Some minor remarks:
- When building with maven, in the manifest of the resulting jar some
entries are duplicated with different values.
I get:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: Apache Maven
Built-By:
[
https://issues.apache.org/jira/browse/COLLECTIONS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509351
]
Henri Yandell commented on COLLECTIONS-3:
-
That should be:
synchronized(map) {
Playing with SoakLRUMap
I believe the RC1 issues have been taken care of, so here goes with a
second try:
http://people.apache.org/~bayard/commons-cli/1.0-rc2/
with the site in:
http://people.apache.org/~bayard/commons-cli/1.0-rc2/site/
One quirk to note. The site is from trunk while the release is from
the 1.0.x bra
[
https://issues.apache.org/jira/browse/CLI-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed CLI-21.
Resolution: Fixed
> [cli] clone method in Option should use super.cl
[
https://issues.apache.org/jira/browse/CLI-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed CLI-134.
-
Resolution: Fixed
Second patch solves it.
> 1.1 is not backwards compatible because it adds methods to
[
https://issues.apache.org/jira/browse/CLI-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated CLI-134:
--
Attachment: CLI-134-2nd.patch
Last patch commented out the wrong method. This patch fixes that and fixes
[
https://issues.apache.org/jira/browse/CLI-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed CLI-135.
-
Resolution: Fixed
Patches applied. Clirr no longer errors.
> Backwards compatibility between 1.1 and
[
https://issues.apache.org/jira/browse/CLI-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated CLI-135:
--
Attachment: CLI-135-2nd.patch
Got the parameter wrong on the new/old addValue. I did Object, should have
[
https://issues.apache.org/jira/browse/CLI-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated CLI-135:
--
Attachment: CLI-135.patch
Attaching a patch to do both of these. The new method is addValueForProcessing
On 6/13/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
4 items to fix:
1) Make the fields in HelpFormatter public. DONE.
2) Make the Option class cloneable again. See:
https://issues.apache.org/jira/browse/CLI-21
Brian had a nice patch adding clone(), but he did it the right way
(pro
[
https://issues.apache.org/jira/browse/CLI-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509029
]
Henri Yandell commented on CLI-135:
---
First step is to change the package private addValue variant so it no longer
Issue Type: Bug
Components: CLI-1.x
Affects Versions: 1.0
Reporter: Henri Yandell
Fix For: 1.1
ERROR: 7006: org.apache.commons.cli.Option: Return type of method 'public
boolean addValue(java.lang.String)' has been changed to void
E
[
https://issues.apache.org/jira/browse/CLI-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509037
]
Henri Yandell commented on CLI-21:
--
Here's the clirr error:
ERROR: 7009: org.apache.commons.cli.Option: Accessib
[
https://issues.apache.org/jira/browse/CLI-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated CLI-21:
-
Attachment: CLI-21.patch
Patch making the clone method public again, and dropping the exception.
> [
[
https://issues.apache.org/jira/browse/CLI-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell reopened CLI-134:
---
Damn. Missed and removed a method I shouldn't have :) Leaving one in that
should have stayed.
>
[
https://issues.apache.org/jira/browse/CLI-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed CLI-134.
-
Resolution: Fixed
Applied to SVN - r551811.
> 1.1 is not backwards compatible because it adds methods
[
https://issues.apache.org/jira/browse/CLI-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell updated CLI-134:
--
Attachment: CLI-134.patch
Patch removing the methods.
> 1.1 is not backwards compatible because it a
Project: Commons CLI
Issue Type: Bug
Components: CLI-1.x
Affects Versions: 1.0
Reporter: Henri Yandell
Fix For: 1.1
Attachments: CLI-134.patch
General problem - the interface adds methods.
Solution - remove the interfaces from the methods and
[
https://issues.apache.org/jira/browse/CLI-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509022
]
Henri Yandell commented on CLI-21:
--
Another thought - as I kick myself to keep momentum on the CLI release. Need to
ACK'd.
On 6/26/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
Please acknowledge
http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/
200706.mbox/%
[EMAIL PROTECTED]
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL
ACK'd.
On 6/26/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
Please acknowledge
http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/
200706.mbox/%
[EMAIL PROTECTED]
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL
+1.
On 6/28/07, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
I also would strongly prefer to use this opportunity to create a commits list
and an issues list.
Commons is big enough to need it, and it would increase the signal to noise on
the main list, especially when searching.
Stephen
-
On 6/27/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 6/28/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 6/27/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > On 6/28/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
> > > On 6/27/0
On 6/27/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 6/28/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
> On 6/27/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > Personally, my vote would be to say:
> >
> > commons=committers
>
> You mean a
> dennisl
> niallp
> mvdb
> ozeigermann
> joehni
> oheger
> mbenson
> martinc
> psteitz
> tcurdt
> dfs
> rwinston
> luc
> pietsch
> dion
> brentworden
> skitching
> rahul
>
> Verify that domain "commons.apache.org" is
[
https://issues.apache.org/jira/browse/FILEUPLOAD-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell reopened FILEUPLOAD-137:
--
Still a problem. According to findbugs, there are still errors:
"Message:
[
https://issues.apache.org/jira/browse/COLLECTIONS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed COLLECTIONS-257.
-
Resolution: Duplicate
Fix Version/s: 3.3
Duplicate of COLLECTIONS-219, which
Don't go the subtask route. Keep it all on the one issue as TLP Admin
and Joe'll take care of things.
Hen
On 6/22/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:
There is a Velocity JIRA Issue with a lot of subtasks that basically has
everything that is needed/can be done for a new TLP. S
On 6/23/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote:
Niall Pemberton wrote:
> On 6/23/07, Martin van den Bemt <[EMAIL PROTECTED]> wrote:
>> Noticed the call of toString() on a String during the huntdown of what
>> in beanutils broke the
>> betwixt tests. (in the TestObjectStringConverters
if they upgrade commons-io from
1.3.1 to 1.3.2.
Henri Yandell wrote:
> Sorry for being slow on this one.
>
> I'm with Jochen and Joerg in not getting why deprecation would
> indicate a minor release and not be allowed in a bugfix release. Sure
> it sucks that a new class is imme
On 6/20/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
Next releases: [dbcp] - 1.3 close as many of the 1.3-marked bugs as
possible without the new pool impl and add instrumentation using JDK
logging, therefore increasing required JDK level to 1.4.
+1. Instrumentation is strongly needed.
Resolu
Sorry for being slow on this one.
I'm with Jochen and Joerg in not getting why deprecation would
indicate a minor release and not be allowed in a bugfix release. Sure
it sucks that a new class is immediately being deprecated, but better
to get such things out there now rather than waiting.
Hen
+1.
I also ran Clirr/Jardiff on the command line. Clirr failed as it
needed the AntTask dependency, but jardiff showed that there are no
differences between the 2.0 and 2.0.1 jars.
Hen
On 6/21/07, Dion Gillard <[EMAIL PROTECTED]> wrote:
+1
On 6/22/07, Niall Pemberton <[EMAIL PROTECTED]> wrote
On 6/21/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 6/22/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
>
> On 21.06.2007, at 00:57, Martin van den Bemt wrote:
>
> > Hi everyone,
> >
> > The new Commons TLP was established today, with Torsten Curdt as
> > Vice President.
>
> ...so where do we
1 - 100 of 3323 matches
Mail list logo
