On 09/17/2015 02:33 PM, Dmytro Shevchenko wrote: > Nice work. I compiled and install new version into local maven > repository, but now I can't compile Cloudstack with this library. I > changed dependency version in pom file to new, but got next exception > while compiling 'cloud-plugin-hypervisor-kvm': > > Konsole output > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile > (default-compile) on project cloud-plugin-hypervisor-kvm: Compilation > failure: Co > mpilation failure: > [ERROR] Picked up JAVA_TOOL_OPTIONS: > -javaagent:/usr/share/java/jayatanaag.jar > [ERROR] > /home/dmytro.shevchenko/test/cloudstack/plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java:[80,21] > error: cannot find symbol > [ERROR] symbol: class RadosException > [ERROR] location: package com.ceph.rados > > After investigation I found that class RadosException was moved to > Konsole output 'exceptions' subdirectory, but in > LibvirtComputingResource.java it import as " import > com.ceph.rados.RadosException;". Question is next, if I want compile > some release version with this new changes, which way would be > preferred? change import path LibvirtComputingResource.java and other > places where this class is used to > "com.ceph.rados.exceptions.RadosException"? > >
The latter would be the preferred indeed. I pushed a new version of rados-java and it's making it's way to Maven central now. When that is done I can push a PR for CloudStack which we might get backported to 4.5.3 Wido