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

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

From Camera to Cloud: Netflix’s Scalable Media Processing Pipeline

Netflix has detailed a cloud-based system for scaling camera file processing across global film and TV workflows. The pipeline handles ingest, validation, metadata extraction, and media transformation at scale using FilmLight API and distributed compute. It standardizes workflows across editorial, VFX, and color pipelines, improving consistency and reducing manual handling across productions.

By Leela Kumili

Presentation: Write-Ahead Intent Log: A Foundation for Efficient CDC at Scale

Vinay Chella and Akshat Goel discuss the challenges of running traditional CDC across heterogeneous databases during peak order traffic. They explain how Debezium hit limits under high load and share how they built Write-Ahead Intent Log (WAIL) - a custom architecture that utilizes a dumb producer proxy and a smart consumer pattern to cleanly separate the intent from the state payload.

By Vinay Chella, Akshat Goel

How Lightweight ADRs and Architectural Advice Forums Can Support Architectural Decisions

How we decide is at the core of architecture, and the architecture advice process is a way to decentralize architectural decisions. It needs to be supported by Architecture Decision Records because of the speed at which technology and systems move, and can be complemented by a weekly architecture advice forum.

By Ben Linders

Ky 2.0 Fetch API Wrapper with Revamped Hooks, Smarter Timeouts, and Built-In Schema Validation

Ky 2.0 is an open-source JavaScript HTTP client built on the Fetch API, featuring significant updates such as consolidated hook handling, enhanced timeout management, and improved URL processing. The release includes response validation through schema validation libraries and addresses migration from earlier versions. It aims to provide a lightweight alternative to axios.

By Daniel Curtis

VS Code 1.123 Adds Two-Hour Extension Update Delay to Limit Supply Chain Attacks

VS Code 1.123 adds a two-hour delay before auto-updating extensions to newly published versions, creating a revocation window against supply chain attacks. The delay does not apply to trusted publishers like Microsoft, GitHub, and OpenAI. Similar cooldown mechanisms have now spread across pip, RubyGems, npm, pnpm, Yarn, and Bun.

By Steef-Jan Wiggers

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service