glassfish - What's a good workflow for coding a frontend for a Java EE application? -

the setup java ee on glassfish server running local on 1 machine , frontend development setup running local on machine, plus git collaboration.

i'm doing frontend work (mostly css, js , little html) exclusively. so, need browser-rendered html. right colleague publishes application on local glassfish, grabs rendered html firefox , pastes seperate frontend folder in our git repository.

this seems bad workflow.

i guess solve setting development server, don't have one, yet.

is there way rendered html without me running java tools (eclipse, java ee, glassfish) on machine?

it depends on want avoid not having things on machine.

if local machine low on resources, may not best scenario (depending on how light/heavyweight application is), if main goal not clutter machine unnecessary things, may want try vagrant.

i've created vagrantfile payara (a build of glassfish fixes bugs , includes hazelcast) means clone repo, type vagrant up vagrant ssh , you're logged in headless virtual machine payara running service.

if wanted stick glassfish, i'm sure there glassfish vagrantfiles out there too.

if added line provision script wget latest build of war autodeploy folder, workflow start vagrant image , visit application.

since headless vm, can run low resources.

the same approach different tools use docker, if you're familiar that.