Hmmm...
This all sounds odd. In general, mvn jetty:run (if all the Scala classes
are compiled) takes about 3 or 4 seconds, even on my slow box.
Is your CPU at 100%?
What kind of machine is hosting your ubuntu VM?
On Tue, May 26, 2009 at 11:18 AM, Joe Wass j...@folktunefinder.com wrote:
FWIW, it's a Mac Mini Intel Core 2 Duo with 2GB RAM @ 2GHz on Mac OS X
10.5.6 running Ubuntu Server 9.04 in Sun VirtualBox.
I'm virtualising because production will be an Ubuntu VM and I prefer
to work with VMs for dev. IIRC the CPU isn't working hard inside or
outside of the VM when it takes a
On Tue, May 26, 2009 at 12:08 PM, Joe Wass j...@folktunefinder.com wrote:
FWIW, it's a Mac Mini Intel Core 2 Duo with 2GB RAM @ 2GHz on Mac OS X
10.5.6 running Ubuntu Server 9.04 in Sun VirtualBox.
I'm virtualising because production will be an Ubuntu VM and I prefer
to work with VMs for
Ok, I have no real answers, but this is just an observation i've seen
sometimes on my mac(s) when doing dev with jetty (unrelated to lift).
Sometimes, and just sometimes it appears to get itself it a total melt
down and says its exited but checking the activity monitor shows that
it really is
Hi Joe,
I may be out on a limb here, but could this be a DNS issue with your VM
setup? For me, a 120 second timeout makes me look at network trouble
first. I too run VirtualBox on a mac for some stuff, but have found its
networking support just different enough from VMWare (my normal vm
