Let me ask this question... Why does it seem to be so difficult to get the typical corporate IT developer to look for existing internal solutions, yet those same developers can be huge advocates for many open source solutions?
This is a bit of an apples/ornages question, in that the open source efforts, or even looking up the Servlet API as you suggest, are dealing with items that aren't even considered for "building." There is more likely to be debate on which competing item to leverage rather than building your own. How do we reach the same point in corporate solutions? One may say that the limited people to support a reusable asset is an impediment, but there are probably many open source solutions that gained traction while really only having a handful of developers. I think a key is marketing and communications, and a repository is only a tool in the process. I can have the best TV ad ever, but if it's not shown in front of my target audience, it will fail. Neither simple web pages nor a commercial repository are going to be successful unless people are encouraged to look in the first place. -tb Todd Biske http://www.biske.com/blog/ Sent from my iPhone On Nov 26, 2007, at 10:51 AM, "Mike Glendinning" <[EMAIL PROTECTED]> wrote: > >> >> >> > > For example, I have been managing server-side Java development > projects since 1998 and my developers have never needed a repository > to "discover" any of the J2EE service interfaces such as "servlet" > and so on. They just read the documentation on the web site or in a > book! >
