aspose file tools*
The moose likes IDEs, Version Control and other tools and the fly likes CVS Implementation Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "CVS Implementation" Watch "CVS Implementation" New topic
Author

CVS Implementation

Nuwan Priyadarshana
Greenhorn

Joined: Aug 27, 2005
Posts: 26
I want to implement CVS for our Java (web) development, so I am using NetBeans as a development tool. My question is should I put entire NetBeans project to CVS repository and check out entire project or add only required file to CVS repository and check out required file to separate NetBeans project ?

Regards,


Nuwan<br />SCJP 1.5(83), SCWCD 1.4(86) <br/>
www.saralasolutions.com
Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24168
    
  30

It's possible to do things either way. If your developers have a standard corporate desktop, so that paths and IDE settings are likely to be just the same for everyone, then you can check the IDE project files into CVS along with the project. On the other hand, many teams have developers with some variation in their environments, so identical project files would not work for all team members. In this situation, you should not check the project files in; just check in the source code, Ant files, etc, and not the IDE project file(s).


[Jess in Action][AskingGoodQuestions]
Nuwan Priyadarshana
Greenhorn

Joined: Aug 27, 2005
Posts: 26
Thank you Ernest for the information.
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
I might add that, if there's a clear majority of developers using the exact same workspace settings, then it might make sense to add the project files used by that majority under version control. The others would then have to override the "default" with their own, but at least the majority wouldn't need to configure anything after checking out the project from CVS.

Having said that, I suppose it just might happen that every now and then someone mistakenly checks in their non-standard project files...


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: CVS Implementation
 
Similar Threads
Importing a Java Project from CVS into Eclipse
Unable to Checkout file in CVS-Linux
Eclipse: ssh plugin ?
Subversive Eclipse Plugin: how to add version-tracking to existing project?
invalid CEN Header (bad signature)