How to ignore test in maven build using Netbeans

If you want to ignore the test cases execution to run while building a maven project using Netbeans then do the following :

1. Select the project in the project explorer.
2. Right Click it , then select Custom then Goals.
3. In new window check Skip Tests and add install as “Goal”
4. Press OK
5. Done !! now drink coffee.

Renewal of Domain Name

So, I renewed my domain name gauravpaliwal.com for another one year 🙂  🙂

gaurav@gaurav:~$ whois gauravpaliwal.com

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

   Domain Name: GAURAVPALIWAL.COM
   Registrar: DIRECTI INTERNET SOLUTIONS PVT. LTD. D/B/A PUBLICDOMAINREGISTRY.COM
   Whois Server: whois.PublicDomainRegistry.com
   Referral URL: http://www.PublicDomainRegistry.com
   Name Server: NS13.ABHEDYA.NET
   Name Server: NS14.ABHEDYA.NET
   Status: clientTransferProhibited
   Updated Date: 20-may-2011
   Creation Date: 23-may-2010
   Expiration Date: 23-may-2012

>>> Last update of whois database: Sat, 21 May 2011 06:31:58 UTC <<<

My New ISP

After watching a series of serious problem with Sify as my ISP especially with their DNS and worst support for Linux , I migrated to new ISP. It offers a actual download speed of 48kbps (On a connection that is 392kbps) and 60+kbps upload speed *SIMULTANEOUSLY* unlike Sify .Here are few screenshots attached of their user control panel :).

A Great Learning Curve

When I got access to SVN and become a new member of the ever growing OpenMRS community, I realized that I have full Read/Write access to whole of the SVN and asked my mentors following thing :

"

1. I want my write access to be "LIMITED" only to http://svn.openmrs.org/openmrs-modules/feedback/ . How this can be done ?

Then Burke Mamlin (My Co-Mentor) replied me with one of the best statement that I have heard so far :

"We purposefully don't try to manage a social problem (i.e., svn code of conduct) through a technical solution."

And then I realized the actual meaning of the fact that great power come with even greater responsibilities.Although the snip from the Burke's  mail is following :

Just limit your commits to that code.  If you check out that folder it will be very difficult – if not impossible – for you to accidentally write to other parts of the repository.  That said, if a couple months go by and you notice an obvious misspelling or typographical error in the code, you won't have to ask for privileges to change it.

We purposefully don't try to manage a social problem (i.e., svn code of conduct) through a technical solution.  You know what you should be doing & what you shouldn't be doing and we trust you.  If you make a mistake, the repository keep track of each change so it's very easy to fix.  If someone abuses their access to the repository, then that's easy to fix too. 🙂