when you fire up a vagrant up, it will mount as defalt, the current folder as /vagrant in the virtual machine, and will map the local 2222 as 22 in the remote machine.
so, if you have your ide in your computer, from one directory, you can mount current directory as vagrant mount a common path for scripts and binaries map port 80/443/8080 to guest 80/443/8080 in that way, the IDE should be able to connect to some path for software, then you can compile the software, and the VM will have the compiled bits already if you need to restart a service, you can use vagrant ssh default -c "sudo command> example vagrant ssh defaults -c "sudo service tomcat restart" Alvaro. On Sat, Feb 8, 2014 at 5:17 AM, Robert Gründler <[email protected]> wrote: > Hi, > > vagrant is an awesome tool for developing applications written in > scripting languages. I'm currently exploring ways to integrate this > workflow with > applications that run on the JVM. > > My question: To really use the advantages of vagrant, one would need to > run the whole JVM inside a vagrant container, and connect to it > from the IDE as a remote JVM, right? > > Or are there other (better) possibilities i'm not aware of? > > > regards > > > -robert > > > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
