• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Versioning EJBs

 
Francisco A Guimaraes
Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was planning to start versioning my J2EE projects using CVS, but I came across a huge doubt: what and how do I put in the repository? Do I put the ear file? or Only the source code? I really don�t know what to do. Any feedback and sugestions are deeply appreciated.
Sincerely,
Francisco Areas Guimaraes
 
Dave Coombes
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One option is to use XDoclet tags in your source code which you keep in CVS and then generate the deployment descriptors as part of the build process using Ant.
 
Simon Brown
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you mean source code or runtime versioning?
Simon
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I generally recommend you put both the source and the completely built EAR's in CVS -- you will need both in any case.
Kyle
 
Francisco A Guimaraes
Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks everybody for your quick response. I discovered that if you create separate modules in cvs for each of the WS projects it works just fine, I think I�ll go with that for now, it seems simpler than the alternatives, and maybe put the ear file somewhere. I really appreciated all responses. Dave, do you know where I could find some info about the XDoclets?
[]�s
Francisco Areas Guimaraes
[ December 03, 2002: Message edited by: Francisco A Guimaraes ]
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18226
53
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Personally, I've always liked to put the source and the results under version control, since that way in a pinch I can grab a back-version of a working product even if the development environment is no longer compatible with the source.
Or, as a rule - archive everything you'd leave after doing a "make clean" (or its Ant equivalent!).
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic