[ https://issues.apache.org/jira/browse/ACCUMULO-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277499#comment-16277499 ]
Keith Turner commented on ACCUMULO-4753: ---------------------------------------- So this is caused by having two different versions of commons beanutils on the classpath? I wonder if this could be avoided by modifying the classpath to only have one version that works for both commons config versions. > Update to commons-configuration2 > -------------------------------- > > Key: ACCUMULO-4753 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4753 > Project: Accumulo > Issue Type: Task > Reporter: Josh Elser > Assignee: Josh Elser > Priority: Critical > > I'm looking at what it would take to get Accumulo working against Hadoop 3. > Thankfully, the only issue seems to be around the commons-configuration2 > update that Hadoop has changed to. With our use of commons-configuration (1) > for ClientConfiguration and others, this brings in multiple versions of > commons-beanutils artifacts which result in exceptions at runtime. > I think the quickest solution is to just upgrade ourselves to use > commons-configuration2. The "long-term" solution is to try to switch over to > the shaded jars that Hadoop is publishing (but I'm reticent to sign up for > that right now :P). > I think we need to have a discussion about where we want to land this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)