Both the Agent and Server require Google GSON. This is not available from
the Ubuntu repositories, so we have to package it ourselfs.
Due to the fact that people might choose to run the Hypervisor on the same
host as the management server we can't have cloud-agent-deps conflict with cloud-deps
cloud-agent-deps now depends on cloud-deps so the hypervisor has Google GSON 1.7.1
This results in a number of extra JAR files to be installed on the hypervisor.
The management server also depends on a couple of these scripts, so renaming
to cloud-scripts makes more sence then installing cloud-agent-scripts.
In the future we might want to split this up in two packages.
cglib 2.2.2 is available in Ubuntu and Debian from the repositories, no need
to ship it in the cloud-deps package.
It's also not used by cloud-agent, but by cloud-utils, so place the dependency there.
Ubuntu 12.04 and Debian (testing) both ship from their repository, so there is no need
for us to distribute it in our packages.
We depend on it externally for our logging.
This involves removing a couple of JAR files from these packages:
* cloud-deps
* cloud-agent-deps
* cloud-client
A couple of libraries no longer have the cloud-* prefix or go renamed otherwise.
We no longer include the following libraries:
* netscaler
* iControl
* manageontap
* jnetpcap
* junit
* jetty
* vmware
* xenserver
These are not required anymore or not allowed license wise.
By adding these files to the *.conffiles file we prevent them from being overwritten by dpkg.
We don't want to overwrite these files, since they can contain very specific information regarding the setup.
Although this master branch doesn't contain 3.0.2 since we moved passed that
it didn't feel apprioriate to bump the version to 4.0.0 (yet).
This file should be updated to 4.0.0 at the point where we release 4.0
No need for these packages to depend on any cloud-agent package.
If they need files from this packages, then we need to move those files.
The client/management server should never depend on agent packages.
Although these bindings have to be removed for the first Apache release
we place the upstream JAR here.
The 0.4.5 bindings were homebrew and contained own code which wasn't sent upstream.
These changes were sent upstream and got into 0.4.8.
For now we keep the 0.4.8 bindings in the repo until we have a new build system in place
which handles this.
This is still however a release blocker since we can't distribute these bindings from the Apache servers!
