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: 116

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: Local First – How To Build Software Which Still Works After the Acquihire

Alex Good discusses the fragility of modern cloud-dependent apps and shares a roadmap for "local-first" software. By leveraging a Git-like DAG structure and Automerge, he explains how to move from brittle client-server models to resilient systems where data lives on-device. He explores technical implementation, rich-text merging, and how this infrastructure simplifies engineering workflows.

By Alex Good

Article: Stateful Continuation for AI Agents: Why Transport Layers Now Matter

Agent workflows make transport a first-order concern. Multi-turn, tool-heavy loops amplify overhead that is negligible in single-turn LLM use. Stateful continuation cuts overhead dramatically. Caching context server-side can reduce client-sent data by 80%+ and improve execution time by 15–29% .

By Anirudh Mendiratta

Presentation: State of Play: AI Coding Assistants

Birgitta Böckeler discusses the rapid evolution of AI agents, moving beyond "vibe coding" to sophisticated context engineering. She explains how architectural constraints and "harness engineering" create the safety nets required for autonomous code generation. She shares vital insights for leaders on balancing speed with maintainability, security risks, and the cost of AI autonomy.

By Birgitta Böckeler

Inside Spotify’s 2025 Wrapped Archive: AI Narratives at Scale and the Privacy Trade‑Off

Spotify's engineering team developed the 2025 "Wrapped Archive," generating 1.4 billion personalized reports for 350 million users. This system identifies key listening days and crafts narratives using a language model. As companies increasingly provide narrative recaps, concerns about user privacy and data tracking persist, necessitating a balance between insights and privacy safeguards.

By Matt Foster

Presentation: When Every Bit Counts: How Valkey Rebuilt Its Hashtable for Modern Hardware

Madelyn Olson discusses the evolution of Valkey's data structures, moving away from "textbook" pointer-chasing HashMaps to more cache-aware designs. She explains the implementation of "Swedish" tables to maximize memory density. She shares insights on systems intuition, memory prefetching, and the rigorous testing needed for mission-critical caches.

By Madelyn Olson

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service