Moving East… Big Pancakes w/ Applesauce
Jul 28

Java.net vs. SF.net

Tech Add comments

Lofi has a post on JavaLobby saying “Java.net underestimates SF.net”. He may have some valid points (SF.net is not just CVS). So my questions are:

a) Why are some projects moving to java.net? (e.g. OpenSymphony code)
b) Why would you choose java.net vs. sf.net?

Are people moving to java.net as sf.net is too bloated? They want their Java projects on a Java site? They think that it will get more exposure there? Or maybe due to boredom, they just feel like moving it somewhere else.

java.net may not be perfect, but it is a start, and it will be interesting to see where Sun goes with the entire endeavour.

3 Responses to “Java.net vs. SF.net”

  1. Jason Carreira Says:

    I can tell you that the reason the Opensymphony code is moving to java.net is because anonymous pserver access to CVS on sf.net has been unavailable 90% of the time for several months. Sf.net may be more than CVS, but without CVS they’re nothing. Plus, Sf.net’s other tools are pretty poor. Their bug tracker, for instance, is just crap.

  2. Dion Almaer Says:

    Ahh interesting. Thanks Jason. When will they use JIRA for bug tracking? ;)

  3. Jason Carreira Says:

    We use Jira, yes.

    http://jira.opensymphony.com.

    java.net is using Issuezilla, which I guess is based on Bugzilla? I don’t know, but it looks crappy.