How do you work in a team with spring roo?

Question

I'm evaluating Spring-Roo to use in one of my projects but I'm not sure how can it work within a team.

• Everybody in the team can use the roo console?
• How do you commit your changes to svn?
• How do you manage merges and branching?

Thanks!

Answer 1

I think here is what I would do:

1. The "Architect Think Tank" in the team can create the basic bootstrap application once they have very hign level domain model carved out.
2. This can then go into SVN.
3. Followed by this team members can fire roo console either from command prompt or STS and start making changes to their respective modules!
4. This then is managed like any other project i.e. team members who create new entities, fields check their changes into svn.

I don't quite see the need for branches. Merging is required even for normal development with multiple team members so I don't see why would it be difficult with Roo.

Does that make sense?

Answer 2

From Ben Alex in the Spring Roo forum:

In general I wouldn't recommend checking the ITDs into source control given Roo can rebuild them (a bit like your javac compiler builds .class files so you don't check those in).

Git is an exception to this general advice though, because Roo has addon-git which offers a very good automatic integration at a commit tracking level with what Roo's doing (including the ITDs).

One thing to note is that there is no official support for SVN that I've seen, only an addon for git. Another user suggested using Maven's support for Subversion.

Your build/deploy procedures will also be a factor.