- This topic has 3 replies, 2 voices, and was last updated 18 years, 10 months ago by
Riyad Kalla.
-
AuthorPosts
-
nbhatiaMemberGiven the directory structure that MyEclipse expects for a standard J2EE application (with 3 projects – application, EJB and web app), can someone tell me what should be checked into the source repository? Note that I would prefer a process where dependent libraries are not checked into the repository. These should be pulled in from a central place on the local hard drive after checking out a fresh project from the repository.
Thanks for your help.
NareshSeptember 18, 2006 at 10:24 am #258685
Riyad KallaMemberNaresh,
I don’t quite understand the question, you should check into the repository anything you want versioned… did you mean something more specific? THis is a very developer-centric question, like asking “What movie should I go see this weekend” so I’m not terribly clear on how to answer you.September 18, 2006 at 11:14 am #258702
nbhatiaMemberAh, the intent of the question was to seperate out what is real source vs. what is generated. Most of the time this is very clear but for some things like like .mymetadata, I see ocassionaly MyElipse will occasionally change dates on it even if there is no content change. So the question was more geared towards a team environment, what should be checked in, vs what individual team members should keep their own copy of (and put cvsignore on such files).
September 18, 2006 at 11:20 am #258703
Riyad KallaMemberI see… well this is really a team-focused question as well. For example I tend to work on a lot of mixed-IDE teams, so we never check IDE project files into the repository, the down side is that everyone has to setup the project on each machine, but that’s not so bad (normally project files contain absolute paths anyway, which will typically break on other machines, so requiring that each dev re-set the project isn’t the worst for small teams, but for huge teams can be a pain).
So if you don’t check any of the dot files into source control, each person will need to setup the projects, if that’s an issue, then check them in. If it’s not, then I’d say leave them out. That way when the IntelliJ or JBuilder guy on the team wants to check in his project files, you can tell him “no” 🙂
-
AuthorPosts