Quaker Oats Uttapam - The Indian Pizza

Uttapam is a traditional south Indian dish which closely resembles the pizza. Typically, Uttapam is prepared using urad dal and rice. We twist it's recipe a bit, to create a much healthier and tastier Uttapam using Quaker Oats.

If you want to create the traditional way, the urad dal and rice batter has to be created and stored overnight. However, using Quaker Oats, you can create Uttapam instantly.

Oats as you know is rich in fibre and protein. Thus the Quaker Oats adds much more power and punch to this classic dish.

The ingredients list :

Quaker Oats.
Gram Flour (a.k.a Besan).
Chopped Onions.
Sliced Tomatos.
Cilantro (a.k.a Coriander).
Amul Yellow Butter.
Salt & Pepper.

Mix the Quaker Oats and Besan in sensible proportions with water in a bowl, till it haves a semi-thick batter like consistency.

Heat a pan / skillet and add some Amul yellow butter.

Now spread the batter on the skillet and top it with chopped onions, sliced tomatoes & cilantro.

Sprinkle some salt and black pepper on top. Cook the Uttapam on both sides till the Uttapam gets fully cooked.

Server hot with some Amul butter on top. Wow it tastes absolutely delicious and leaves you extremely filling.

Increase Default Size limit of WAR files in Tomcat 7+

Correct me if am wrong, ever since Tomcat 7.0.x versions and above, the minimum size for a deployable WAR file is set to 50 MB by default. So if you're WAR file exceeds 50 MB limit, you will get the IllegalStateException error.

There is a fix for this problem. This file size limit can be increased to a value higher than 50 MB.

Go to the location : TOMCAT_HOME/webapps/manager/WEB-INF folder. We need to edit the web.xml file here.

Before editing, I suggest you create a backup of the original web.xml ( cp web.xml web.xml.bkp )... Just in case...

Now open the web.xml and search for the attribute "max-file-size". You see the default value is set to 52428800 i.e 50MB. Increase it to let's say 100 MB (104857600 in bytes).

Also increase the value of the attribute "max-request-size" to 100 MB (104857600 in bytes).

Restart tomcat to bring the changes into effect.

Now you can deploy a 100 MB WAR file onto Tomcat without getting any error.

Travel Bytes - Chicago Subway - O'Hare Airport

Chicago O'Hare International Airport was in the news recently, when one of the subway trains crashed, derailed and stepped onto an elevator. The incident injured many people. The live survellaince video capturing the accident can be seen here. In the meantime, I thought I'll just post a few images of how the O'Hare subway station originally looks like.

As you see in the image, this is exactly where the train crashed. Apparently, the train driver dozed off and was actually sleeping when the incident occurred. As you see the blue color indicates that the subway's Blue line is available.

Well, if you're visiting the city, you may have to get down at the LaSalle Street station in 'The Loop" neighborhood, depending on your destination. Check out the CTA Blue line station map below. Also please check google maps and plan accordingly.

Find youngest revision number in Subversion

In Subversion, in order to find the youngest revision number, the command is :

svnlook youngest

It will show the latest (youngest) revision number. In better words, the latest version which contains the most recent changes.

Eg : 

svnlook youngest /Users/IronCladZone/SubRepo1
25

Show hidden .classpath .project files in Eclipse

If you're using Eclipse IDE for any Java based projects, you might want to make .classpath or .project files visible.

In order to do so, click the small triangle on the right top side of Project Explorer and select Customize View.

Just deselect / un-tick the .* resources option and refresh your project.

Now you will be able to see the .classpath & .project files, which are hidden by default. Note that the .classpath file will contain information about the classpath and build info while the .project file will contain the project metadata.

This is useful while working with Maven. When you use the command mvn eclipse:eclipse, it creates .classpath & .project files, which are not visible in the project explorer by default. You can make them visible in Eclipse Project Explorer like this.

Unsupported IClasspathentry kind=4 error in Maven

While importing a Maven project into eclipse, you may sometimes get an error like "Unsupported IClasspathentry kind=4".

The best solution was found on this StackOverflow page. The 2nd solution provided by Sagar worked for me and fixed the issue.

Quick Fix : 

In Eclipse, Right click the project -> Maven -> Disable Maven Nature

Open Terminal, go to the project directory and type mvn eclipse:clean

Now, again right click the project in Eclipse -> Configure -> Convert to Maven Project

Note that when you type mvn eclipse:clean in terminal, it deletes the old .classpath, .project files

[INFO] Deleting file: .project
[INFO] Deleting file: .classpath
[INFO] Deleting file: .wtpmodules

Maven Environment Variables

In order to make Maven work perfectly, we need to define 2 distinct environment variables. They are M2_HOME and M2_REPO. Let's see the basic difference between the two.

M2_HOME is the variable which defines the Maven installation directory.

M2_REPO is the variable which defines the location of your local repository.

Eg : 

So, for instance, if you installed Maven in /usr/local directory, then M2_HOME should be set to /usr/local/apache-maven-3.x.x

If you want to use some local directory (at any location) as your local repository, the M2_REPO should point to it.

Let's say for example, you created a directory /Users/IronCladZone/Maven/Repos which you intend to use as your local repository, M2_REPO should point to this location.

Also, If you use Eclipse IDE to work on, you should define the same in the preferences as well.

Go to Preferences -> Java -> Build Path -> Classpath Variables and create a New entry for M2_REPO, which points to your local repository and a new entry for M2_HOME which points to Maven installation directory.

Go to Preferences -> Maven -> User Settings and check if the Local Repository is set to the desired location.

Also check if the settings.xml location is rightly pointed. Sometimes, the settings.xml is not located in the ~/.m2/repository location. If not, then it must be located at your M2_HOME/conf location. ( Eg : /usr/local/apache-maven-3.x.x/conf ).