Hi folks, Just a quick update on this. I created the deps-ctrl branch off of master now that I actually have something to show.
If you take a look under deps you'll see it looks pretty bare. I've removed a number of the jars. There's also a few new ant targets you can use: resolveBuildDeps: This downloads the jars that I've removed that are necessary for building and places them in deps/ resolveOptBuildDeps: This downloads some of the jars for plugins that aren't in the default code path. (F5, and Libvirt for the moment). [1] resolveRuntimeDeps: This downloads all of the jars that weren't necessary for building CloudStack. I haven't gone though and verified that all of these jars are indeed necessary for running, though some obviously are. I've also removed a number of targets from build-all - currently for hypervisors only OVM is supported. Xen could be supported, and despite having the xenserverjava jar in place, I have removed XS/XCP support as well as KVM and VMware as they currently depend on dependencies with prohibited licenses. I've also removed NetScaler, F5, and NetApp support from the default build. So why is XenServer Java still there - well some of the db migration for 2.1->2.2 code depends on it for some reason. I think I have that worked out (I think the import is now unneeded.) but I haven't yet tried my fix, so it remains in place so that CloudStack builds cleanly. Also - CloudStack currently doesn't build with the default xenserverjava bits for 5.6.100 or 6.0, it depends on it's own fork, or pukes otherwise. I also still have the AWSAPI bits to process - I'll start a different thread on that momentarily as I have a few questions about that. Finally, I'd welcome help here, so if you are interested, please jump in. --David [1] I haven't been able to find easily downloadable source for all of the optional jars. (VMware, NetApp, etc)
