Most users, I would presume, use the archetypes published in the maven repos
(?), which would mean most of us are pretty much agnostic regarding which
VCS is used, so this decision should mainly concern those actively
developing Jersey. Personally, I like the decentralized variant (git, hg,
darcs) better than SVN, but since I don't plan on being an active Jersey
developer, my vote should weigh pretty light. Listen to the frequent
contributers to the project, rather than average users, when deciding which
route to take. As Rob says, barrier to entry should also be a factor,
obviously. git/hg has an edge in this case, I'd say.
2011/4/13 Rob - <skyscrapper666_at_hotmail.com>
> *Maybe it's just me, but to me the barrier to entry is much smaller if
> all I have to do is clone a github repository, tweak code to solve my
> problem, push, and then send a pull request. Using SVN, I can't really
> contribute without becoming a committer or jumping through hoops. With SVN,
> the workflow would be to checkout anonymously, tweak code to solve my
> problem, create a patch file, locate the issue tracker, create an account on
> the issue tracker, post a bug report, and then attach the patch file.*
>
> You would still do the same with GIT, HUT, etc. It's the way the workflow
> works.
>