[
https://issues.apache.org/jira/browse/ACCUMULO-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886079#comment-13886079
]
John Vines commented on ACCUMULO-2267:
--------------------------------------
With this change, it also means we need to maintain an entirely new suite of
example accumulo-site files.
The changes made in ACCUMULO-1638 are very disruptive to all of the existing
scripts and examples we have in place. This issues presented in this ticket
should have been remedied with that ticket and weren't. I don't think this is
worth being a blocker so if these issues stand when we're down to the last
items left then I think we should revert ACCUMULO-1638 in 1.6.0-SNAPSHOT to
maintain previous functionality. Then it can be fixed properly in 1.7.0.
> problems running accumulo from RPM
> ----------------------------------
>
> Key: ACCUMULO-2267
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2267
> Project: Accumulo
> Issue Type: Bug
> Reporter: Michael Berman
> Fix For: 1.6.0
>
>
> - jps is called in the init.d scripts but it's not in the PATH it sets. on
> my centos box, it's in $JAVA_HOME/bin
> - in bin/accumulo, accumulo-start.jar is expected to be in
> $ACCUMULO_HOME/lib, but actually it's in $JAVA_HOME/accumulo
> - in bin/accumulo, accumulo-start.jar does not have version decoration, but
> the installed jar does
> - nothing else (other accumulo jars from $JAVA_HOME/accumulo, other
> dependencies from $ACCUMULO_HOME/lib) seems to be getting into the classpath.
> initial failure is NoClassDefFoundError:
> org/apache/commons/vfs2/provider/FileProvider
> i wonder if the standardization on RPM deployment locations is worth the
> departure from the standard accumulo deployment locations, at least for
> 1.6.0, since it seems like the impact on all the script infrastructure hasn't
> really been thought through yet, so close to the release.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
