0 Replies Latest reply on May 1, 2006 1:51 PM by Don Seiler

    Eclipse vs NetBeans from a project/source management perspec

    Don Seiler Newbie

      My shop is taking the big leap forward into the world of J2EE, EJB with JBoss and Hibernate. Up until now, all of our java app development has been done on NetBeans, which was picked due to it's ant-friendliness.

      Since JBoss really seems to put a lot of work into the Eclipse IDE, I thought I'd try it out and go through the http://docs.jboss.com/jbosside/tutorial/build/en/html/index.html. While the tutorials seems to make sense and xdoclets seems to be all the rage with the kids, I could help but notice how much extra set up I had to go through vs NetBeans. Granted NetBeans interface did a lot of the code generation without xdoclet.

      Basically it boils down to the fact that I don't want to have generated code in our CVS, and it seems then that xdoclet is the way to go. We build our releases and RPMs purely in ant, so everything needs to be doable outside of eclipse (obviously other libs like jboss and jre will be there).

      Can anyone give me some perspective on how they manage their project code with Eclipse-based projects?