[jira] Created: (LANG-557) Javadoc wrong for StringUtils startsWith, startsWithIgnoreCase, endsWith and endsWithIgnoreCase

Javadoc wrong for StringUtils startsWith, startsWithIgnoreCase, endsWith and endsWithIgnoreCase --- Key: LANG-557 URL: https://issues.apache.org/jira/browse/LANG-557

[jira] Commented: (NET-89) [net] TelnetClient broken for binary transmissions + solution

[ https://issues.apache.org/jira/browse/NET-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781119#action_12781119 ] Shlomy Reinstein commented on NET-89: - I have a different case in which the

[jira] Resolved: (LANG-501) Add support for background initialization

[ https://issues.apache.org/jira/browse/LANG-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Heger resolved LANG-501. --- Resolution: Fixed The patch for CallableBackgroundInitializer was applied in revision 883101. Add

[jira] Resolved: (MATH-315) GeneticAlgorithm: Register number of populations evolved during evolve()

[ https://issues.apache.org/jira/browse/MATH-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-315. -- Resolution: Fixed Fix Version/s: 2.1 Patch applied in r883132, with following changes: * improved

[jira] Created: (DBCP-307) PoolingConnection.PStmtKey.equals() and cpdsadapter.PooledConnectionImpl.PStmtKey.equals() don't check for null or the correct class

PoolingConnection.PStmtKey.equals() and cpdsadapter.PooledConnectionImpl.PStmtKey.equals() don't check for null or the correct class Key:

[jira] Updated: (DBCP-307) PoolingConnection.PStmtKey.equals() and cpdsadapter.PooledConnectionImpl.PStmtKey.equals() don't check for null or the correct class

[ https://issues.apache.org/jira/browse/DBCP-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated DBCP-307: -- Attachment: dbcp_307.txt PoolingConnection.PStmtKey.equals() and cpdsadapter.PooledConnectionImpl.PStmtKey.equals()

[jira] Commented: (CODEC-89) new Base64().encode() appends a CRLF, and chunks results into 76 character lines

[ https://issues.apache.org/jira/browse/CODEC-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781274#action_12781274 ] Gary Gregory commented on CODEC-89: --- What a pickle. The current behavior is documented in

[jira] Commented: (CODEC-88) Base32 encoder

[ https://issues.apache.org/jira/browse/CODEC-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781277#action_12781277 ] Gary Gregory commented on CODEC-88: --- Sure, submit a patch! :) Base32 encoder

[jira] Commented: (CODEC-91) Handling of embedded padding in base64 encoded data changed in 1.4

[ https://issues.apache.org/jira/browse/CODEC-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781278#action_12781278 ] Gary Gregory commented on CODEC-91: --- The old behavior was a bug I think. From the spec

[jira] Commented: (CODEC-89) new Base64().encode() appends a CRLF, and chunks results into 76 character lines

[ https://issues.apache.org/jira/browse/CODEC-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781295#action_12781295 ] Julius Davies commented on CODEC-89: Could we put out a fix as 1.4.1 ? new

[jira] Commented: (CODEC-91) Handling of embedded padding in base64 encoded data changed in 1.4

[ https://issues.apache.org/jira/browse/CODEC-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781297#action_12781297 ] Julius Davies commented on CODEC-91: FYI: there are two additional changes to the

[jira] Commented: (CODEC-89) new Base64().encode() appends a CRLF, and chunks results into 76 character lines

[ https://issues.apache.org/jira/browse/CODEC-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781305#action_12781305 ] Gary Gregory commented on CODEC-89: --- I see a change for a 1.4.1 or a 1.5 as the same issue

[jira] Commented: (DBCP-307) PoolingConnection.PStmtKey.equals() and cpdsadapter.PooledConnectionImpl.PStmtKey.equals() don't check for null or the correct class

[ https://issues.apache.org/jira/browse/DBCP-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781308#action_12781308 ] Phil Steitz commented on DBCP-307: -- Understand the point on bad practice, but this looks