Quite a few of my colleagues use Ubuntu as OS for development purposes. For all these years, though I have been working on Linux and UNIX, I haven’t migrated to full-fledged Linux because of many reasons. As working with command line provides a lot of efficiency I use cygwin. However though cygwin works with DOS based “cmd”, I never liked using “cmd” in all these years just because it doesn’t look good compared to putty or similar softwares. With quite a few research I found puttycyg which is a putty extension of cygwin. For this to work, you should already have cygwin installed. After downloading it from http://code.google.com/p/puttycyg/ you need to create a shortcut on your desktop with following target:
$PATH_TO_PUTTYCYGputtycyg-20090811putty.exe -cygterm -
QuickTip : Invalid target release: 1.6 with mvn install
After working for around an year in Flex, I moved back to Java platform again. While building the project I am working on, I saw the following error:
[INFO] ————————————————————————
[ERROR] BUILD FAILURE
[INFO] ————————————————————————
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.6
Usage: javac
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
Logically I changed my PATH environment variable to make JDK bin folder point to JDK version 1.6. Even after making changes, it still didn’t work. It took me a quite a lot of time to figure out that maven uses JAVA_HOME variable for executing the build which was pointing to the obvious, i.e. JDK 1.5. I changed it and it worked like a glove.
Knowledge Sharing Between Distributed Teams
One of the key USPs of pair-programming is – it provides value which is more than simple typing. That includes ACTIVE participation in code-review, knowledge sharing on continual basis, frequent design discussions with minimal distractions etc. If you primarily focus on knowledge sharing, pair-programming essentially provides true form of knowledge sharing as instead of looking at some bulky heartless documents you sit together with a person who has already worked on the subject and can have conversations and design discussions.
[Read more…] about Knowledge Sharing Between Distributed Teams
Augmented Distributed Agile Teams – The Need of Local Retrospective
World is becoming a global village especially in form of communication and the dissemination of information. In context of current economic turmoil and lack of enough trained software professionals locally, distributed Agile is becoming a norm for software project execution.
Earlier, most of the times, entire distributed software project used to be executed completely at offshore because of time-zone differences and communication issues. Now because of communication revolution, you see a new trend where software companies like to extend their teams (augmented Agile teams) with different vendors. Recently while working in such a project from a distributed location, we realized the need of local retrospective.
[Read more…] about Augmented Distributed Agile Teams – The Need of Local Retrospective
Refactoring Flex application from existing Adobe AIR codebase
Adobe AIR is a great technology to provide platform-independent desktop RIA applications. Gone are the days when Windows operating system used to be ubiquitous in desktop market. That’s the reason why Adobe AIR is considered as the future of desktop applications. Desktop applications are here to stay as they come with the power of providing rich features in efficient/optimal way compared to browser mode.
[Read more…] about Refactoring Flex application from existing Adobe AIR codebase