[jira] [Commented] (VFS-838) Port from Jsch to Apache Mina

[ https://issues.apache.org/jira/browse/VFS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727575#comment-17727575 ] Rob Spoor commented on VFS-838: --- [~christiangfk], I know it's an outdated SSH server. Like I said, updating

[jira] [Commented] (VFS-838) Port from Jsch to Apache Mina

[ https://issues.apache.org/jira/browse/VFS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726803#comment-17726803 ] Rob Spoor commented on VFS-838: --- A quick attempt to simply replace the dependency gives the following error

[jira] [Comment Edited] (VFS-838) Port from Jsch to Apache Mina

[ https://issues.apache.org/jira/browse/VFS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726799#comment-17726799 ] Rob Spoor edited comment on VFS-838 at 5/27/23 12:20 PM: - I tihnk option 2 is

[jira] [Commented] (VFS-838) Port from Jsch to Apache Mina

[ https://issues.apache.org/jira/browse/VFS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726799#comment-17726799 ] Rob Spoor commented on VFS-838: --- I tihnk option 2 is actually the best option. Its

[jira] [Comment Edited] (VFS-838) Port from Jsch to Apache Mina

[ https://issues.apache.org/jira/browse/VFS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726797#comment-17726797 ] Rob Spoor edited comment on VFS-838 at 5/27/23 12:17 PM: - I had a quick look at

[jira] [Commented] (VFS-838) Port from Jsch to Apache Mina

[ https://issues.apache.org/jira/browse/VFS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726797#comment-17726797 ] Rob Spoor commented on VFS-838: --- I had a quick look at this, but I found some references to JSch in the API.

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17567686#comment-17567686 ] Rob Spoor commented on CONFIGURATION-817: - You're welcome! > Upgrade to JUnit 5 >

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17567597#comment-17567597 ] Rob Spoor commented on CONFIGURATION-817: - [~mattjuntunen], can you update this ticket now

[jira] [Commented] (CONFIGURATION-815) Package depends on log4j 1.2.17

[ https://issues.apache.org/jira/browse/CONFIGURATION-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566801#comment-17566801 ] Rob Spoor commented on CONFIGURATION-815: - Why not switch to reload4j? It's a drop-in

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566408#comment-17566408 ] Rob Spoor commented on CONFIGURATION-817: - I've already removed almost all assertion

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565887#comment-17565887 ] Rob Spoor commented on CONFIGURATION-817: - In the mean time, I'm throwing away messages

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565123#comment-17565123 ] Rob Spoor commented on CONFIGURATION-817: - Is it perhaps an idea to split this ticket into

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565122#comment-17565122 ] Rob Spoor commented on CONFIGURATION-817: - How do we feel about using some more advanced

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565109#comment-17565109 ] Rob Spoor commented on CONFIGURATION-817: - To be honest, I used replace all per class to

[jira] [Updated] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor updated CONFIGURATION-817: Description: >From

[jira] [Updated] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor updated CONFIGURATION-817: Description: >From https://lists.apache.org/thread/ygtkpch0s7nss4vx8xfytwsbnv7mzss9

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564697#comment-17564697 ] Rob Spoor commented on CONFIGURATION-817: - See [CONFIGURATION-817: update to JUnit 5

[jira] [Commented] (CONFIGURATION-817) Upgrade to JUnit 5

[ https://issues.apache.org/jira/browse/CONFIGURATION-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564695#comment-17564695 ] Rob Spoor commented on CONFIGURATION-817: - Besides upgrading JUnit 5, we need to get rid

[jira] [Created] (CONFIGURATION-817) Upgrade to JUnit 5

Rob Spoor created CONFIGURATION-817: --- Summary: Upgrade to JUnit 5 Key: CONFIGURATION-817 URL: https://issues.apache.org/jira/browse/CONFIGURATION-817 Project: Commons Configuration Issue

[jira] [Closed] (IO-729) BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources

[ https://issues.apache.org/jira/browse/IO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor closed IO-729. Verified. > BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause > IllegalArgumentException in

[jira] [Updated] (IO-729) BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources

[ https://issues.apache.org/jira/browse/IO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor updated IO-729: - Fix Version/s: 2.12.0 > BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause >

[jira] [Commented] (IO-729) BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources

[ https://issues.apache.org/jira/browse/IO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17421585#comment-17421585 ] Rob Spoor commented on IO-729: -- I've updated the PR. > BrokenReader, BrokenWriter, BrokenInputStream,

[jira] [Commented] (IO-729) BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources

[ https://issues.apache.org/jira/browse/IO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420859#comment-17420859 ] Rob Spoor commented on IO-729: -- I've created a PR for the 3rd option:

[jira] [Commented] (IO-729) BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources

[ https://issues.apache.org/jira/browse/IO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420328#comment-17420328 ] Rob Spoor commented on IO-729: -- [~ggregory] I hadn't thought of a solution yet, I merely stated an issue. The

[jira] [Created] (IO-729) BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources

Rob Spoor created IO-729: Summary: BrokenReader, BrokenWriter, BrokenInputStream, BrokenOutputStream can cause IllegalArgumentException in combination with try-with-resources Key: IO-729 URL:

[jira] [Commented] (NET-665) Support for multiple FTPFileFilters

[ https://issues.apache.org/jira/browse/NET-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17249257#comment-17249257 ] Rob Spoor commented on NET-665: --- Is this really necessary? Unless you're stuck on Java 7 or lower (and I pity

[jira] [Commented] (IO-597) FileUtils.iterateFiles goes out of memory when executed for a directory with large number of files

[ https://issues.apache.org/jira/browse/IO-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17214739#comment-17214739 ] Rob Spoor commented on IO-597: -- Whatever solution uses {{File.listFiles}} will potentially have the same issue.

[jira] [Commented] (CONFIGURATION-794) Unclosed file handle when reading config from JAR file URL

[ https://issues.apache.org/jira/browse/CONFIGURATION-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211957#comment-17211957 ] Rob Spoor commented on CONFIGURATION-794: - Do you mean adding a flag somewhere to disable

[jira] [Commented] (CONFIGURATION-794) Unclosed file handle when reading config from JAR file URL

[ https://issues.apache.org/jira/browse/CONFIGURATION-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211884#comment-17211884 ] Rob Spoor commented on CONFIGURATION-794: - I've done some investigation, and the problem

[jira] [Closed] (IO-619) Support sub sequences in CharSequenceReader

[ https://issues.apache.org/jira/browse/IO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor closed IO-619. Fix Version/s: (was: 2.7.1) 2.7 Resolution: Fixed > Support sub sequences in

[jira] [Commented] (IO-619) Support sub sequences in CharSequenceReader

[ https://issues.apache.org/jira/browse/IO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119790#comment-17119790 ] Rob Spoor commented on IO-619: -- Done. > Support sub sequences in CharSequenceReader >

[jira] [Commented] (IO-619) Support sub sequences in CharSequenceReader

[ https://issues.apache.org/jira/browse/IO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17119049#comment-17119049 ] Rob Spoor commented on IO-619: -- I think this actually is in release 2.7:

[jira] [Updated] (IO-619) Support sub sequences in CharSequenceReader

[ https://issues.apache.org/jira/browse/IO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor updated IO-619: - Issue Type: New Feature (was: Improvement) > Support sub sequences in CharSequenceReader >

[jira] [Updated] (IO-619) Support sub sequences in CharSequenceReader

[ https://issues.apache.org/jira/browse/IO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor updated IO-619: - External issue URL: https://github.com/apache/commons-io/pull/91 > Support sub sequences in CharSequenceReader >

[jira] [Updated] (IO-619) Support sub sequences in CharSequenceReader

[ https://issues.apache.org/jira/browse/IO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor updated IO-619: - External issue ID: 91 > Support sub sequences in CharSequenceReader > --- >

[jira] [Created] (IO-619) Support sub sequences in CharSequenceReader

Rob Spoor created IO-619: Summary: Support sub sequences in CharSequenceReader Key: IO-619 URL: https://issues.apache.org/jira/browse/IO-619 Project: Commons IO Issue Type: Improvement

[jira] [Closed] (TEXT-154) StringEscapeUtils.escapeEcmaScript does not escape

[ https://issues.apache.org/jira/browse/TEXT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Spoor closed TEXT-154. -- Resolution: Not A Problem I missed that the / is already escaped. That turns into <\/script> which does not

[jira] [Created] (TEXT-154) StringEscapeUtils.escapeEcmaScript does not escape

Rob Spoor created TEXT-154: -- Summary: StringEscapeUtils.escapeEcmaScript does not escape Key: TEXT-154 URL: https://issues.apache.org/jira/browse/TEXT-154 Project: Commons Text Issue Type: Bug