[jira] [Created] (DBUTILS-89) Add method in BeanProcessor to populate an existing bean

2012-04-11 Thread Adam Dyga (Created) (JIRA)
Add method in BeanProcessor to populate an existing bean 
-

 Key: DBUTILS-89
 URL: https://issues.apache.org/jira/browse/DBUTILS-89
 Project: Commons DbUtils
  Issue Type: New Feature
Affects Versions: 1.4
Reporter: Adam Dyga


I really miss a method in BeanProcessor that would populate an *existing* bean 
with data from ResultSet, eg:

BeanProcessor.populateBean(ResultSet resultSet, Object bean) .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (COLLECTIONS-405) Add ListUtils.select()

2012-04-11 Thread Adam Dyga (Created) (JIRA)
Add ListUtils.select()
--

 Key: COLLECTIONS-405
 URL: https://issues.apache.org/jira/browse/COLLECTIONS-405
 Project: Commons Collections
  Issue Type: Wish
Affects Versions: 3.2.1
Reporter: Adam Dyga


It would be nice to have ListUtils.select() method, similar to 
CollectionUtils.select(). The main difference would be the type returned (List 
vs Collection).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Ravi Prakash (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251624#comment-13251624
 ] 

Ravi Prakash commented on IO-319:
-

I'll be happy to. I'm working on it now. I'm not sure how platform-independent 
the test code needs to be, but I'll give it a fair shot and hopefully you'll be 
able to guide me to a better iteration.


 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical

 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Gary D. Gregory (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251626#comment-13251626
 ] 

Gary D. Gregory commented on IO-319:


Great, thank you Ravi. 

 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical

 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Ravi Prakash (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ravi Prakash updated IO-319:


Attachment: commons-io-319.patch

Hi Gary,

Could you please review this patch? I wasn't able to find a way to create 
symlinks under Windows (FAT doesn't seem to support it) so the test code only 
checks under non-windows systems.


 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (VFS-409) Update Apache Commons Compress to 1.4 from 1.3

2012-04-11 Thread Gary D. Gregory (Created) (JIRA)
Update Apache Commons Compress to 1.4 from 1.3
--

 Key: VFS-409
 URL: https://issues.apache.org/jira/browse/VFS-409
 Project: Commons VFS
  Issue Type: Task
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Maven home: C:\Java\apache-maven-3.0.4\bin\..
Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_31\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Gary D. Gregory
 Fix For: 2.1


Update Apache Commons Compress to 1.4 from 1.3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (VFS-409) Update Apache Commons Compress to 1.4 from 1.3

2012-04-11 Thread Gary D. Gregory (Resolved) (JIRA)

 [ 
https://issues.apache.org/jira/browse/VFS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary D. Gregory resolved VFS-409.
-

Resolution: Fixed

SendingC:/svn/org/apache/commons/trunks-proper/vfs/pom.xml
Sending
C:/svn/org/apache/commons/trunks-proper/vfs/src/changes/changes.xml
Transmitting file data ...
Committed revision 1324814.

 Update Apache Commons Compress to 1.4 from 1.3
 --

 Key: VFS-409
 URL: https://issues.apache.org/jira/browse/VFS-409
 Project: Commons VFS
  Issue Type: Task
 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
 Maven home: C:\Java\apache-maven-3.0.4\bin\..
 Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
 Java home: C:\Program Files\Java\jdk1.6.0_31\jre
 Default locale: en_US, platform encoding: Cp1252
 OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Gary D. Gregory
 Fix For: 2.1


 Update Apache Commons Compress to 1.4 from 1.3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (MATH-779) ListPopulation Iterator allows you to remove chromosomes from the population.

2012-04-11 Thread Reid Hochstedler (Created) (JIRA)
ListPopulation Iterator allows you to remove chromosomes from the population.
-

 Key: MATH-779
 URL: https://issues.apache.org/jira/browse/MATH-779
 Project: Commons Math
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Reid Hochstedler
 Fix For: 3.1


Calling the iterator method of ListPopulation returns an iterator of the 
protected modifiable list. Before returning the iterator we should wrap it in 
an unmodifiable list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (MATH-779) ListPopulation Iterator allows you to remove chromosomes from the population.

2012-04-11 Thread Reid Hochstedler (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/MATH-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Reid Hochstedler updated MATH-779:
--

Attachment: MATH-779.txt

Proposed patch.

 ListPopulation Iterator allows you to remove chromosomes from the population.
 -

 Key: MATH-779
 URL: https://issues.apache.org/jira/browse/MATH-779
 Project: Commons Math
  Issue Type: Bug
Affects Versions: 3.0
Reporter: Reid Hochstedler
  Labels: genetics
 Fix For: 3.1

 Attachments: MATH-779.txt

   Original Estimate: 1h
  Remaining Estimate: 1h

 Calling the iterator method of ListPopulation returns an iterator of the 
 protected modifiable list. Before returning the iterator we should wrap it in 
 an unmodifiable list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Gary D. Gregory (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251677#comment-13251677
 ] 

Gary D. Gregory commented on IO-319:


On Windows, the sym link is called an NTFS junction point. This has been 
available since Windows 2000 according to 
https://en.wikipedia.org/wiki/NTFS_symbolic_link

MKLINK [[/D] | [/H] | [/J]] Link Target

/D  Creates a directory symbolic link.  Default is a file
symbolic link.
/H  Creates a hard link instead of a symbolic link.
/J  Creates a Directory Junction.
Linkspecifies the new symbolic link name.
Target  specifies the path (relative or absolute) that the new link
refers to.

 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Issue Comment Edited] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Gary D. Gregory (Issue Comment Edited) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251677#comment-13251677
 ] 

Gary D. Gregory edited comment on IO-319 at 4/11/12 3:34 PM:
-

On Windows, the sym link is called an NTFS junction point. This has been 
available since Windows 2000 according to 
https://en.wikipedia.org/wiki/NTFS_symbolic_link

{noformat}
MKLINK [[/D] | [/H] | [/J]] Link Target

/D  Creates a directory symbolic link.  Default is a file
symbolic link.
/H  Creates a hard link instead of a symbolic link.
/J  Creates a Directory Junction.
Linkspecifies the new symbolic link name.
Target  specifies the path (relative or absolute) that the new link
refers to.
{noformat}

Can you inlude Windows support in your patch? I am on Windows myself.

Thank you!

  was (Author: garydgregory):
On Windows, the sym link is called an NTFS junction point. This has been 
available since Windows 2000 according to 
https://en.wikipedia.org/wiki/NTFS_symbolic_link

MKLINK [[/D] | [/H] | [/J]] Link Target

/D  Creates a directory symbolic link.  Default is a file
symbolic link.
/H  Creates a hard link instead of a symbolic link.
/J  Creates a Directory Junction.
Linkspecifies the new symbolic link name.
Target  specifies the path (relative or absolute) that the new link
refers to.
  
 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Ravi Prakash (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ravi Prakash updated IO-319:


Attachment: commons-io-319.patch

Thanks for the review and pointer Gary! I've updated the patch for windows. I'm 
afraid I do not have a Windows machine to test this on. Could you please?

 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch, commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-278) Improve Tailer performance with buffered reads

2012-04-11 Thread James Herrmann (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251745#comment-13251745
 ] 

James Herrmann commented on IO-278:
---

Looks like theses patches have been rolled in. So, congrats to all on that. I 
went ahead and maven repo'ed your fork anyway because of the IO-269 issue. 
Tailer would read from start of file on frequent occasions. Not good when 
you're sending alerts! Sergio, does your fork handle the IO-269 bug? Right now, 
that's the last known issue I'm concerned about.

Thanks!

Jim

 Improve Tailer performance with buffered reads
 --

 Key: IO-278
 URL: https://issues.apache.org/jira/browse/IO-278
 Project: Commons IO
  Issue Type: Improvement
Affects Versions: 2.0.1
Reporter: Sergio Bossa
 Attachments: Tailer.diff, TailerTest.diff


 I noticed Tailer read performances are pretty poor when dealing with large, 
 frequently written, log files, and this is due to the use of RandomAccessFile 
 which does unbuffered reads, hence causing lots of disk I/O.
 So I improved the Tailer implementation by introducing buffered reads: it 
 works by loading large (configurable) file chunks in memory, and reading 
 lines from there; this enhances performances in my tests from 10x to 30x 
 depending on the file size.
 I also added two test cases: one to simulate reading of a large file (you can 
 use it to compare performances), the other to verify correct handling on 
 buffer breaks; obviously, all tests pass.
 I'm attaching the diff files, let me know if it's okay for you guys!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Gary D. Gregory (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251747#comment-13251747
 ] 

Gary D. Gregory commented on IO-319:


Thank you Ravi, the patch applies and tests OK but... How can this really work 
when FileUtils.isSymlink(File file) always returns true on Windows?

 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch, commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Issue Comment Edited] (IO-278) Improve Tailer performance with buffered reads

2012-04-11 Thread James Herrmann (Issue Comment Edited) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251745#comment-13251745
 ] 

James Herrmann edited comment on IO-278 at 4/11/12 5:08 PM:


Looks like theses patches have been rolled in. So, congrats to all on that. I 
went ahead and maven repo'ed your fork anyway because of the IO-279 issue. 
Tailer would read from start of file on frequent occasions. Not good when 
you're sending alerts! Sergio, does your fork handle the IO-269 bug? Right now, 
that's the last known issue I'm concerned about.

Thanks!

Jim

Edited: wrong bug #

  was (Author: herrjj):
Looks like theses patches have been rolled in. So, congrats to all on that. 
I went ahead and maven repo'ed your fork anyway because of the IO-269 issue. 
Tailer would read from start of file on frequent occasions. Not good when 
you're sending alerts! Sergio, does your fork handle the IO-269 bug? Right now, 
that's the last known issue I'm concerned about.

Thanks!

Jim
  
 Improve Tailer performance with buffered reads
 --

 Key: IO-278
 URL: https://issues.apache.org/jira/browse/IO-278
 Project: Commons IO
  Issue Type: Improvement
Affects Versions: 2.0.1
Reporter: Sergio Bossa
 Attachments: Tailer.diff, TailerTest.diff


 I noticed Tailer read performances are pretty poor when dealing with large, 
 frequently written, log files, and this is due to the use of RandomAccessFile 
 which does unbuffered reads, hence causing lots of disk I/O.
 So I improved the Tailer implementation by introducing buffered reads: it 
 works by loading large (configurable) file chunks in memory, and reading 
 lines from there; this enhances performances in my tests from 10x to 30x 
 depending on the file size.
 I also added two test cases: one to simulate reading of a large file (you can 
 use it to compare performances), the other to verify correct handling on 
 buffer breaks; obviously, all tests pass.
 I'm attaching the diff files, let me know if it's okay for you guys!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-278) Improve Tailer performance with buffered reads

2012-04-11 Thread Sergio Bossa (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251757#comment-13251757
 ] 

Sergio Bossa commented on IO-278:
-

Hi James, I think this is not the right place to discuss issues related to my 
fork, please use Tayler github tracker for that.

Thanks,

Sergio B.

 Improve Tailer performance with buffered reads
 --

 Key: IO-278
 URL: https://issues.apache.org/jira/browse/IO-278
 Project: Commons IO
  Issue Type: Improvement
Affects Versions: 2.0.1
Reporter: Sergio Bossa
 Attachments: Tailer.diff, TailerTest.diff


 I noticed Tailer read performances are pretty poor when dealing with large, 
 frequently written, log files, and this is due to the use of RandomAccessFile 
 which does unbuffered reads, hence causing lots of disk I/O.
 So I improved the Tailer implementation by introducing buffered reads: it 
 works by loading large (configurable) file chunks in memory, and reading 
 lines from there; this enhances performances in my tests from 10x to 30x 
 depending on the file size.
 I also added two test cases: one to simulate reading of a large file (you can 
 use it to compare performances), the other to verify correct handling on 
 buffer breaks; obviously, all tests pass.
 I'm attaching the diff files, let me know if it's okay for you guys!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Ravi Prakash (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251767#comment-13251767
 ] 

Ravi Prakash commented on IO-319:
-

Thanks Gary! Aah! I did not notice that. You probably meant isSymLink always 
returns false
bq. Note: the current implementation always returns false if the system is 
detected as Windows using FilenameUtils#isSystemWindows()
causing isSymLink to always be true on Windows. I guess the real fix would be 
to make the isSymlink() method not do that. Could you please append to the 
patch and fix it on Windows? I'm sorry I don't have a Windows machine :(

 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch, commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IO-319) FileUtils.sizeOfDirectory follows symbolic links.

2012-04-11 Thread Sebb (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IO-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251777#comment-13251777
 ] 

Sebb commented on IO-319:
-

Symbolic links are likely to be very rare on Windows.
IMO it does not matter if the patch does not fix the crash for Windows hosts, 
so long as it does not otherwise change the behaviour on Windows.


 FileUtils.sizeOfDirectory follows symbolic links.
 -

 Key: IO-319
 URL: https://issues.apache.org/jira/browse/IO-319
 Project: Commons IO
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Ravi Prakash
Priority: Critical
 Attachments: commons-io-319.patch, commons-io-319.patch


 First of all Thanks tons Apache Commons folks for all the amazing work! :) My 
 first JIRA. Yayyy. I contributed B-)
 A symbolic link may create a cycle and so sizeOfDirectory crashes with an 
 IllegalArgumentException. e.g. 
 {noformat}
 $ tree test
 test
 ├── file
 └── ravi
 ├── cycle - ../../test
 └── file
 {noformat}
 causes FileUtils.sizeOfDirectory to crash like so
 {noformat}
 java TestJAVA
 Exception in thread main java.lang.IllegalArgumentException: 
 somepath/test/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle/ravi/cycle
  does not exist
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2053)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 at org.apache.commons.io.FileUtils.sizeOf(FileUtils.java:2057)
 at 
 org.apache.commons.io.FileUtils.sizeOfDirectory(FileUtils.java:2089)
 {noformat}
 We faced the same issue in Hadoop :(. Checkout 
 https://issues.apache.org/jira/browse/HADOOP-6963 for our solution

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (SANSELAN-68) Incorrect reading Physical Width/Height Dpi and Physical Width/Height Inch from TIFF files

2012-04-11 Thread Damjan Jovanovic (Resolved) (JIRA)

 [ 
https://issues.apache.org/jira/browse/SANSELAN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damjan Jovanovic resolved SANSELAN-68.
--

   Resolution: Fixed
Fix Version/s: 1.0

Patch applied to latest SVN. Thank you for your contribution!

 Incorrect reading Physical Width/Height Dpi and Physical Width/Height Inch 
 from TIFF files
 --

 Key: SANSELAN-68
 URL: https://issues.apache.org/jira/browse/SANSELAN-68
 Project: Commons Sanselan
  Issue Type: Bug
  Components: Format: TIFF
Affects Versions: 1.0, 1.1, 1.x
Reporter: VVD
  Labels: patch
 Fix For: 1.0

 Attachments: sanselan-tiff-dpi.diff


 Width: 3509
 Physical Width Dpi: 4650
 Physical Width Inch: 1169.667
 Height: 2481
 Physical Height Dpi: 4650
 Physical Height Inch: 827.00024
 {code}
 TiffImageParser.java (196):
 -case 3: // Meter
 -unitsPerInch = 0.0254;
 +case 3: // Centimeter
 +unitsPerInch = 2.54;
 (c) http://partners.adobe.com/public/developer/en/tiff/TIFF6.pdf
 TiffImageParser.java (218):
 -physicalWidthDpi = (int) (XResolutionPixelsPerUnit / 
 unitsPerInch);
 +physicalWidthDpi = (int) Math.round(XResolutionPixelsPerUnit 
 * unitsPerInch);
 TiffImageParser.java (226):
 -physicalHeightDpi = (int) (YResolutionPixelsPerUnit / 
 unitsPerInch);
 +physicalHeightDpi = (int) 
 Math.round(YResolutionPixelsPerUnit * unitsPerInch);
 {code}
 After this patch I got correct values:
 Width: 3509
 Physical Width Dpi: 300
 Physical Width Inch: 11.69667
 Height: 2481
 Physical Height Dpi: 300
 Physical Height Inch: 8.2700024
 May be need to patch writing of tiff image too - don't know.
 P.S. GIMP show values: 300,000, 300,000, 11,697, 8,270.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (SANSELAN-71) Software field is missing in Exif TagConstant and Changing the order of reader.getbyteorder in Tiffimage parser

2012-04-11 Thread Damjan Jovanovic (Resolved) (JIRA)

 [ 
https://issues.apache.org/jira/browse/SANSELAN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damjan Jovanovic resolved SANSELAN-71.
--

   Resolution: Fixed
Fix Version/s: 1.0

Patch applied, thank you!


 Software field is missing in Exif TagConstant and Changing the order of 
 reader.getbyteorder in Tiffimage parser
 ---

 Key: SANSELAN-71
 URL: https://issues.apache.org/jira/browse/SANSELAN-71
 Project: Commons Sanselan
  Issue Type: Bug
 Environment: W-7
Reporter: Piyush Kapoor
Priority: Minor
 Fix For: 1.0

 Attachments: sanselan.patch

   Original Estimate: 1m
  Remaining Estimate: 1m

 Some fields like Software has been removed while modifying ExifTagConstants .
 In tiffimagepareser line reader.getbytereader should be below 
 reader.readFirstDirectory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira