An open-source revision control system, which aims to be a compelling replacement for CVS.
Subversion is a centralized system for sharing information. It comprises of a repository, which is a central store of data. The repository stores information in the form of a file system. Clients can connect to this repository, and can read or write to these files. When a client writes data, it actually makes the information available to others; and when a client reads the data, it actually receives information from others. Its a typical client server system which uses version model.
Consider that you are working on a large/medium size Java project in teams. This is an ideal scenario for using Subversion to distribute and maintain source code. Good news is that you can use integrate your source code with Subversion within Eclipse environment.
An Eclipse plugin called Subclipse is to be used for integrating source code with Subversion within Eclipse environment. You may download Subclipse from: http://subclipse.tigris.org/download.html
In the following article, we are going to compare the various features between the two frameworks. Struts 2 is very simple as compared to struts 1, few of its important features are:
1. Servlet Dependency
Actions in Struts1 have dependencies on the servlet API since the HttpServletRequest and HttpServletResponse objects are passed to the execute method when an Action is invoked while in case of Struts 2, Actions are not container dependent because they are made of simple
Subclipse is a very popular Eclipse plugin which provides SVN repository supports within Eclipse. It serves the purpose but there is no real way to change the SVN user for a repository if credentials are saved. I will try to address this problem in this post.
First of all, why you would need to change the svn user credentials? Person A is working on your machine and he checks out a project from a SVN repository using his credentials. He saves his SVN credentials in your Eclipse environment.
SVN (SubVersion) is being used in software development houses to maintain the source code. Its very effective if used properly. In this post, I will present some basic concepts about SVN.
Usually, SVN has following directory structure:
You may add more directories like archive and some other of you want. I will explain the use of above directories so you know when to use what.
The trunk directory contains
I would like to highlight a problem which many developer face while check outing a project from SVN.
Consider that you are check outing a project from SVN comprising of many folders. During checkout process, you run out of disk space or you computer breaks down of any reason. What you think of checked out project? There will be few files/folders left to be checked out. Also it is possible that fvew files are corrupted. The solution is to fist make sure you have enough free space on
You must have used SVN while working in a team on a Java project. In this post, Ill write about 'revert' command.
Let me present a scenario. You made some changes in a class and now you realize that the changes are not required/not correct. You wish to discard your changes. You have to use svn revert to discard your changes. Java Code: $ svn revert foo.java
Following switches are available: Java Code: --targets
$ svn revert foo.java
Subclipse is a popular SVN plugin for Eclipse. This post is about how to do checkout using Subclipse.
You will check out code from the trunk or branch of a project. First configure your repositories. Open the SVN Repository Perspective and then open the contents of the repository where your project is located. Locate the trunk/ or branch/ directory in the project and right-click the trunk/ directory or branch/ directory, and choose Checkout from the context-menu. You will be see a
Committing means persisting your changes. You may commit one file or multiple files at once.
Subclipse makes committing easy and simple. When a file is modified, Subclipse displays an icon next to the file name (asterisk) which indicates that your local copy is different from what was in the repository
when the file was checked out. This helps you know what to commit. Remember, if you create a new file, it will have a different icon(a small question-mark). The "changed"