Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am not an experienced Java developer and I am currently modifying and re-building a plugin project. I am about to adopt a versioning control system (e.g. Subclipse), however I already have several versions of such project. My intention is that to check how these versions differs from each other and I was wondering what is the best approach into this. I work with Eclipse IDE.
Thank indeed,
I.
Subclipse just connects Eclipse with a Subversion repository. You have to have a Subversion repository somewhere for Subclipse to work.
Assuming you have a Subversion repository, you commit the oldest version first. You create a Eclipse workspace on you computer that you’ll use to communicate with Subversion. First, you copy the oldest version of your project into the Eclipse workspace. Then you commit the workspace. You update your workspace by copying each saved version to your Eclipse workspace in turn, and commit.
That way, the source control will be able to show you the differences between each saved version.