Authentication problem with Egit and Github

Git is the best source code control system for me which written using C language . Eclipse provide a way to integrate Git with eclipse and based on JGit , a Java port for Git .
There is a issue when authenticating EGit on eclipse indigo with Github . Egit failed with identifying paraphrase for ssh authentication. A simple solution for this is adding ssh (/usr/bin/ssh) to Environment variables .
export GIT_SSH=/usr/bin/ssh

Few reasons that made me more interested in opensource

  1. When debugging a complex application , nothing can be easier than drilling a source code.
  2. People has different coding styles . But the beauty of coding style depend of experience . One way to tackle this latency is reading those different beautiful codes written by experts and learning the fashion .
  3. Some times third party libraries can not be use as a bunch . Most of the time it need tweak .Having a source code always simplify this task.
  4. Most of open-source software contain high quality code because of people continuously working on bug reporting and fixing .

Quotes I follow

  1. If you passionate about what you do, your work stops being 'just work'.
  2. I have a belief in myself to do anything I chose to .
  3. Believe in your ability. Ignore the noise. March forward.

Arch and automatic build

I addicted to Arch few months back and decided to live as a full time Arch user . It was awesome period and managed to learn most of the crazy stuff that hidden the by beginner friendly layer of destros like Ubuntu .

Arch is a rolling release based distribution and so always managed to run with very much newest packages . This is a really good experience since it allow users to work with new releases very early when comparing with other destros.

But problem arise when it come to automatic building of packages . Most of the building scripts configured to run with stable releases . So most of the time those build failed since Arch always has the future versions of package releases. True its Linux and you can manually fix those problems . But then why we use automatic build scrips ? .

Install maven in arch linux

  1. install maven using package manager
    sudo pacman -S maven
  2. In a command terminal, add the M2_HOME environment variable, 
    e.g. export M2_HOME=/opt/maven/
  3. Add the M2 environment variable, 
    e.g. export M2=$M2_HOME/bin.
  4. Add M2 environment variable to your path,
    e.g. export PATH=$M2:$PATH.
  5. Run mvn --version and  result should be something like following ..

[soori@lapi ~]$ mvn --version
Apache Maven 3.0.3 (rNON-CANONICAL_2011-03-19_21-46_root; 2011-03-20 03:16:53+0530)
Maven home: /opt/maven
Java version: 1.7.0, vendor: Oracle Corporation
Java home: /opt/java/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.0-arch", arch: "amd64", family: "unix"