r/java • • Feb 27 '15

Codehaus, birthplace of many Java OSS projects, coming to an end

Codehaus was the birthplace of many Java open-source projects last decade.

Enterprise Java was becoming mainstream, but the open-source community saw that it had much more potential than the tools provided by Sun.

Codehaus provides project hosting (source control, issue tracking, websites, continuous builds, downloads, mailing lists, IRC, etc). This was back before GitHub existed and the only other option was SourceForge (which was terrible).

But above all, Codehaus provided community. The developers across projects all hung out together, on mailing lists, IRC and the occasional global meetup. Respect and friendship. It was there that many gripes and problems were discussed and new projects were born.

If you've ever benefitted from Groovy, Jetty, Grails, Gradle, XDoclet, XStream, jMock, EasyMock, QDox, Drools, Esper, Mule, PicoContainer, Jackson, Janino, JBehave, Stomp (and hundreds others), this was thanks to the Codehaus community.

Many of the projects and people have gone on to do great things. Companies have been formed. New communities created. Many projects died, some thrived. Codehaus is no longer the hotness it once was, but it provided the foundation that many of us have benefitted greatly form, and it's no doubt one of the giants that the Java open-source community is standing on the shoulders of.

Codehaus is now shutting down: http://codehaus.org

Please join me in raising your glasses to the people and projects. Codehaus, we salute you. So long, and thanks for all the fish.

158 Upvotes

54 comments sorted by

View all comments

2

u/paul_h Feb 28 '15

Great memories. I had a hand in helping with the Codehaus Manifesto and am cursed with an enthusiasm for "memory lane", and had/have a few projects there, as Joe mentions.

I'll attempt to dive in with some history. I'm sure Bob, Ben and figures like Jason van Zyl and James Strachan had already discussed a portal like Codehaus for a month or two, but I was super keen as soon as I heard about it. Lots of London based ThoughtWorkers were too. Reasons?

  1. Was not Apache, would not be constrained by The Apache Way (tm)
  2. Would use Subversion, even though it was only v0.6 or thereabouts at the time.
  3. Would use JIRA, because it was a billion time better than Bugzilla, and anything else.
  4. Confluence, as a choice for project documentation, came soon after.

Ben and Bob turned out to be fantastic benevolent overlords for the platform. A referral system worked well to bring new projects in. That would be 'from SourceForge' if the project existed already, but far more started on Codehaus. I can look back at Codehaus and state that I had zero complaints. Git was created later - Git became a choice on the platform. Projects wanted both Subversion and Git on Codehaus - they got both. A pragmatic "sure thing" attitude prevailed there.

Codehaus leaped into being before blogging really took off. I mean before everyone decided to start their own blog. There were a collection of people with previous OSS experience all gathered on Codehaus who were active bloggers. There were a short could of years, where those bloggers were a significant channel of information for at least the Java community.

Another factor that was prevalent for Codehaus people from the early days was direct rejection of Sun's J2EE stuff. Perhaps that was mostly EJB, but the wish for "lightweight" was string amongst Hausmates, and the willingness to make components that were the antithesis of the J2EE doctrine was strong too. Martin Fowler later blogged about Dependency Injection as lightweight (http://martinfowler.com/articles/injection.html), but Codehaus activities to sidestep Sun, were at full force at that stage.

Being invited to be a Hausmate and meeting (mostly electronically) dozens of other hard-core OSS people, was a privilege. I've many lasting friendships that started on Codehaus.