On 09/06/2012 08:05 PM, Marcus Sorensen wrote:
Trying to get a working RPM build of 4.0 going... I assume my latest
issue is related to this. "class not found:
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource", if
someone is building RPMs isn't it safe to assume they want the
kvm/libvirt pieces? What was Wido's fix? I don't see this patch
applied to maven-waf, just 623f199b0378683e6f5f0c2b2b5c692b6504d16f as
latest.
Sorry, I completely missed this review!
The legal issue with KVM was approved like Elan posted, see LEGAL-144 as
I mentioned in the commit message.
I saw Elan's post on the ml, checked out the legal status and enabled
KVM again since we were allowed to do so :)
Wido
On Thu, Sep 6, 2012 at 11:04 AM, Hugo Trippaers
<[email protected]> wrote:
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6925/#review11105
-----------------------------------------------------------
Fixed by Wido in the maven-waf branch.
Thanks for the patch :-)
- Hugo Trippaers
On Sept. 5, 2012, 10:38 a.m., Hiroaki Kawai wrote:
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6925/
-----------------------------------------------------------
(Updated Sept. 5, 2012, 10:38 a.m.)
Review request for cloudstack.
Description
-------
Adding libvirt.org maven repository in pom.xml will automate the build, and we
can run kvm hypervisor plugin build without -Dnonoss. I also added exec:java
configuration so that we can test the hypervisor code easily.
Diffs
-----
plugins/hypervisors/kvm/pom.xml 8cdaa86
plugins/pom.xml 2a6ca31
Diff: https://reviews.apache.org/r/6925/diff/
Testing
-------
mvn && mvn test
Thanks,
Hiroaki Kawai
