[
https://issues.apache.org/jira/browse/VFS-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated VFS-378:
--------------------------------
Description:
Right you get:
{noformat}
"Unknown message with code "vfs.provider.tar/open-tar-file.error"."
{noformat}
Instead of:
{noformat}
"Could not open Tar file "C:\some\path\to\a\file".".
{noformat}
The following are missing from
{{core/bin/org/apache/commons/vfs2/Resources.properties}}:
{noformat}
vfs.provider.tar/open-tar-file.error=Could not open Tar file "{0}".
vfs.provider.tar/close-tar-file.error=Could not close Tar file "{0}".
{noformat}
was:
The following are missing from
{{core/bin/org/apache/commons/vfs2/Resources.properties}}:
vfs.provider.tar/open-tar-file.error=Could not open Tar file "{0}".
vfs.provider.tar/close-tar-file.error=Could not close Tar file "{0}".
> Tar error message are missing from resource file
> ------------------------------------------------
>
> Key: VFS-378
> URL: https://issues.apache.org/jira/browse/VFS-378
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: C:\Java\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_29\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary D. Gregory
> Assignee: Gary D. Gregory
> Fix For: Nightly Builds
>
>
> Right you get:
> {noformat}
> "Unknown message with code "vfs.provider.tar/open-tar-file.error"."
> {noformat}
> Instead of:
> {noformat}
> "Could not open Tar file "C:\some\path\to\a\file".".
> {noformat}
> The following are missing from
> {{core/bin/org/apache/commons/vfs2/Resources.properties}}:
> {noformat}
> vfs.provider.tar/open-tar-file.error=Could not open Tar file "{0}".
> vfs.provider.tar/close-tar-file.error=Could not close Tar file "{0}".
> {noformat}
--
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
