Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Yes, I'd say it's useful to have a version control, even if you are the only user. Some of the advantages would be:</p> <ul> <li>You can revert your changes fast, no wondering what you changed since last update/commit</li> <li>You can branch your project for testing out ideas, and merge the branches, or revert back to the base</li> <li>In case a new programmer joins the project, he can just check out the project from the version control system and start getting into it, no copying files over network or via usb-stick or something</li> <li>You have a history of your project (what was done when)</li> <li>Your projects are stored in a single place, where you can easily see them all and/or implement automatic backups</li> <li>Sharing and working on a project in multiple computers becomes easier</li> <li>You get experience using version control, which you'll probably need later on when working as a team on some project</li> </ul> <p>If you are working on your home computer and no-one else works on the project(s) in the version control system, I'd say set it up on your own computer. Companies usually have (or at least should have) their own internal version control systems in their intranets.</p> <p>As for what version control system is the "best", I can't really say. I've only used CVS and SVN, from these two I'd say definitely go with SVN. I've also heard good things about Mercurial and GIT, but haven't ever used either.</p> <p>As for other tools, I'm not sure if you need any (since you're already using Maven). We have Hudson at work, but I don't know how to setup one (it was done by somebody else), although the Hudson website says it's really easy. Hudson monitors the version control system (in our case, svn) and automatically builds the project when it notices new changes committed into the svn. It runs the maven-target and reports any test-failures to committer via email. I think it can also be scheduled to do builds at certain times and deploy the project to specified place, but not sure on this. For a single developer project, I'd say setting up Hudson is probably overkill.</p> <p>Edit: As an afterthought, if you choose to go with SVN, get Subclipse (since you're using Eclipse), it's an SVN-plugin that makes it easy to handle checkouts/commits/updates/reverts and viewing history, changes etc. straight out from the Eclipse-IDE.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload