Actually, the build reported success with no errors! I ended up blowing away my entire cloudstack vm and started over. Things seem to be working now. I actually run the management server ON devcloud itself, so the new memory requirements required me to up my settings (i.e.: export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx2g")
/boot/grub/grub.cfg I upped my xen "dom0_mem" so I could get a little more base memory. I was swapping quite badly when trying to launch jetty, and got memory errors along the way. -Ryan Dietrich On Feb 4, 2013, at 3:00 PM, Kelven Yang <kelven.y...@citrix.com> wrote: > It looks like your first command was actually failed to execute? > com.cloud.upgrade.DatabaseCreator is packaged in the artifact from the > first command. > > > Kelven > > > On 2/4/13 9:20 AM, "Ryan Dietrich" <r...@betterservers.com> wrote: > >> After a pull on the master branch, I am unable to deploy the database. >> >> I ran: >> mvn -P developer,systemvm clean install >> Then: >> mvn -P developer -pl developer,tools/devcloud -Ddeploydb >> I got: >> java.lang.ClassNotFoundException: com.cloud.upgrade.DatabaseCreator >> >> >> On Feb 4, 2013, at 9:40 AM, Sailaja Mada <sailaja.m...@citrix.com> wrote: >> >>> Hi, >>> >>> These are the observations with 4.1 master branch dev environment today >>> . >> >
