Open-Source Context



Email    print   
January 15, 2005 —  (Page 1 of 3)
I’m conflicted about open-source software. I just read yet another alarmist SCO-versus-all-that-is-good-with-theworld magazine article that fretted that the SCO-IBM lawsuit meant the end of open-source software. As I read, I found myself thinking that, even though I use a lot of open-source stuff, the end of open source as we know it might not be such a bad thing.

My most recent experiences with Tomcat demonstrate my dilemma. The newest version of Tomcat was just plain broken. It didn’t load and run custom tags correctly, for example. Though I could (in fact did) go to an earlier version, the fact that Tomcat wasn’t subjected to even rudimentary regression testing is disturbing.

The next issue is one of documentation and developer attitude. I wanted to use a local-configuration-file mechanism that’s pushed heavily in the documentation (context.xml), and I was deploying from the development directory using the Ant build.xml file that’s shipped with Tomcat. This process simply doesn’t work.

I started with the documentation to find a solution. Tomcat’s documentation is virtually unusable, though. It’s a hodgepodge of inadequate .html files. There’s no way to print it. There’s no real organizational principle, index or search mechanism. A lot of the documentation is written by developers for other developers, so it is sketchy at best, and incomprehensible to a new user.

I then subscribed, reluctantly, to the Tomcat-user mailing list. I say “reluctantly” because this is a high-volume list with a lot of noise on it. The answer I got from the list was disturbing. I was told that direct deployment from a development directory was added only because users demanded it.

The developers (I’m reading between the lines) didn’t really want to add the feature. They also didn’t want you to deploy from a directory for philosophical reasons. Consequently, they implemented local-directory deployment badly—in a minimal way. A casualty of this process was context.xml. In order to get that feature to work, I would have to deploy in a jar file. However, jar deployment is a real annoyance when you’re doing test-driven development because it adds time to the very short (5-minute) compile-deploy-test cycle.




Pages 1 2 3 


Share this link: http://sdt.bz/28336
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Fall was a bad season for Linux
Actions from Novell and Red Hat have put the community's in a lot of trouble and uncertainty Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb