[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-10-05 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: 
OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch, 
> OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch, 
> OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-10-05 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: (was: 
OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch)

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch, 
> OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch, 
> OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-10-05 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: 
OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch, 
> OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch, 
> OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-10-05 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: (was: 
OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch)

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch, 
> OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch, 
> OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-10-05 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: 
OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch, 
> OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch, 
> OFBIZ-11192_0005-Use-Path-for-component-config-rootLocation-.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-09-24 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: 
OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch, 
> OFBIZ-11192_0004-Refactor-ComponentContainer-loadComponentFr.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-09-23 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: 
OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch, 
> OFBIZ-11192_0003-Use-java.nio.file-API-in-ComponentContainer.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-09-23 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Attachment: 
OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch

> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: 
> OFBIZ-11192_0001-Refactor-ComponentLoaderConfig-class.patch, 
> OFBIZ-11192_0002-Convert-Config-ofbizHome-and-Config-logDir-.patch
>
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (OFBIZ-11192) Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files

2019-09-11 Thread Mathieu Lirzin (Jira)


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

Mathieu Lirzin updated OFBIZ-11192:
---
Description: 
Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
manipulate the filesystem than {{java.io}}. For example the presence of a Path 
class allows more typesafe manipulation of file and directory names than using 
plain strings.

Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
maintainability and readability to move to the new {{java.nio.file}} API 
instead.

Some documentation regarding how to migrate to new API is available:

* https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
* https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping

  was:
Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
manipulate the filesystem than {{java.io}}. For example the presence of a Path 
class allows more typesafe manipulation of file and directory names than using 
plain strings.

Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
maintainability and readability to move to the new {{java.nio.file}} API 
instead.


> Use ‘java.nio.file’ API instead of ‘java.io’ when manipulating files
> 
>
> Key: OFBIZ-11192
> URL: https://issues.apache.org/jira/browse/OFBIZ-11192
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Mathieu Lirzin
>Assignee: Mathieu Lirzin
>Priority: Minor
>
> Since Java 1.7 the {{java.nio.file}} package provides a more modern way to 
> manipulate the filesystem than {{java.io}}. For example the presence of a 
> Path class allows more typesafe manipulation of file and directory names than 
> using plain strings.
> Currently OFBiz uses {{java.io}} exclusively but it would improve safety, 
> maintainability and readability to move to the new {{java.nio.file}} API 
> instead.
> Some documentation regarding how to migrate to new API is available:
> * https://docs.oracle.com/javase/tutorial/essential/io/fileio.html
> * https://docs.oracle.com/javase/tutorial/essential/io/legacy.html#mapping



--
This message was sent by Atlassian Jira
(v8.3.2#803003)