Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070724/dbcp.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 7/23/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
DBCP-143 talks about problem with propagation of SQLNestedException
to clients and the comment suggests a conversion to normal Java
nested exception when we switch to Java 1.4. Since we made the leap,
I did a bit of refactoring to remove this
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 soul get the money he is owed;-)
Phil
Should be fixed now. The nightlies run the m1 build and that needs
the transitive dependencies to be specified. We could change the
nightly to m2, but I think it is a good idea to keep the m1 build
working for now and the nightly can alter us if we break it.
Phil
On 7/24/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 7/24/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 24, 2007, at 7:56 AM, Phil Steitz wrote:
On 7/23/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
snip/
So, should we drop SQLNestedException?
This is tempting, but it breaks
On 7/23/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 20, 2007, at 5:26 PM, Phil Steitz wrote:
On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote:
On Jul 19, 2007, at 11:19 PM, Phil Steitz wrote:
I would love to have a fix
I will do this.
Phil
On 7/23/07, Henri Yandell [EMAIL PROTECTED] wrote:
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,
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514497
]
Phil Steitz commented on POOL-97:
-
A more conservative solution would be to revert to the pool 1.2 setup where
[
https://issues.apache.org/jira/browse/DBCP-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-11.
-
Resolution: Fixed
Patch applied. Thanks.
[dbcp] stmt.getConnection() != Connection used to create
On 7/19/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 7/19/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
I think passivate() is called automatically when the connection is
put back in the pool (due to the _conn.close() call). I think there
are tests that check that the statements were closed
On 7/21/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 20, 2007, at 10:15 PM, Phil Steitz wrote:
On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote:
I think this will require a patch to pooling (documented in
DBCP-221). What
[
https://issues.apache.org/jira/browse/POOL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved POOL-94.
-
Resolution: Won't Fix
Javadoc has been updated to include a warning.
GenericObjectPool allows checking
[
https://issues.apache.org/jira/browse/DBCP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-232.
--
Resolution: Fixed
Javadoc fix committed in r558394. Thanks for reporting thi
maxWait = 0 waits
[
https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514453
]
Phil Steitz commented on MATH-167:
--
Fixed for nomal distribution in r558450.
Leaving open because we should look
[
https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated MATH-167:
-
Fix Version/s: 1.2
ConvergenceException in normal CDF
On 7/19/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
Are there any DBCP-1.3 release plans? Based on the JIRAs I think we
are close to being ready to release. Are there any items that are
planned but don't have JIRAs?
There are two things that I would like to at least talk about that
relate to
on the second close.
-dain
On Jul 19, 2007, at 10:33 PM, Phil Steitz wrote:
Sorry I missed this in initial review. I am not sure we want to
remove the passivate() below, since that closes statements traced by
this connection. Am I missing something here?
Phil
jakarta/commons/proper/dbcp/trunk/src
On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote:
On Jul 19, 2007, at 11:19 PM, Phil Steitz wrote:
I would love to have a fix for DBCP-44; but that could wait on pool
1.4 if necessary (and Ipersonally see no way to fix it just within
On 7/20/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 20, 2007, at 11:26 AM, Dain Sundstrom wrote:
On Jul 19, 2007, at 11:19 PM, Phil Steitz wrote:
On 7/19/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
Are there any DBCP-1.3 release plans? Based on the JIRAs I think we
are close
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 happy to have him among us as a Commons committer.
Welcome, Dain!
[
https://issues.apache.org/jira/browse/DBCP-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-209.
--
Resolution: Invalid
I agree with Dain. For BasicDataSource, the username and password are pool
Sorry I missed this in initial review. I am not sure we want to
remove the passivate() below, since that closes statements traced by
this connection. Am I missing something here?
Phil
jakarta/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/DelegatingConnection.java
Tue Jul 17
On 7/19/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
The PerUserDataSource and SharedPoolDataSource use primitives for the
read only, transaction isolation and auto commit default values so
there is not way to see if the value was set in the configuration.
This means there is no way to allow the
[
https://issues.apache.org/jira/browse/DBCP-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-233.
--
Resolution: Fixed
Patch applied. Many thanks.
Allow connection, statement, and result set
[
https://issues.apache.org/jira/browse/DBCP-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-134.
--
Resolution: Fixed
Fixed in r 557176.
[dbcp] DelegatingConnection.close() throws exception
[
https://issues.apache.org/jira/browse/DBCP-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-3.
Resolution: Fixed
Fixed in r 557176.
[dbcp] PoolableConnection.close() won't allow multiple close
[
https://issues.apache.org/jira/browse/DBCP-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-5.
Resolution: Fixed
Fixed in r 557176.
[dbcp] PoolGuardConnectionWrapper violates close() contract
[
https://issues.apache.org/jira/browse/DBCP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-23.
-
Resolution: Fixed
Fixed in r 557176.
[dbcp] SQLException When PoolablePreparedStatement Already Closed
On 7/16/07, Henri Yandell [EMAIL PROTECTED] wrote:
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
On 7/17/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
I'm working on a fix for the back pointers bugs DBCP-11 and DBCP-217
where the Statement.getConnection() and ResultSet.getStatement()
return the wrong objects. The fix is pretty simple; we just need to
make sure we wrap Statements and
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 clutter the component codebases, so I
am hesitant to
On 7/13/07, Julien Aymé [EMAIL PROTECTED] wrote:
It seems good; just a little mispelling problem with the protected
method createConectionFactory():
Wouldn't it be better if it were spelled createConnectionFactory() ?
(With 2 n in connection :-)
Good catch. Thanks!
Phil
[
https://issues.apache.org/jira/browse/DBCP-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-230.
--
Resolution: Fixed
Patch applied. Thanks!
[DBCP] BasicManagedDataSource
On 7/12/07, Brett Porter [EMAIL PROTECTED] wrote:
On 13/07/07, Phil Steitz [EMAIL PROTECTED] wrote:
Where are we now in terms of capabilities for Continuum builds? In
particular, is it possible to a) deploy the tarballs to
people.apache.org and b) deploy the snapshot jars produced
On 7/11/07, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
This is particularly for Phil and those on commons-math, but if
anyone else is interested in getting set up just holler.
commons-math currently have a build set up in vmbuild.apache.org.
It's been down for little bit, but is now back up.
[
https://issues.apache.org/jira/browse/MATH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz reopened MATH-160:
--
Good catch, Luc. I thought clirr was set up to fail the build when this
happens. In any case, this needs
On 7/8/07, Jochen Wiedmann [EMAIL PROTECTED] wrote:
I second Rahul's opinion. I wouldn't want to build high barreers, but
I'd prefer to have them. Apart from that, I have never found it a
problem to join the Commons. In particular, considering my own
invitation which came basically with the
+1
Phil
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 note. The site is from trunk
If this relates to an open issue against [vfs], you should add your
comments to the JIRA ticket for the issue. If you have looked at the
open issues and this looks like a new problem, please open a new
ticket. To find or create issues against [vfs], follow this link:
[
https://issues.apache.org/jira/browse/MATH-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510905
]
Phil Steitz commented on MATH-167:
--
Thanks for reporting this. I see three alternatives to address - appreciate
On 7/6/07, Dain Sundstrom [EMAIL PROTECTED] wrote:
On Jul 5, 2007, at 7:13 AM, Phil Steitz wrote:
Thanks, Dain. I applied the patch.
I also patched the m1 and ant builds to work. The Ant now fails with
JDK 1.3, but unless someone screams loudly soon, we have moved the
minimum jdk level
On 7/6/07, Niall Pemberton [EMAIL PROTECTED] wrote:
Phil,
Dennis released Verson 3 of the parent pom a while ago - do you not
want to use that?
Doh! Thx
Phil
Niall
On 7/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: psteitz
Date: Thu Jul 5 23:04:45 2007
New Revision: 553747
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 commons validator and commons i18n to enhance
them for Struts.
On 7/6/07, Henri Yandell [EMAIL PROTECTED] wrote:
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
[
https://issues.apache.org/jira/browse/DBCP-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-228.
--
Resolution: Fixed
Patch applied. Thanks!
[dbcp] Managed Connection support
I just posted a patch JIRA which adds support for container managed
connections to DBCP. In an environment where you have an accessible
transaction manger such as Tomcat (when installed), Geronimo or
OpenEJB, this patch allows adds support for pooling managed
connections to an XA or non-XA data
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070704/dbcp.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
Phil
On 6/26/07, Jochen Wiedmann [EMAIL PROTECTED] wrote:
Hi,
I have prepared a further release candidate, with the following changes:
- Deprecation tags have been removed from the FileCleaner. (In the 1.3
branch only,
not in the trunk.) The discussion has clearly shown, that opinions
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070629/proxy.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1 - need to do this anyway.
On 6/29/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Hmm, it seems that I spoke too soon. We need a place in subversion to
put the tagged release. Since the pom is currently in sandbox-trunks
there simply is no tags directory to put the release in.
I propose that
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070628/lang.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 6/27/07, Henri Yandell [EMAIL PROTECTED] wrote:
Personally, my vote would be to say:
commons=committers
You mean all apache committers? I agree that we should continue the
tradition of granting commons karma to any committer who asks for it.
I don't know much about how this works in svn
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 6/23/07, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/23/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
This will be the first release and is important because it enables
reproducible
[
https://issues.apache.org/jira/browse/MATH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved MATH-160.
--
Resolution: Fixed
Applied a modified version of the patch, along with test cases, verified
against
On 6/23/07, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
This will be the first release and is important because it enables
reproducible builds and site generation for the sandbox components.
Since you have a policy against releasing sandbox
On 6/23/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 6/23/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Hi,
It is time to release version 1 of the commons-sandbox-parent. The
latest changes includes updating the parent to commons-parent-3 and
locking down the versions for plugins. Note that
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-97:
Attachment: timer.patch
EVICTION_TIMER is never cancelled
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-97:
Attachment: timer.patch
Attaching a patch (timer.patch) that makes the eviction timer a (lazy
initialized
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-97:
Attachment: (was: timer.patch)
EVICTION_TIMER is never cancelled
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-97:
Attachment: (was: timer.patch)
EVICTION_TIMER is never cancelled
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-97:
Attachment: timer.patch
EVICTION_TIMER is never cancelled
[
https://issues.apache.org/jira/browse/POOL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-102:
-
Fix Version/s: 2.0
Affects Version/s: 1.1
1.2
Thread waiting forever
[
https://issues.apache.org/jira/browse/POOL-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved POOL-102.
--
Resolution: Fixed
Patch applied. Thanks!
Thread waiting forever for borrowObject() cannot
[
https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-97:
Fix Version/s: 2.0
EVICTION_TIMER is never cancelled
[
https://issues.apache.org/jira/browse/POOL-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved POOL-95.
-
Resolution: Fixed
Fix Version/s: 2.0
Fix has been applied and will be included in 2.0
On 6/21/07, Henri Yandell [EMAIL PROTECTED] wrote:
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
[
https://issues.apache.org/jira/browse/POOL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506784
]
Phil Steitz commented on POOL-98:
-
OK, I understand the use case, but with the 1.3 pool impl, I don't think what
you
+1 on release notes, release contents, rat, META-INF, maven build, but
have to -1 on bits-to-mirrors, until I can verify the hashes:
ERROR: Checksum stored in commons-modeler-2.0.1-javadoc.jar.md5 does
not match commons-modeler-2.0.1-javadoc.jar
Correct hash: a5381f035c7076bffe8df548768449e2
I am not 100% sure that this is correct Jelly ant lib syntax, but I
think I now see the problem.
In maven.xml, you have
!-- create checksum for sources jar --
ant:checksum
file=${maven.dist.dir}/${maven.final.name}-sources.jar
property=jar.md5/
ant:echo message=${jar.md5}
+1 to no escape!
Phil
On 6/21/07, Niall Pemberton [EMAIL PROTECTED] wrote:
Rahul Akolkar is an existing Jakarta PMC member and Commons Committer.
He was against the proposal for Commons to become a TLP. Since that
vote passed and the Apache Board has now passed the resolution for
Commons to
+1!
Phil
On 6/21/07, Niall Pemberton [EMAIL PROTECTED] wrote:
Simon Kitching is an existing Jakarta PMC member and Commons
Committer. He was against the proposal for Commons to become a TLP.
Since that vote passed and the Apache Board has now passed the
resolution for Commons to become a TLP I
[
https://issues.apache.org/jira/browse/POOL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz reopened POOL-86:
-
Assignee: Phil Steitz (was: Sandy McArthur)
I agree with Rob that a better solution should be provided
+1 - looks good, including hashes now.
Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Leaving the ticket because this is really general discussion.
snip.
ok, I can understand this. Any time frame on compositepool / what is needed to
get the code release-ready?
As with all things apache, that depends on available volunteer cycles.
I posted a straw man roadmap for both [pool]
[
https://issues.apache.org/jira/browse/DBCP-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506620
]
Phil Steitz commented on DBCP-216:
--
Patch looks correct and appropriate to me, subject to the comments below
[
https://issues.apache.org/jira/browse/DBCP-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-97:
Fix Version/s: 1.3
setAutoCommit(true) when returning connection to the pool
[
https://issues.apache.org/jira/browse/DBCP-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-225:
-
Fix Version/s: 1.3
getConnection / borrowObject fails with NullPointerException
[
https://issues.apache.org/jira/browse/DBCP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506646
]
Phil Steitz commented on DBCP-212:
--
PoolableConnectionFactory.makeObject() has been synchronized since the initial
[
https://issues.apache.org/jira/browse/POOL-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506659
]
Phil Steitz commented on POOL-98:
-
I don't think we want to expose the _pool, since this is actually a linked list
There are still quite a few bugs open against [dbcp] and [pool]. We
also have an unreleased, improved pool impl in the compositepool
package. I would like to toss out some ideas for discussion about
where to go with these two components and guage interest in helping
out.
Recent releases:
[
https://issues.apache.org/jira/browse/MATH-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved MATH-166.
--
Resolution: Fixed
Patch applied. Thanks
Special functions not very accurate
[
https://issues.apache.org/jira/browse/MATH-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved MATH-158.
--
Resolution: Fixed
Modified version of patch applied.
Changes: made arguments doubles and used
On 6/19/07, Dion Gillard [EMAIL PROTECTED] wrote:
I believe you're right.
http://jakarta.apache.org/site/proposal.html#decisions/items/plan says
...Majority
approval is required before the public release can be made.
Yes, that is the policy, but I have never seen us move forward with a
[
https://issues.apache.org/jira/browse/DBCP-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz reopened DBCP-102:
--
[dbcp] setReadOnly setAutoCommit called too many times
[
https://issues.apache.org/jira/browse/DBCP-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated DBCP-102:
-
Fix Version/s: (was: 1.2.2)
1.3
Setting fix level to 1.3, as fix represents
[
https://issues.apache.org/jira/browse/DBCP-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz reopened DBCP-97:
-
Need to verify this fix is correct and necessary.
setAutoCommit(true) when returning connection to the pool
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070616/dbcp.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1
Builds happily, sigs and hashes are good and everything else looks good to me.
Thanks for rolling the source distro.
Phil
On 6/13/07, Torsten Curdt [EMAIL PROTECTED] wrote:
As (more or less) requested I've also created a source and binary
distributions
Sorry, but I have to agree with Niall on this - needs to be 2.0 with
the incompatible changes - and I would like very much for us to agree
once and for all on some versioning/deprecation rules. We seem to
have lost the old versioning guidelines (unless I am senile, we used
to have these on the
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070613/email.log
http://vmbuild.apache.org/~commons/nightly/logs//20070613/logging.log
http://vmbuild.apache.org/~commons/nightly/logs//20070613/finder.log
http://vmbuild.apache.org/~commons/nightly/logs//20070613/pipeline.log
Ignore this. All builds actually succeeded. Error in script made
worse last night :-(. Should be fixed now.
Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070612/beanutils.log
http://vmbuild.apache.org/~commons/nightly/logs//20070612/logging.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
On 6/12/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Dennis Lundberg wrote:
Phil Steitz wrote:
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070612/beanutils.log
http://vmbuild.apache.org/~commons/nightly/logs//20070612/logging.log
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070611/logging.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 6/11/07, Ben Speakmon [EMAIL PROTECTED] wrote:
Phil actually had to fix a bug in commons-nightly before the maven 2 file
would be honored, so after I asked about getting email working, logging
started working too.
On 6/11/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
I'm unsure why, but it
Type: Improvement
Affects Versions: 1.2.2
Reporter: Phil Steitz
Priority: Minor
Fix For: 1.3
Validation queries used when testOnBorrow and/or testOnReturn do not currently
support queryTimeouts. This should be configurable.
See http://www.mail
Failed build logs:
http://vmbuild.apache.org/~commons/nightly/logs//20070610/logging.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 6/10/07, Torsten Curdt [EMAIL PROTECTED] wrote:
So you are saying +1 for the assembly release ...but I don't get the
who needs what part.
What I meant was that I did not see it as a big user inconvenience to
bundle all of the jars into a single release, since they are
individually
On 6/7/07, Martin van den Bemt [EMAIL PROTECTED] wrote:
If the intention is to have a NullPointerException when null is passed, declare
it and throw it
specifically (that way you are in control of the exception). I think every
undocumented nullpointer
exception is a bug.
I would prefer
public abstract class DistributionFactory {
/**
@@ -59,16 +59,7 @@
* @return a new factory.
*/
public static DistributionFactory newInstance() {
-DistributionFactory factory = null;
-try {
-DiscoverClass dc = new DiscoverClass();
-
1 - 100 of 1427 matches
Mail list logo
