Matt RaibleMatt Raible is a Web Architecture Consultant specializing in open source frameworks.

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: AngularJS, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

Java.net vs. SourceForge

I think it's about time I moved AppFuse from the Struts project on SourceForge to its own project. That way, I'll have more control over controlling spam on mailing lists, adding developers and other such stuff. So the question is - should I stick with SF or move to java.net? I'm fairly happy with SF, except for their recent CVS hiccup and regular CVS outages. It's cool that java.net gives you a wiki, but I doubt I'll convert all my JSPWiki wiki pages to java.net's wiki syntax (whatever it is). So I guess the question is for you folks that have used both (i.e. OpenSymphony developers): Is java.net better than SF?

Dave asked this same question in June of last year - and Roller still lives on SourceForge. I wonder if that's any indication?

Posted in Java at Feb 24 2004, 09:18:56 AM MST 6 Comments
Comments:

I'd go with SF - the outages are few and far between.

Posted by Greg Bloodworth on February 24, 2004 at 10:24 AM MST #

java.net is INFINITELY superior to sf.net. sf.net status emails are 'sorry for the outages, things will improve in X months'. Java.net has had one single outage so far (scheduled), for a major upgrade that everyone can see the results of. I've yet to have a single problem with java.net in the 7 or 8 projects I'm involved with there. Everything is fast and just works. Mailing lists are nicer to admin and view, file uploads are so much more straightforward and downloading doesn't involve that obscene mirror page. The only downside is the time it takes to get a project approved, but appropriate nagging at jbob the community administrator usually gets this going pretty quickly. sf.net feels hobbyist, java.net feels professional. I wonder if there are people who have had specific bad experience with java.net, rather than those merely opposed to the idea.

Posted by Hani Suleiman on February 24, 2004 at 11:56 AM MST #

My recent experience with java.net was not that nice. They changed their policies for project approvals, and now each project is supposed to be a part of “community". Thus, projects must be approved by community rather than an administrator. It means a sort of advertising for your project on the discussion forum and convincing others that it deserves to be hosted at java.net. If you are personally fine with that then go java.net.

Posted by Pinocio on February 24, 2004 at 12:26 PM MST #

java.net has always had communities and the community leaders have always played a role in the project approval process. We try and let the projects and communities operate as independantly as possible. As a result, some of the communities have instituted quality control into their project approval process. This is not unlike other open source communities where the community votes on project proposals. Each community in java.net has the freedom to operate differently.

Pinocio had issues with the governace of the Java Games Community of java.net. That is a very well run and organized community and Pinocio did not agree with their policies. Luckily, java.net is free so people are free to use it and free not to use it. I advocate the former ;)

Timely project approval was one of our issues that we have recently got in front of. I was more to blame than anything else. We had some serious refinements to make including delegating authority to community leaders to speed up the process. So, Hani is right. Nagging me is welcome. If you are nagging me, I probably deserve it. My goal is to reduce "nagging jbob" to a sport or a hobby and not a requirement for getting things done!

One thing to concider is that, because java.net is focused on Java and is community based, we are more than just a filing cabinet for projects. We do a lot of community building and provide a lot of support for members and project owners. We actually promote and spotlight projects on the java.net home page. We are proud to have O'Reilly and Associates acting as Editor for java.net to make sure the content is interesting and fair. We have a people wiki for members to create personal profiles, including posting their skills and resumes! We have a help wanted wiki for project owners to request specific skills for their projects and more.

Because there is such a community and people aspect to java.net and because we are not just another online CVS file cabinet, requesting a project is a process and not just a form. We are always looking for feedback on what works and doesn't work and particularly like suggestions for improvement. We have a java-net community project that is our community "water cooler" and hosts discussion forums for people to provide feedback and ask questions. I encourage people to check it out.

Posted by jbob on February 28, 2004 at 12:31 PM MST #

I'm curious what provider you switched to, and if things have changed since this post. I'm currently battling daily Subversion outages at java.net with the Mifos project, and we're ready to migrate to another provider.

Posted by Adam Monsen on September 30, 2009 at 11:16 AM MDT #

@Adam - Yes, I've had issues with AppFuse's FishEye instance because of java.net's SVN. For SVN, I'd suggest Google Code. Otherwise, GitHub seems to be all the rage in 2009.

Posted by Matt Raible on September 30, 2009 at 11:56 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed