[
https://issues.apache.org/jira/browse/ACCUMULO-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807487#comment-13807487
]
John Vines commented on ACCUMULO-1514:
--------------------------------------
So it boils down to this switch {code}switch (fo.getType()) {
case FILE:
classpath.add(fo);
pathsToMonitor.add(fo);
break;
case FOLDER:
pathsToMonitor.add(fo);
for (FileObject child : fo.getChildren()) {
classpath.add(child);
}
break;
case IMAGINARY:...{code}
So this code always adds all children, but not the folder to the classpath. I
can see two solutions -
1. Treat files and folders exactly the same (folder will be on classpath
instead of all children)
2. Explicitly add the folder to the classpath as well as it's children (folder
and all children will be on classpath)
> AccumuloVFSClassloader incorrectly treats folders as folders of jar files
> -------------------------------------------------------------------------
>
> Key: ACCUMULO-1514
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1514
> Project: Accumulo
> Issue Type: Bug
> Reporter: Christopher Tubbs
> Assignee: John Vines
> Fix For: 1.6.0
>
>
> Specifying a directory of classes is incorrectly interpreted as a directory
> of jars in the general.dynamic.classpaths configuration property.
> Example: adding a path such as *_$ACCUMULO_HOME/core/target/classes_* gets
> incorrectly interpreted as *_$ACCUMULO_HOME/core/target/classes/\*_* and
> evaluates to *_$ACCUMULO_HOME/core/target/classes/org_* and
> *_$ACCUMULO_HOME/core/target/classes/META-INF_*, but *NOT* to
> *_$ACCUMULO_HOME/core/target/classes_* as expected.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
