Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Hugo Trippaers <HTrippaers@schubergphilis.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Subject: Maven status (from my point of view)
Thread-Topic: Maven status (from my point of view)
Thread-Index: Ac2Kn7PkCBT4p4E8TVOsJqAUYxhoaQ==
Date: Tue, 4 Sep 2012 14:12:07 +0000
Message-ID: <6DE00C9FDF08A34683DF71786C70EBF029B4AF8E@SBPOMB402.sbp.lan>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hey all,

The switch to maven is coming along nicely I think, however we are not ther=
e yet. With the dependencies gone from the tree, the maven build is now the=
 easiest way to build CloudStack IMHO. All classes are properly compiled an=
d stored in jar files and dependencies are automagically downloaded to make=
 sure everything compiles. Over the last few days I've added packaging of t=
he systemvm.iso to the maven files and I did some work on the awsapi. The a=
wsapi is proving to be difficult as it has multiple results (.mar, .aar, .j=
ar files and a webapp). Maven doesn't really like this. On the other hand, =
maven has plugins to deal with axis2 and generate everything, so with a  bi=
t of work we should be able to simplify this. Test code is not compiled in =
some cases as there are some interesting circular references (test code for=
 server depending on vmware plugin comes to mind), that needs to be sorted =
if we want maven to be able to do its job.

I've spend the last two days to get packaging back into something that look=
s workable. Even though we want to move away from waf, it seemed like the b=
est way to fix the packaging for now. With the exception of awsapi all RPM =
packages are being built on my dev environment so that is looking good. I d=
on't have a debian environment yet, so I'm not able to test a debian build.=
 I haven't done any testing on the rpms yet, just verified that they are bu=
ild, hoping to do that tomorrow.

Couple of questions that I would like some feedback on:
* Maven includes the dependencies with their original filename, I believe w=
e used to ship our deps with cloud- prepended to the name. Now we need to e=
ither check if our dependencies aren't already supplied by the OS or put th=
em in a different directory, like /usr/share/java/cloud/*jar. What is the b=
est route to take?
* Awsapi should be split in three sub projects (directories)  I think, the =
autogenerated ec2 part, the autogenerated e3 part and cloudstack own code w=
hich might be distributed as a webapp.=20
* I've split the server rpm in two, one called server and contains all oss =
stuff and one called server-nonoss containing the modules that depend on no=
n-oss libs, is that ok?

Darren, is this more or less in line with the stuff you are doing?

Feedback, ideas, complaints anyone?

Will send an update when there is something to report.

Cheers,

Hugo