Robert Munteanu created JCR-3666:
------------------------------------
Summary: FileVault: VaultFsConfig11 references incorrect classes
from prior versions
Key: JCR-3666
URL: https://issues.apache.org/jira/browse/JCR-3666
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-jcr-commons
Reporter: Robert Munteanu
Priority: Minor
I stumbled upon this by accident, so I can't say whether this has unintended
side effects or not, but just to make sure...
VaultFsConfig11 references classes from prior mappings
{code}
Map<String, String> m = helper.getMappings();
m.put("org.apache.jackrabbit.vault.fs.imprt.FolderArtifactHandler",
"org.apache.jackrabbit.vault.fs.impl.io.FileArtifactHandler");
m.put("org.apache.jackrabbit.vault.fs.imprt.FileArtifactHandler",
"org.apache.jackrabbit.vault.fs.impl.io.FileArtifactHandler");
m.put("org.apache.jackrabbit.vault.fs.imprt.GenericArtifactHandler",
"org.apache.jackrabbit.vault.fs.impl.io.GenericArtifactHandler");
m.put("org.apache.jackrabbit.vault.fs.imprt.NodeTypeArtifactHandler",
"org.apache.jackrabbit.vault.fs.impl.io.NodeTypeArtifactHandler");
m.put("org.apache.jackrabbit.vault.fs.filter.ItemFilter",
"org.apache.jackrabbit.vault.fs.api.ItemFilter");
m.put("org.apache.jackrabbit.vault.fs.filter.PathFilter",
"org.apache.jackrabbit.vault.fs.api.PathFilter");
{code}
But since there was no prior org.apache.jackrabbit.vault.fs.imprt package, I
guess that this is incorrect, and that the mappings should include both the
previous class names and the class names which were in effect before FileVault
was donated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
