Nice! Can't wait to look at this! --Alex
> -----Original Message----- > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers > Sent: Friday, September 20, 2013 3:40 AM > To: dev@cloudstack.apache.org > Subject: Moved the systemvm to its own maven project > > Hey all, > > Just a heads-up that i pushed this commit to master: > > commit 6c261042821c5597dab8d6be85dc59c948424e13 > Author: Hugo Trippaers <htrippa...@schubergphilis.com> > Date: Fri Sep 20 18:08:20 2013 +0800 > > Move the system vm to a separate maven project. > > All (almost) files belonging to the systemvm aer now centralize in the > systemvm directory. The code for the separate functions is still in the > services directory. This will make the code easier to understa > > > This commit effectively separates the code in the console-proxy from the > actual building of the systemvm.iso. The systemvm profile (mvn -Psystemvm) > will now control if the systemvm will be build entirely instead of just > determining if the iso will be built. For slight speed up in the complete > compile just leave the systemvm profile disabled. > > I think this will make it more clear for everybody where the systemvm is > located as its current location in console-proxy was a bit confusing. > > Testing done: > * Setting up devcloud with new build and new systemvm.iso > * Verified ssvm operation (nfs secondary storage) > * Verified cvm operation > > As with all maven changes don't forget to update the maven configuration in > your IDE. (For eclipse users, right-click on the project, Maven -> Update > Project) > > Cheers, > > Hugo
