I have strong web-developer background, where in order to show client a demo I've uploaded a solution to demo environment and sent over a link. If case client asked to make changes, I did them in PhpStorm, dev-tested on local env, deployed in one-click from IDE and asked them to reload the page. In was that simple and very efficient.
Now, I am working in Java and I deeply miss those efficiency I had with PHP. Demo deployment stays simple, but changes are a total mess. I need to:
- Rebuild the bundle with Maven;
- Upload 100Mb to Nexus;
- Run a deployment via a specialized tool, which downloads 100Mb, erases old deployment and deploys everything again.
Most of the JARs inside the bundle - 3rd party libs - never change. Redeploying them seems inefficient.
I could use JRebel or tools of that kind, but I am not in the position to make the organization buy proprietary software.
I believe there are teams out there that couldn't rely on paid software too. How to do dev-deploy-test cycle faster by implementing smart architecture and using free tools?
Update: Take my apologies, if the question tastes a bit ranty. What I'd like to know is How do you dev-deploy-test at wherever you work? Only non-interpreted Java-like programming eco-systems are in scope of the question.