----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/6923/#review11060 -----------------------------------------------------------
Heya, This works, but a better fix would be to figure out why these targets depend on those vmwre tools. We need to be able to distribute console-proxy and build it without any dependencies on vmware stuff. Can you rewrite this patch to remove the dependencies on those three libs to vmware jars? If there are any errors we'll need to fix that. Cheers, Hugo - Hugo Trippaers On Sept. 5, 2012, 9:39 a.m., Hiroaki Kawai wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/6923/ > ----------------------------------------------------------- > > (Updated Sept. 5, 2012, 9:39 a.m.) > > > Review request for cloudstack. > > > Description > ------- > > I run mvn without -Dnonoss and got errors about vmware jar dependencies (with > empty m2 local repository). > > [ERROR] Failed to execute goal on project cloud-vmware-base: Could not > resolve dependencies for project > org.apache.cloudstack:cloud-vmware-base:jar:4.0.0-SNAPSHOT: The following > artifacts could not be resolved: com.cloud.com.vmware:vmware-vim:jar:1.0, > com.cloud.com.vmware:vmware-vim25:jar:1.0, > com.cloud.com.vmware:vmware-apputils:jar:1.0: Could not find artifact > com.cloud.com.vmware:vmware-vim:jar:1.0 in central > (http://repo.maven.apache.org/maven2) -> [Help 1] > > Here I attach a patch to fix this. > > > Diffs > ----- > > pom.xml 99b1177 > > Diff: https://reviews.apache.org/r/6923/diff/ > > > Testing > ------- > > mvn && mvn test > > > Thanks, > > Hiroaki Kawai > >
