[jira] Commented: (LANG-69) [lang] ToStringBuilder throws StackOverflowError when an Object cycle exists

[ https://issues.apache.org/jira/browse/LANG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468000 ] Henri Yandell commented on LANG-69: --- svn ci -m "Applying a modified version of Maarten Coene's patch for #LANG-69. A

svn commit: r500497 - /jakarta/commons/proper/lang/trunk/src/java/org/apache/commons/lang/builder/ToStringStyle.java

Author: bayard Date: Fri Jan 26 23:13:59 2007 New Revision: 500497 URL: http://svn.apache.org/viewvc?view=rev&rev=500497 Log: Fixed indentation/tabs. Eclipse wasn't setup right I guess Modified: jakarta/commons/proper/lang/trunk/src/java/org/apache/commons/lang/builder/ToStringStyle.java Mo

svn commit: r500495 - in /jakarta/commons/proper/lang/trunk/src: java/org/apache/commons/lang/builder/ReflectionToStringBuilder.java java/org/apache/commons/lang/builder/ToStringStyle.java test/org/ap

Author: bayard Date: Fri Jan 26 23:11:08 2007 New Revision: 500495 URL: http://svn.apache.org/viewvc?view=rev&rev=500495 Log: Applying a modified version of Maarten Coene's patch for #LANG-69. All unit tests pass; opinions would be very welcome though. Modified: jakarta/commons/proper/lang

[jira] Commented: (LANG-69) [lang] ToStringBuilder throws StackOverflowError when an Object cycle exists

[ https://issues.apache.org/jira/browse/LANG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467984 ] Henri Yandell commented on LANG-69: --- I think the first step is to drop the register in appendStart, then in appendInt

[jira] Commented: (LANG-69) [lang] ToStringBuilder throws StackOverflowError when an Object cycle exists

[ https://issues.apache.org/jira/browse/LANG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467980 ] Henri Yandell commented on LANG-69: --- Still pounding on this issue... Not sure if my refactoring of the registries is

[jira] Updated: (LANG-69) [lang] ToStringBuilder throws StackOverflowError when an Object cycle exists

[ https://issues.apache.org/jira/browse/LANG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell updated LANG-69: -- Attachment: LANG-69-refactor.patch Patch attached with a refactoring of the code to pull the duplicated re

[jira] Updated: (LANG-69) [lang] ToStringBuilder throws StackOverflowError when an Object cycle exists

[ https://issues.apache.org/jira/browse/LANG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell updated LANG-69: -- Attachment: LANG-69-refactor.patch > [lang] ToStringBuilder throws StackOverflowError when an Object cycle

[jira] Updated: (LANG-69) [lang] ToStringBuilder throws StackOverflowError when an Object cycle exists

[ https://issues.apache.org/jira/browse/LANG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell updated LANG-69: -- Attachment: (was: LANG-69-refactor.patch) > [lang] ToStringBuilder throws StackOverflowError when an O

[jira] Created: (CONFIGURATION-251) project.xml file references deprecated xml-apis-2.0.2

project.xml file references deprecated xml-apis-2.0.2 - Key: CONFIGURATION-251 URL: https://issues.apache.org/jira/browse/CONFIGURATION-251 Project: Commons Configuration Issue Type: Bug

Re: [VOTE] IO 1.3 (RC3)

+1 Henri Yandell wrote: > I've made a third release candidate of IO 1.3, tagged IO_1_3_RC3. > > Available at: > > http://people.apache.org/~bayard/commons-io/1.3-rc3/ > > Various build files, clirr/jardiff reports and the proposed site. > > [ ] +1 > [ ] -1 > > Vote to end on Monday (if it m

[jira] Resolved: (NET-150) Line terminator "/r/n" not properly traced in TelnetClient SpyStream

[ https://issues.apache.org/jira/browse/NET-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giancarlo Barresi resolved NET-150. --- Resolution: Fixed Fix Version/s: 1.4 Final Suggested PATCH: Modify the method

[jira] Created: (NET-150) Line terminator "/r/n" not properly traced in TelnetClient SpyStream

Line terminator "/r/n" not properly traced in TelnetClient SpyStream Key: NET-150 URL: https://issues.apache.org/jira/browse/NET-150 Project: Commons Net Issue Type: Bug

[jira] Closed: (FILEUPLOAD-124) Error while uploading the file - in Clusterd in Environment

[ https://issues.apache.org/jira/browse/FILEUPLOAD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed FILEUPLOAD-124. Resolution: Invalid Closing as Invaid [2 weeks later]. > Error while uploading the fil

[jira] Commented: (LANG-286) Serialization - not backwards compatible

[ https://issues.apache.org/jira/browse/LANG-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467846 ] Henri Yandell commented on LANG-286: The following had serialVersionUID set for the 2.2 release. There have been no

Re: [VOTE] IO 1.3 (RC3)

Oops :) Done. On 1/26/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: The md5 checksums include the "dist" directory in the name - can these be re-created without it please otherwise +1 from me. Niall On 1/26/07, Henri Yandell <[EMAIL PROTECTED]> wrote: > I've made a third release candidate o

[jira] Commented: (LANG-286) Serialization - not backwards compatible

[ https://issues.apache.org/jira/browse/LANG-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467834 ] David J. M. Karlsen commented on LANG-286: -- Any news on this? I'm extending NestableRuntimeException and Nest

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

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-jelly-tags-jaxme has an issue affecting its community integration. This

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

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-jelly-tags-jaxme has an issue affecting its community integration. This

[EMAIL PROTECTED]: Project commons-jelly-tags-soap (in module commons-jelly) failed

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-jelly-tags-soap has an issue affecting its community integration. This i

[EMAIL PROTECTED]: Project commons-jelly-tags-soap (in module commons-jelly) failed

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-jelly-tags-soap has an issue affecting its community integration. This i

Re: [VOTE] IO 1.3 (RC3)

The md5 checksums include the "dist" directory in the name - can these be re-created without it please otherwise +1 from me. Niall On 1/26/07, Henri Yandell <[EMAIL PROTECTED]> wrote: I've made a third release candidate of IO 1.3, tagged IO_1_3_RC3. Available at: http://people.apache.org/~ba

Re: LICENSE and NOTICE in javadoc jar (Was: [VOTE] IO 1.3 (RC3))

Agreed.. Mvgr, Martin Jörg Schaible wrote: > Then you need'em also in the --sources.jar ... > > Martin van den Bemt wrote on Friday, January 26, 2007 9:38 AM: > >> -1 to dropping that, since a javadoc jar is a release too, >> which needs a license and notice. If we >> haven't done that in the p

RE: LICENSE and NOTICE in javadoc jar (Was: [VOTE] IO 1.3 (RC3))

Then you need'em also in the --sources.jar ... Martin van den Bemt wrote on Friday, January 26, 2007 9:38 AM: > -1 to dropping that, since a javadoc jar is a release too, > which needs a license and notice. If we > haven't done that in the past, doesn't mean we have to > continue not to do that.

Re: LICENSE and NOTICE in javadoc jar (Was: [VOTE] IO 1.3 (RC3))

-1 to dropping that, since a javadoc jar is a release too, which needs a license and notice. If we haven't done that in the past, doesn't mean we have to continue not to do that. Mvgr, Martin Jochen Wiedmann wrote: > On 1/26/07, Henri Yandell <[EMAIL PROTECTED]> wrote: > >> 2) Javadoc jar for M