virtual machine - Is vagrant useful for java/javaee developers? -

virtual machine - Is vagrant useful for java/javaee developers? -

when working java/javaee usual development environment setup have locally (jdk installation, database, appserver etc). know lot of people in ruby/js world utilize virtual machines development (mainly vagrant).

i wonder if there efficient way set similar env java/javaee. suspect can install database server , application server jdk version on such virtual machine, regular development? still need have jdk installed locally, right? (i need ide work properly) need maven build project, need total maven local repo. , need deploy app on virtual machine's app server.

i can see no real advantage here (still having pieces of environment on both machines). have experience , can share me?

vagrant tool setting virtualbox virtual machine. brings table ability provision vm , ability pass provisioning recipe others.

this useful in ruby/js community because don't have compile step. way utilize code stays on local machine , runtime done on vm. if create alter on local computer running programme on vm instantly picks alter , runtime modified if code on vm. literally don't have have ruby/js installed on computer.

in java/.net world have compile step need java , jars need compile against on machine. lessens of usefulness of setup.

on other hand have databases, message queues, containers, etc. working , on team may pain shoot email , update db version , load new sample data. in vagrant 1 person needs create updates , can tell grab new vm , not have of upgrade steps yourself.

so still useful in compiled language less useful in scripting language.

java virtual-machine vagrant