<$BlogRSDUrl$>

Wednesday, March 21, 2007

Recently I came across this article in "information week" magazine.

http://www.informationweek.com/showArticle.jhtml?articleID=198001444

It was written by someone named "charles bobcock".

he writes really funny. For e.g., he goes,

In the 1980s, Stallman was the embodiment of the hippy programmer ethic: anti-capitalist, anti-authoritarian, a binge programmer in MIT's artificial intelligence lab who slept under his desk and couldn't find a real job. Still, he's considered a prophet by some. Stallman's radical software-wants-to-be-free philosophy, which he called "copyleft," led to the GNU toolset, which includes such invaluable IT tools as the GNU C compiler, then to the GPL, and consequently guided the development of the open source software industry.

Wow... It is unbelievable that people get paid for writing crap.

For all we know, stallman was the only person, who took a stand when most people were working on a "real job".
"opensource", "linux" or "apache" wouldn't exist today, if RMS (Stallman) didn't do what he did in 1984.

Stallman wrote emacs, gcc and many others. Linux is directly dependent on gcc. I'm sure gcc will migrate to GPLv3. In that case, torvalds has no option but migrate linux to GPLv3 or keep using older versions of gcc or write his own c compiler.

This author complains about GPLv3. So are the guys who belong to "opensource". These guys are a small fraction of the community that stands behind, FSF and Stallman. No one in our community is paying attention what press writes. we simply ignore them. We just love to code and our code is going to be in GPLv3.

If Linux is not ready to move to GPLv3, no problem. The community will come up with a better kernel in GPLv3. In fact it is only a matter of time, that we will have many options for GNU operating system. Today we have only one kerlnel (linux), who knows how many we have tomorrow.

btw, charles bobcock, if you really want to understand "free software", please attend one of the speeches. Don't expect RMS to give you special treatement. please check http://www.fsf.org/events/all.html.

I hope you understand what you write in future.

Labels:


Tuesday, March 20, 2007

I use "ant" for building java code in my projects.
Recently I have enabled -Xlint for javac ant task,





srcdir="${src.home}/"
destdir="${class.home}"
debug="true"
source="1.4"
target="1.4"
optimize="true"
listfiles="true"
deprecation="true"
includes="common/**,util/**"
>





However, after enabling "-Xlint", the following warning showed up,

[javac] /Users/snambi/opentrade/otp/src/util/SimpleMail.java
[javac] /Users/snambi/opentrade/otp/src/util/StringUtils.java
[javac] warning: [path] bad path element "/Users/snambi/opentrade/otp/software/activemq-3.0/lib/log4j.jar": no such file or directory
[javac] warning: [path] bad path element "/Users/snambi/opentrade/otp/software/activemq-3.0/lib/log4j-core.jar": no such file or directory
[javac] warning: [path] bad path element "/Users/snambi/opentrade/otp/software/mantaray_1.8_bin/ext/log4j.jar": no such file or directory
[javac] warning: [path] bad path element "/Users/snambi/opentrade/otp/software/mantaray_1.8_bin/ext/log4j-core.jar": no such file or directory
[javac] 4 warnings

The code compiled properly and no problems in executing the program.
But this warning was annoying.

So I checked the $CLASSPATH within "Ant". There are no problems. It had "log4j-1.4.8.jar".
Still "ant" complains about the "log4j.jar" not in path.

After some googling and searching for a reason for this warning, I found the following,

$jar -xvf commons-logging-1.0.3.jar META-INF/MANIFEST.MF
inflated: META-INF/MANIFEST.MF
snambis-computer:/Users/snambi/opentrade/otp/software/activemq-3.0/lib>

$cat META-INF/MANIFEST.MF
Manifest-Version: 1.0
Created-By: Apache Ant 1.5.1
Extension-Name: org.apache.commons.logging
Specification-Vendor: Apache Software Foundation
Specification-Version: 1.0
Implementation-Vendor: Apache Software Foundation
Implementation-Version: 1.0.3
Class-Path: log4j.jar log4j-core.jar

The "MANIFEST.MF" file is pointing to "log4j.jar" and "log4j-core.jar".
Hence the warning.


This page is powered by Blogger. Isn't yours?