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

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

How Slack Manages Context in Long-running Multi-agent Systems

To sustain productivity in long-running agent systems, Slack engineers moved away from accumulating chat logs and started using structured memory, validation, and distilled truth to maintain coherence and accuracy of long-running agent systems.

By Sergio De Simone

Google Cloud Introduces Agents CLI to Streamline AI Agent Development Lifecycle

Google Cloud has introduced Agents CLI within its Agent Platform, aiming to streamline the development lifecycle of AI agents from local prototyping to production deployment. The release targets a common challenge in agent development, where tooling and infrastructure are often fragmented across multiple services and environments.

By Robert Krzaczyński

GitHub Uses eBPF to Eliminate Deployment Risks and Prevent Circular Failures

GitHub has introduced a new approach to improving deployment safety by leveraging eBPF, enabling the company to detect and prevent hidden circular dependencies that could block recovery during outages.

By Craig Risi

Presentation: AI-Powered SRE for Autonomous Incident Response

The presenters discuss incident response, how AI-enhanced SRE platforms connect signals from logs, metrics, traces, and historical incidents to enable autonomous decisions.

By Rohit Dhawan, Pavan Madduri, Alina Astapovich, Goutham Rao, Renato Losio

Presentation: Week-Long Outage: Lifelong Lessons

Molly Struve discusses a brutal six-day outage that nearly sank a company. She explains technical lessons like the importance of FMEAs, shadow traffic, and exercising rollback mechanisms. She shares why the human elements - widening your circle early and having a VP who acts as a defender - are what truly build psychological safety.

By Molly Struve

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service