Setup project for multiple developers

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

Replies to This Discussion

Permalink Reply by Thomas Michaud on April 9, 2010 at 10:27am
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.
Permalink Reply by Jackie Gleason on April 9, 2010 at 11:22am
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.
Permalink Reply by Zemian Deng on April 9, 2010 at 1:35pm
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
Permalink Reply by sony john on April 9, 2010 at 9:43pm
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

NestJS v12 Roadmap: Full ESM Migration, Standard Schema Validation and Modernised Toolchain

NestJS has announced a draft pull request for its upcoming v12.0.0 release, scheduled for early Q3 2026. Key changes include a transition from CommonJS to ESM, native Standard Schema support in route decorators, and shifts in testing and linting tools. Vitest will replace Jest, and oxlint will replace ESLint, while Rspack will replace Webpack for bundling.

By Daniel Curtis

Driving and Measuring the Impact of Platform Engineering

Platform engineering has to be approached from a socio-technical perspective, and shaped by all stakeholders, not just developers, Sergiu Petean said in his talk Driving the Future of Insurance through Platform Engineering. Platform success depends on written principles that endure change while embracing change as the main design force, to enable teams to build, run, and release software.

By Ben Linders

Cloudflare Announces Agent Memory, a Managed Persistent Memory Service for AI Agents

Cloudflare announced Agent Memory in private beta, a managed service that extracts structured memories from AI agent conversations and retrieves them on demand using five-channel parallel retrieval with Reciprocal Rank Fusion. Shared memory profiles let teams of agents access common knowledge. Competitors include Mem0, Zep, LangMem, and Letta.

By Steef-Jan Wiggers

Meta's Approach to Migrating their Systems to Post-Quantum Cryptography

Meta has already begun preparing for the threats posed by quantum computing and migrating its systems to post-quantum cryptography, a complex process that will take multiple years to complete. In a recent article, Meta researchers outline their strategy and share key lessons learned along the way.

By Sergio De Simone

Presentation: Stripe’s Docdb: How Zero-Downtime Data Movement Powers Trillion-Dollar Payment Processing

Jimmy Morzaria discusses the evolution of Stripe’s database tier to support 5 million QPS with 5.5 nines of reliability. He explains the architecture of DocDB and shares how Stripe leverages a custom zero-downtime data movement platform to perform horizontal sharding, version upgrades, and multi-tenant migrations - all while maintaining the strict consistency required for global commerce.

By Jimmy Morzaria

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service