I've recently started a new project at work and the development workflow feels incredibly outdated and inefficient. Here's how the team operates:
1. They access the .war file in the JBoss deployment folder.
2. They unzip it using 7-Zip.
3. Then they edit files directly in Notepad.
4. After that, they refresh the server to check their changes.
5. Finally, they must manually transfer those changes back to the actual codebase in VS Code, praying they remember everything.
This process honestly feels backward. Additionally, for other microservices, I'm required to rebuild WAR files each time I make a change and drag them into the JBoss deployment folder. I did create a script to make this a bit easier, but even with that, it feels clunky and inefficient. Is this kind of workflow normal in Java development setups, or am I just being picky?
5 Answers
The state of your workflow feels like a huge step back from modern practices. Seriously, someone on the team needs to take a couple of weeks to learn Maven and set up a proper build and deploy pipeline. It’s like everyone has forgotten how to do things efficiently!
Honestly, that workflow is super backward and definitely not standard practice. You should be able to streamline the deployment process. Ideally, it should flow like this: Code -> Build -> Package -> Deploy. Editing files in a .war like that is just asking for trouble!
This isn't just unprofessional; it’s a disaster waiting to happen. Someone's going to mess up and forget to sync their WAR file edits back to the source. There’s no way this retains integrity in a production environment! You should start looking for a job elsewhere.
Right? If they’re handling deployments this way, imagine what else is going wrong behind the scenes.
No chance that’s normal. Manually extracting and editing the WAR file is just ridiculous. A build tool like Maven or Gradle should handle building the WAR from your source code automatically. This should all be tied into your version control and CI/CD pipeline. Total game-changer!
Nope, definitely not the way it should be done. You should look into using Maven for building. It can vastly improve your workflow, streamline deployments, and even automate updates!
For sure! CI/CD setups with automatic builds and deployments are the way to go. That manual process is a recipe for disaster.
Exactly! In a modern setup, you should edit your code locally, and it should reflect automatically during development. Shaving time off the change/test cycle is super important.