I need to setup a web based java project for 6 Developers.

How i can achieve that all 6 developers work will generate a single war file without much hassle.

Please help me

Thanks in advance

Views: 104

Replies to This Discussion

Short Answer - Use Maven2 and Subversion (SVN).

Long Answer -
I recommend you use a Source Code Control program such as Subversion. All of your developers need to check code into and out of this.

Configure the subversion project with Maven2 (you could use Ant) to build a single war file.

Finally: You need to state to your developers you want a single WAR file for deployment. (And your developers should have already asked you how you want this deployed. Exploded WAR vs. Single (or multiple) WAR files.
I agree with the previous poster except for one thing, I would add Hudson to the mix. Hudson is a very powerful tool that you can use to fire off whatever building you want to do using maven. So the steps would go something like this...

1.) User checks code into Subversion
2.) Hudson Recognizes the new commit and uses maven to build/run tests
3.) Hudson can then automatically deploy to whatever environment.

Of course you should also set up multiple environments so that commits are not automatically deployed to prod.

Long story short, research Maven, Subversion, and Hudson.
These are basic infrastructure question, and I would suggest you re-use what's in your team's best talents first. Check with your team lead for his expertise in these area first. Everyone will have their own preference, and they work most efficiently with their strong areas. If you already got a team of 6, one would need to make decision for these and lead others to follow. Let the lead do what he does best with. If he is not good at it, he probably shouldn't be the lead in the first place.

With that said, I personally prefer a java development with these tools:
* Source Control: Mecurial (hg)
* BuildTool: Maven2 + Nexus Repository Manager
* Editor/IDE: JEdit and Eclipse with M2Eclipse plugin
* Project Management/Issue Tracker: Jira or Bugzilla
* Wiki: Confluence or MoinMoin
* BuiltServer: Hudson

Good luck with your team.

/Z
Thanks every body . I will try to set up the project. I will post again once its done.

RSS

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Presentation: The Ideal Micro-Frontends Platform

Luca Mezzalira shares a decision framework for micro-frontends, covering composition, routing, and communication. He explains how to structure "stream-aligned" teams and use a "tiger team" for foundational architecture. He also discusses the sociotechnical benefits of reducing external dependencies and shares how to use guardrails and discovery services to achieve 25+ deployments per day.

By Luca Mezzalira

Agoda’s API Agent Converts Any API to MCP with Zero Code and Deployments

Agoda engineers developed API Agent, enabling a single MCP server to access any internal REST or GraphQL API with zero code and zero deployments. The system reduces overhead from multiple APIs, supports AI-assisted queries, and uses in-memory SQL post-processing for safe, scalable data handling across internal services.

By Leela Kumili

Podcast: [Video Podcast] Building Resilient Event-Driven Microservices in Financial Systems with Muzeeb Mohammad

In this episode, Thomas Betts chats with Muzeeb Mohammad about building event-driven microservices for financial systems. The discussion covers some of the core principles and patterns for event-driven architectures, reasons for using these patterns, and some of the challenges related to finance and other highly-regulated industries.

By Muzeeb Mohammad

Google Explores Scaling Principles for Multi-agent Coordination

Google Research tried to answer the question of how to design agent systems for optimal performance by running a controlled evaluation of 180 agent configurations. From this, the team derived what they call the "first quantitative scaling principles for AI agent systems", showing that multi-agent coordination does not reliably improve results and can even reduce performance.

By Sergio De Simone

Article: Architecting Agentic MLOps: A Layered Protocol Strategy with A2A and MCP

In this article, the authors outline protocols for building extensible multi-agent MLOps systems. The core architecture deliberately decouples orchestration from execution, allowing teams to incrementally add capabilities via discovery and evolve operations from static pipelines toward intelligent, adaptive coordination.

By Shashank Kapoor, Sanjay Surendranath Girija, Lakshit Arora

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service