This tutorial is directed towards new users of Linux or people who migrated from Windows to Linux recently. If you are a Windows user, TortoiseSVN . . . → Read More: Subversion and RapidSVN]]> Subversion is a very popular version control system. Though Subversion provides a very robust command line client, most of us prefer using a nice GUI front end. Windows users are really fortunate to have a powerful tool like TortoiseSVN which without any argument is simply the best front end for Subversion. Unfortunately, TortoiseSVN is available for just the Windows platform. Here I would like to highlight about RapidSVN, a cross-platform GUI front end for Subversion.

This tutorial is directed towards new users of Linux or people who migrated from Windows to Linux recently. If you are a Windows user, TortoiseSVN might be the best bet for you. Learn more about TortoiseSVN from the post “Extending Subversion by using TortoiseSVN“.

Pre-requisites
Subversion

Installation
Installing RapidSVN in Ubuntu is a breeze,

sudo apt-get install rapidsvn

Once installation is done, RapidSVN can be found under “Applications -> Programming”. Or if you use a dock like GNOME-Do, you can launch it by typing “rapidsvn”.

For other platforms, download the latest release from the RapidSVN site.

Adding a repository to RapidSVN
Unlike TortoiseSVN which seamlessly integrates into Windows Explorer, RapidSVN allows you to manage the files from a dedicated user interface. RapidSVN will display details like status, author, revision number etc in separate columns.

To add a new repository to RapidSVN, right click “Bookmarks”, click “Add Existing Repository” and enter the repository url.

Checkout a working copy
To checkout a working copy from the repository, right click a repository, click “Checkout New Working Copy” and enter appropriate details.

RapidSVN will display any unversioned files in your working copy, if any.

Adding files to working copy
Right click any unversioned file and then click “Add” to add them in your working copy. Click “Add recursive” if you want to add a folder with multiple sub folders inside it.

RapidSVN will display appropriate status regarding the files that are added in your working copy but not yet committed to the repository.

Commiting changes
You can commit the added files, modified files by right clicking them and selecting “Commit”.

View history (Log)
To view the change history of a file, right click a file and select “Log”.

Reverting local changes
Right click a modified file and click “Revert” to revert the changes you made to your working copy.

Compare the changes made (Diff)
Unlike TortoiseSVN, RapidSVN does not provide built in support for “Diff”. However, you can instruct RapidSVN to use any externl diff tool to fill that gap. So this is what you will see when you attempt to run “Diff” on a file,

Fortunately, there are many excellent “Diff” tools available. I use “Meld” as the diff tool in Ubuntu Linux. “Meld” should be available in all major Linux distros. This is how you will install “Meld” in Ubuntu,

sudo apt-get install meld

Once you have your diff tool of choice installed, you need to tell RapidSVN to use the diff tool. In RapidSVN, click “View -> Preferences” and then open the “Programs” tab. In the “Programs” tab, look for a section called “Diff Tool” and enter the command name there and save the changes.

Now you can diff the changes made to a file by right clicking it and selecting “Diff” or “Diff to Head” or “Diff to Base”.

Once you click “OK”, RapidSVN will invoke the respective Diff tool to display the differences.

Other Settings
If you want to open and edit files right from within RapidSVN, open “Edit -> Preferences” and then enter the appropriate value in the “Standard Editor” section.

If you want to explore your working copy from within RapidSVN, then configure the “Standard Explorer” section in “Preferences”.

Overall, RapidSVN is a solid Subversion client especially to linux users. What Subversion client do you use?

SolitaryGeek Poll

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. - Martin Fowler

Hudson is a popular open-source continuous integration server used by many organizations like Redhat JBoss. Though there are many well known and well established open-source projects like CruiseControl, Continnum and some commercial offerings like Bamboo, what makes Hudson special is it’s powerful yet easy to use web interface, it’s simplicity and it’s extensible architecture with many plugins.

Objective

The objective of this . . . → Read More: Hudson CI Server – A quick start guide]]> Introduction

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day.
- Martin Fowler

Hudson is a popular open-source continuous integration server used by many organizations like Redhat JBoss. Though there are many well known and well established open-source projects like CruiseControl, Continnum and some commercial offerings like Bamboo, what makes Hudson special is it’s powerful yet easy to use web interface, it’s simplicity and it’s extensible architecture with many plugins.

Objective

The objective of this tutorial is to setup, configure and learn to use Hudson by building “Apache Commons IO“, a well known java project.

Requirements

• Hudson
• Subversion (or any other version control system like CVS, Mercurial, Git if you want to build your own project)
  
• (Optional) Tomcat or Glassfish
• Apache Ant (or Maven)
  

Installation and Starting Hudson

Installing Hudson is super easy. Just download the war file, open your terminal/command-prompt and issue the command “java -jar hudson.war”. Now point your browser to http://localhost:8080. That was easy, right?

Hudson has an embedded servlet container called “Winstone” which works much like a standard servlet container like Tomcat by serving your JSP pages and servlets.

If you want Hudson to start on a different port, say 8180, issue the following command,
<code> java -jar hudson.war –httpPort=8180 </code>

Ofcourse you can deploy Hudson to Tomcat, Glassfish or any other supported servlet containers. The following guides can be useful in that case:

• Hudson and Tomcat
• Hudson and Glassfish

More container specific guides can be found from this hudson wiki.

Once you started Hudson or deployed it to a servlet container, this is what you might see in your browser when you start Hudson for the first time.

Hudson Home Directory

All your Hudson jobs/settings are stored in the Hudson home directory. If you did not specify one, Hudson shall assume some defaults like <code> ~/.hudson </code> in Linux or your respective home directory in Windows. It’s ok to go ahead with the defaults while you test drive Hudson but once you are done, I strongly recommend you to define a Hudson home directory of your choice, preferrably on a separate partition or drive. This will ensure that all your Hudson configuration/jobs are intact in case of any system crash.

Say, suppose your home directory is “/hudson” (in Linux), this is how you will define the Hudson home directory,

If you are using the embedded servlet container, start it by specifying the java system property “HUDSON_HOME”,
<code> java -DHUDSON_HOME=/hudson -jar hudson.war </code>

If you are using Tomcat, follow the explanations in this wiki. However, if you run Tomcat as a windows service, you need to do some tweaking to let Tomcat set this property. In that case, you will be better off if you start Tomcat using it’s batch file and set the property right there. (Or if you managed to run Tomcat as a Windows Service and still able to define the Hudson home correctly, why don’t you share your views with us?)

If you are using Glassfish, go to admin console and add the JVM option <code> -DHUDSON_HOME=/hudson</code>. More detailed explanations can be found on this wiki.

Just remember that the idea is to define a system property “HUDSON_HOME” through any of the possible ways.

This is how the Hudson home directory shall look like.

Manage Hudson

Hudson provides an easy to use web interface to manage the configurations needed to administer a continuous integration server. Let us do some basic configurations to get Hudson ready.

Start Hudson and click the “Manage Hudson” link located on the left.

Now click “Configure System”. Hudson will display a page where you can configure things like access control, JDK, Ant, Email Settings etc.

Access Control

We will enable security to secure our Hudson setup. Otherwise anybody can go and meddle with your Hudson jobs. If you don’t want that to happen, check the “Enable Security” checkbox.

Once security is enabled, we need to tell Hudson the type of “Access Control” we want to use. Let us choose the Security Realm as “Hudson’s own user database” and leave the option “Enable users to signup” as checked. (If you do not check the “sign up” option here, Hudson is definitely going to whack you later!. ) Under the “Authorization” section, choose “Matrix-based Security”.

Now add an user called “administrator” and give the necessary privileges. ENSURE THAT YOU GIVE “ADMINISTER” PRIVILEGES TO THIS USER or else, you may not able to access the administrative console once security and access control are enabled. (Again, if you miss it, Hudson is gonna whack you!)

Hudson will display an error symbol near the user we just added. That’s because the user does not exist  in the system. Do not bother, we will create the user a little later. Now go ahead and add users who might be accessing Hudson. Give appropriate access controls to the users and do not give full access to everyone. That will eventually create a system that is difficult to manage.

Configure JDK

Done with security? Now we need to configure the JDK which Hudson shall use to build the jobs. Find out the section “JDK” in the same page. Click the “Add JDK” button and then enter the details of your JDK.

Configure Ant

We need to tell Hudson where Ant is located. Find out the section called “Ant”, click “Add Ant” and enter the respective details.

(Follow the same procedure, if you want to configure Maven.)

That’s it! Hudson is now almost ready for prime time. Feel free to configure the Email Settings as well with the appropriate values. When you are done, press the “Save” button to save all the changes you have made.

Once you press the “Save” button, Hudson will redirect you to a login page.

Manage Users

Click the “Signup” link at the top right corner of Hudson and register a new user called “administrator” (or whatever name you gave in the “Access Control” section).

Hudson will automatically login the user provided the user was already configured in the “Access Control” section. Once a new user (administrator) is registered in the system, Hudson will provide an option called “Manage Users” in the “Manage Hudson” page.

You can now create other users from this page.

You will be using this page to manage all your Hudson users. Looks like we have covered quite a lot of information. It’s time now to create some jobs and see Hudson in action.

Creating Job

That’s the core feature of Hudson. Hudson jobs can fetch the source code from a repository, execute your build scripts, run your tests, prepare javadoc, notify you in case of any failure, archive the build artifacts and much more. That’s where you can really see the power of Hudson. Enough talking, let us explore these Hudson features now by creating a job.

The Hudson job which we are going to create now is going to be very simple and is capable of doing the following:

• Checkout the source code of apache commons-io project using subversion
  
• Run the build script (build.xml in case of Ant, pom.xml for Maven)
• Archive the build output
  

Create a job by clicking the link “New Job” on the left. Give a name for the job, select the option “Build a free-style software project” and then press “OK”.

Configure Job

Hudson will create a new empty job for us which we need to configure.

Let us configure the repository for this job first. Go to the section “Source Code Management”, choose the option “Subversion” and enter the repository url  as “http://svn.apache.org/repos/asf/commons/proper/io/trunk“. Enter the “Local module directory” as  “.”

Look for the section called “Build”. Click the button “Add build step” and select “Invoke Ant”. Leave the rest to default. (Maven users, choose the appropriate action)

Go to the section “Post-build Actions”. Select the checkbox “Archive the artifacts”. The apache commons-io build script shall create the jar in the directory named “target”. So enter the value “target/*.jar” in the text field titled “Files to archive”. Though this is not mandatory to build a job, I recommend you to do this as this will help the users of your continuous integration server to download the build outputs quickly.

NOTE: Since we are building the apache-commons-io project we are entering the value “target/*.jar”. If for example, your build output directory is “dist”, then you should enter here as “dist/*.jar”.

Press the “Save” button at the bottom. Our job is ready and just click link “Build Now” at the left to start building the job.

Once the build is initiated, you can relax and watch the progress in the “Build History”.

If you are restless and want to see exactly what is going on, just click the link (corresponding to the build number) in the “Build History”.

Now click the link “Console Output”.

Hudson will display you the console view where you can do all your research.

Now that the build is successful, you might want to have a look at the jar built by this job. You can find that under “Last Successful Artifacts”.

You can also have a sneak preview about the builds from your Hudson home page.

If in case some of your builds failed, Hudson will report that as well neatly along with displaying the build stability.

That’s it for now. But you can do a lot more like configuring Hudson to build this job every few minutes or just poll the repository once in a while and trigger the build whenever someone commits to the repository. Explore them under the job’s configuration page and enjoy. And did I mention that Hudson has a lot of good plugins already? Maybe I will try to cover those advanced concepts in my next post.

If you are using NetBeans as your IDE, then you have a got a lot of Hudson features integrated right into the NetBeans IDE. Check that out in my post NetBeans 6.7 – A quick glance.

Are you using Hudson? Are you planning to use Hudson? Why not leave a comment below and share your thoughts?

Read also: “NetBeans and Maven – A quick start guide”

My objective was to convert *.DAT files from a VCD into *.mp3. I decided to try WinFF first. The interface was pretty simple to use.

But when I pressed the “Convert” button, I got the following . . . → Read More: Convert video files to mp3 in Ubuntu]]> In my previous post, I explained how to convert audio files from one format to another in Ubuntu. Ubuntu provides native support for this through Sound Converter which can be installed using a simple command. After trying Sound Converter, I was confident that there will be similar applications to convert video files. That made me to install applications like WinFF, Avidemux.

My objective was to convert *.DAT files from a VCD into *.mp3. I decided to try WinFF first. The interface was pretty simple to use.

But when I pressed the “Convert” button, I got the following message,

WinFF reported that the encoder ‘libmp3lame’ is unknown. I tried to install that via apt-get but could not find that in the repository as well. I tried to convert to other formats but in vain. I understand that I miss some libraries/encoders, but the help message was not very useful. The application could have suggested me to install the respective library like Sound Converter does for “mp3″ support.

Since WinFF failed to get the job done for me, I tried Avidemux this time. When I started avidemux, I quickly realised that this not going to be an application which everyone can use effortlessly. Avidemux might be a great tool but unless it gets a decent user interface it’s not going to be used by many. But since I was determined to convert my video files, I proceeded ahead with Avidemux.

When I tried to load the “DAT” file, Avidemux complained that it could not open that file.

I searched the Avidemux wiki but still couldn’t solve the problem. My search continued and in one forum I got a suggestion that I can rename the file to “mpg” and change the “video”, “audio” options to “MPEG-4 ASP (Xvid4)”, “MP3 Lame” respectively. But the result was same. Avidemux couldn’t open the file.

Then I realised that another user had the same frustrations like me and eventually opted to run the popular windows only tool FormatFactory on top of Wine. I decided to follow suit but I thought of trying out AnyVideoConverter on top of Wine. But AnyVideoConverter failed to start which left me with no options but to turn for FormatFactory.

I downloaded and installed FormatFactory using Wine and it started without any issues on my Ubuntu.

Since I wanted to convert video files into “MP3″ format, I clicked the “Audio” tab in the left pane and chose the option “All to MP3″. Then I was prompted to add the necessary files.

Once I added the necessary files, all I had to do was to click “Start” button.

After a few seconds, FormatFactory successfully converted the “DAT” files into “MP3″ format.

Thanks to FormatFactory and Wine, I was able to convert “DAT” files without booting into Windows. Many thanks to this wonderful article which was an eye opener for me.

I haven’t yet tried the FormatFactory|Wine combination to convert my videos into other format. Why don’t you try it and share your experience with us?

Traditionally I use softwares like Any Video Converter, Format Factory to convert audio/video files but unfortunately they are available only on Windows and I had to boot into my old Windows XP in order to use them. I thought I . . . → Read More: Convert audio files in Ubuntu with Sound Converter]]> “Linux lacks good multimedia applications“. How many times have we heard this! This was my perception as well. Not that I do my living based on these tools but I do use them often at home. Atleast, many of us might be in a need to convert audio/video from one format to another and rip tracks out of audio cds.

Traditionally I use softwares like Any Video Converter, Format Factory to convert audio/video files but unfortunately they are available only on Windows and I had to boot into my old Windows XP in order to use them. I thought I had no other choice and also since those tools did the job for me, I was eventually using them whenever the need arises. Fortunately there are some good tools in linux as well.

My search for a good audio/video converter continued and even thought of using those popular windows tools on Ubuntu using Wine after reading the article, Best Linux Ubuntu Video/Audio Converter: Format Factory and WINE.

I was almost sold if not for this comprehensive guide from ubuntu forums. At the first look, the article might look a bit overwhelming, but it contains a wealth of information covering many aspects. I was primarily interested in just a audio converter and I all I had to do was execute this simple command


sudo apt-get install soundconverter audacity oggconvert

All these three are audio converting tools where audacity provides audio editing capabilities as well. You might also need sound-juicer to extract audio files from cd. Installing that is pretty straightforward:

sudo apt-get install sound-juicer

Converting files are only two steps away. Click “Add File” button to add the files you would like to convert. Once you have added the necessary files, click “Convert”.

By default, Sound Converter converts audio files to the opensource “ogg” format. If you want the default output to be “mp3″, you need to first install some additional libraries. Then you need to edit the preferences and change the output format “mp3″ (under the section “Type of result”).

I am using Sound Converter quite regularly now and I am quite impressed with it. How about you? What tools do you use to convert audio files? It will be great if you can share your experiences as well.

Objective: - To learn how to configure Apache http server to provide remote access to subversion repositories. - To learn how to configure authorization and access control to subversion repositories through Apache http . . . → Read More: Extending Subversion with Apache]]> In one of my previous post, I explained about using TortoiseSVN with subversion. Continuing in the same vein, we will see how to extend subversion with the Apache web server. Apache, the most popular http server in the world provides powerful extension point to your subversion repositories and a strong understanding of how these two technologies work together is very important for those who are into it.

Objective:

- To learn how to configure Apache http server to provide remote access to subversion repositories.
- To learn how to configure authorization and access control to subversion repositories through Apache http server.

Pre-requisites:

- Subversion 1.4.6 for Apache 2.2
- TortoiseSVN

Step 1: Download Apache 2.2:

Download the latest Apache 2.2 installer from here.

Step 2: Install Apache 2.2:

Installing the Apache http server is very straightforward. Just follow the instructions in the installer gui.
Let’s call the Apache installation directory as APACHE_HOME. (Normally this shall be C:\Program Files\Apache Software Foundation\Apache2.2 in windows)

Step 3: Copy Subversion modules/dll for Apache:

Subversion comes with two modules that Apache can use to access the repositories.

1. mod_dav_svn.so – The subversion module to provide filesystem access
2. mod_authz_svn.so – The subversion module to provide fine grained access control

These two modules can be found in the SUBVERSION_HOME\bin directory. Copy these files to APACHE_HOME\modules directory.

It’s not over yet. There are two more files you need to copy to ensure that the Apache-Subversion setup works correctly.

1. libdb44.dll
2. intl3_svn.dll

Where are they located? Well, in the same SUBVERSION_HOME\bin directory. Copy these files to APACHE_HOME\bin directory.

Congrats! You have successfully setup your Apache http server. We will now look how to configure Apache to access your subversion repositories.

Step 4 (Optional): Create a Subversion Repository

You want me to explain this again…?

Step 5: Configure http.conf to load Subversion modules for Apache

The http.conf file is the configuration file used by Apache. It can be found in APACHE_HOME\conf directory. We need to configure this file to instruct Apache to load the subversion modules we copied in Step 3. (Remember..?)

Look for the “Dynamic Shared Object (DSO) Support” section in your http.conf. You can see many “LoadModule” statements in this section. Now, uncomment the following line:

Add the following lines after adding the above mentioned line:

Step 6: Configure Subversion repositories in http.conf

Assume that you have a repository at the location “E:\Subversion\Repositories\test-repository”. You want to access this repository using the url “http://localhost/svn/test-repository”. Let us instruct Apache on how to handle this scenario.

Go to the end of your http.conf file and add the following lines:
(Please replace the SVNPath mentioned here with that of yours. Note that we are using file separator “/” and not “\”)

After adding this, restart your Apache service for the changes to take effect.

This is a bare minimum configuration which should enable Apache to access to your subversion repository. Want to check this? Point your browser to the url “http://localhost/svn/test-repository” and Apache http server will be happily displaying all the files under your repository.

Step 7: Authentication

Now your subversion repository can be remotely accessed through Apache http server. And anyone in your network can do a subversion checkout by typing the following command in command prompt.

(Or if you have tortoisesvn, you can right click inside any directory and do a “SVN Checkout”)

And people can even change the source code and “commit” the changes back to your repository. But you don’t want that to happen. You want only authenticated users to access your repository. With Apache, this can be a piece of cake for you. Apache comes with a inbuilt “htpasswd” command line utility to help you create users and passwords in a secured way. To put that into action, just follow these steps:

- Open command prompt and navigate to APACHE_HOME\bin directory.
- Type the command,

Here you are instructing the “htpasswd” utility to create a new user named “james” in a password file called “users.htpasswd” in the directory “APACHE_HOME\conf”. When you enter this command, you will be prompted to enter a password for this user and to confirm it as well. Apache will use MD5 encryption standard (by default) to encrypt the password and store that in the “users.htpasswd” file mentioned by you.

The following screenshot explains this process.

To add more users you can use the following command:

This tells the htpasswd utility to add a user named “gift” in the same “users.htpasswd” file.

You have to instruct Apache to refer to this file for authentication. Open your http.conf file and modify the block you created in Step 6. Your block should now look like this:

In the above block you are instructing Apache to use “Basic” authentication type and allow only “valid users” mentioned in the file “conf/users.htpasswd”.
(NOTE: You are mentioning the relative path of the “users.htpasswd” file from your document root. Your default document root is APACHE_HOME.)

Want to see your settings in action? Save your http.conf file, restart your Apache service and point your browser to the url “http://localhost/svn/test-repository”. You will not be able to access your repository as you did before, you must be authenticated to proceed further. You might see some popup window like this:

If you entered your credentials correctly, you can access the subversion repository through your browser. If your credentials were wrong, your browser will display a page like this:

Step 8: Access Control

Great! You have configured your Apache http server in such a way that only “authorized users” (specified by you in the file “users.htpasswd”) can access your subversion repository. Here comes another need which requires you to specify “specific users” to access “specific parts” of your repository. For example, you want to give your users “read-write” access to the “trunk” folder but only “read” access to “tags” folder. How to achieve this..?

First, create a file called test-repository-authz.conf in the directory APACHE_HOME\conf. We will now define the access controls for your users. It can look something like this:

This says that give “read” access to the users “james” and “gift” for all parts of the repository except for the “trunk” folder where they both will have “read-write” access.

But how will Apache refer to this file…? We need to modify our “Location” block again this time, something like this:

That’s it! Now you have fine grained control over who access which portion of your repository.

Step 9 (Optional): Even more Access Control

Having successfully setup the Apache http server to access your subversion repositories, you are planning to enjoy your coffee break with your colleagues. Suddenly your boss calls you and says “Hei, I want even tight access control mechanism based on IP Address. I don’t want anyone to access our subversion repositories from any other machines other than the one we give access. I hope you can do it.” You think “Can Apache handle this scenario..?”. Why not..? This is how you do that with few more additional lines…

(Note: Please mention the actual IP address instead of “x.x.x.x” and “y.y.y.y”)

We will explore what these statements mean here.

The above statement instructs Apache to process “Deny” statements before “Allow” statements.

The above statement instructs Apache to deny access to all machines by default.

The above statement instructs Apache to allow access from the machines with the IP Address “x.x.x.x” and “y.y.y.y”.

Apache is such a versatile server that it provides many other options but that is outside the scope of this blog entry. Hopefully I will try to cover some of them in another post. Thank you very much for reading this post patiently. I hope this is useful to some of you.

Subversion is arguably the most popular version control system as of now. No wonder NetBeans has very good support for Subversion. I personally feel that a java developer must be familiar with both these tools. This article shall help you to get started with both these tools.

Objectives:

- To create a simple java project in NetBeans.

- To import the java project into the subversion repository.

- To commit the changes made in a java source file.

- To view the revision history of a java source file which was changed.

- To rollback to the previous . . . → Read More: Subversion and NetBeans – A quick start guide]]> Introduction:

Subversion is arguably the most popular version control system as of now. No wonder NetBeans has very good support for Subversion. I personally feel that a java developer must be familiar with both these tools. This article shall help you to get started with both these tools.

Objectives:

- To create a simple java project in NetBeans.

- To import the java project into the subversion repository.

- To commit the changes made in a java source file.

- To view the revision history of a java source file which was changed.

- To rollback to the previous revision of the java source file.

Requirements:

- NetBeans 6.1 Beta or NetBeans 6.0

- Subversion

- TortoiseSVN

- Though not mandatory, but a basic knowledge of subversion concepts.

Note: You can read this article to learn how to install/configure Subversion and TortoiseSVN.

Step 1:

Create a new “Java Application” project called “SimpleLogin”.

Step 2:

Create a new JFrame called “LoginFrame” under the package “org.example.simplelogin” and add the necessary components as shown below.

Step 3:

Name the swing components accordingly.

Your application should like this now on preview:

Step 4:

Create a java class named “LoginService” under the package “org.example.simplelogin”.

Step 5:

Add the following code to the LoginService class.

Here we are defining a simple method which shall return true if the username is “guest” and the password is “password”.

Step 6:

Now open “LoginFrame.java” and add the following methods.

The above methods are self explanatory. We are just doing a simple validation and calling the login method we defined previously in the class LoginService.

Step 7:

Now double click the login “button” in the design mode of LoginFrame.java to create the event handling method named “loginButtonActionPerformed”. Add the following code to call the “performLogin” method.

That’s it.

Step 8:

Run the project.

If you enter the username as “guest” and password as “password”, you will get an output like this.

Otherwise, you will be getting an output like this.

Ok, our simple login application is ready for prime time . Now let us import this project into a subversion repository.

Step 9:

Create an empty folder called “MyRepository” in a preferred location.

Step 10:

Create a subversion repository in the empty “MyRepository” folder as mentioned below, by right clicking anywhere inside the windows explorer.

Accept the default option (FSFS) in the “Create Repository” window.

That’s it. Your repository should be ready when you press “OK” and it should look something like this.

Step 11:

Let us import the NetBeans project we have created into the subversion repository. Right click the NetBeans project we have created and then click “Versioning -> Import into Subversion Repository”.

NetBeans will prompt you with a window. Enter the path of your repository as shown below.

Click the “Next” button and enter the “Repository Folder” name into which you would like to import your project. To make things simple, let us enter our NetBeans project name itself as the “Repository Folder” name. Also enter a small description about this import activity as shown below.

We are almost there. Click the “Next” button and the IDE will show a window like this.

Accept the default entries and click “Finish”. Congratulations! you have imported your project successfully into the subversion repository.

Right click anywhere in your desktop/windows explorer and click “TortoiseSVN -> Repo-Browser” and then enter the path of your subversion repository. You can see all your project files sitting comfortably inside the subversion repository.

Step 12:

Let us play around with some more cool subversion integration features offered by NetBeans. Open the class “LoginService.java” and change the value of “DUMMY_PASSWORD” from “password” to “guest”.

You can see the IDE markup a blue shade near the line you made the change. This indicates that your source file has got something different than the version in the repository. You can also note that the IDE change your java source file name’s font-color to blue.

Let us turn our focus to the editor window again. Click the blue stripe shown by the IDE near the  place where you made changes to the source file. The IDE will popup a small hint-window.

You can see the previous value of the DUMMY_PASSWORD there. The IDE also provides you a set of buttons to revert back the changes or to have a “diff” view on the changes made. Let us explore the “diff’ functionality of the IDE first by clicking the “diff” button.

The IDE will display the “diff” view of the “working copy” and the “HEAD” revision (the latest committed version) in the repository.

From the above figure, you can see the current and previous value of the string DUMMY_PASSWORD. Now you can revert back to the old value of “DUMMY_PASSWORD” by clicking the replace  button (displayed like an arrow)

When you press the “replace” button, the IDE will replace the “current” value with the “original” value.

The “diff” view provided by the IDE will be very useful to examine and compare the changes made to the “working copy”  alongwith the option to revert back to the original version in the repository. But if all you need is to quickly revert back some change to the original version in the repository, you can click on the blue strip in the source code and click the “revert” button.

That’s cool, right?

Step 13:

Enough playing. Now let us commit the changes we made in our source file. Ensure that the source file you are willing to commit is in focus and click the menu “Versioning -> Commit”

When you click the “Commit” menu item, the IDE will prompt you with a window to enter the “message” for this commit operation. Enter a commit message and click the “Commit” button.

Step 14:

Let us explore the history of our source file and see the the changes we made all along. Click the “Versioning -> Search History” menu.

The IDE will display all the versions of the source file.

In the “Search History” window, the IDE offers two views, “summary” view and “diff” view. By default, the IDE displays the “summary” view. The “diff” view contains more information.

You can straightaway “revert” or “rollback” to previous revisions just by right clicking a particular revision.

Nice, isn’t it? There are still a lot more cool subversion features offered by NetBeans. I will blog more about that later. I hope the information provided here was useful to you.

Read also: “NetBeans and Maven – A quick start guide”

SolitaryGeek Poll

TortoiseSVN and Apache comes to your aid. TortoiseSVN is a powerful tool for Subversion, which helps you to issue most of the subversion commands from your windows explorer. Subversion has an inbuilt “svnserve” utility which helps you to expose your repository to remote users, but it’s highly recommended to use the flexible Apache Web Server for this purpose. Subversion comes . . . → Read More: Extending Subversion by using TortoiseSVN]]> Though Subversion is a powerful version control system, it’s command-line based interface may not appeal to some users who used other version control systems like Visual Source Safe. And what if you want to remotely access your repository as well?

TortoiseSVN and Apache comes to your aid. TortoiseSVN is a powerful tool for Subversion, which helps you to issue most of the subversion commands from your windows explorer. Subversion has an inbuilt “svnserve” utility which helps you to expose your repository to remote users, but it’s highly recommended to use the flexible Apache Web Server for this purpose. Subversion comes with it’s own apache modules to expose your repository to remote users. However, in this article we will not focus on Apache. I’m planning to write about the apache integration in my next post. Please be patient

Objective:

In this article you will learn how to install Subversion and TortoiseSVN and use them to create a repository, import files into the repository and view the repository.

Step 1: Install Subversion

Download subversion windows installer for Apache 2.2.x. (Download the file called “svn-x.y.z-setup.exe” and run the installer. Installing should be a straight forward option.

You might see the following windows. They are self explanatory.

Now you should have subversion successfully installed in your machine. To verify that, open the command prompt and type “svn –version”. If you see something like below, pat your head, you have successfully installed subversion.

If you couldn’t see the above mentioned message, you might want to check your “Path” environment variable and add your subversion installation directory to the “Path”.

Step 2: Install TortoisSVN

Download TortoiseSVN from here.

That’s it. Now the installer setup might prompt you to restart your system to complete the installation process. Accept it.

Step 3: Create a Subversion Repository

Now, it’s time to create a subversion repository. Though it’s possible to use the subversion’s “svnadmin” command to create the repository, we will use TortoiseSVN to achieve that.

3a) First, choose a appropriate location to keep all your repositories. In my case it’s “F:\Subversion”. Let us call this folder as REPOSITORY_ROOT. Now, let us create an empty directory called “MyRepository” inside REPOSITORY_ROOT. It should look something like this:

3b) Now, right click inside the folder REPOSITORY_ROOT\MyRepository, and click “TortoiseSVN -> Create repository here” menu.

3c) TortoisSVN will now prompt you with a message box like this:

Leave the default option (Native file system), and click “OK”. You can see a bunch of files inside the “MyRepository” folder like this:

Great!! This is your subversion repository.

Step 4: Import files into your subversion repository

4a) Let us add some files inside our newly created subversion repository. Right click a folder of your choice and click “TortoiseSVN -> Import”

4b) Enter the appropriate repository path where you would like to import these files into. In my case it’s “file:///f:/subversion/myrepository/photos”.

4C) When you press “OK”, TortoiseSVN will import all the files/folders inside the folder which you selected for the import operation into the subversion repository.

4D) Press “OK”. Now we have finished importing the files into our new subversion repostiory. It’s now time to view the content of our repository.

Step 5: Viewing the content of your subversion repository

5a) TortoiseSVN provides a nice “Repository Browser” option to view the content of your subversion repository. Right anywhere in your explorer window/desktop and click “TortoiseSVN -> Repo-browser”.

5B) Enter the url of your subversion repository. In my case, it’s “file:///f:/subversion/myrepository” and click “OK”.

5C) That’s it, now TortoiseSVN will list down all the files inside your repository.

Summary:

In this article, you learned to:

- install Subversion

- install TortoiseSVN

- create a new repository using TortoiseSVN

- import files into the subversion repository using TortoiseSVN

- view the content of the subversion repository using TortoiseSVN

What next?

I initially thought of even writing about installing, configuring apache/websvn in this article itself. But it already took me nearly 3 hours to finish writing this. So please bear with me. I’ll come with a Part II of this article where you will learn how to use apache/websvn along with subversion to make the interaction with your version control system a pleasure. See you again.

Added on August 2, 2008:

I have written an article named “Extending Subversion with Apache“. This article is about setting up Apache http server and configuring it to access subversion repositories. It also deals how to setup Authentication and Access control for your subversion repositories using Apache. Hope you find it useful.

SolitaryGeek Poll