On 4 Mar 2014, at 9:37, Thomas Ferris Nicolaisen wrote:
Here's the clue. All modules that share release schedule/versioning
CAN be in the same repository. All modules that have distinct
schedules SHOULD be in separate repositories.
I +1 this comment. If your module share a not only a common release
cadence, but common version number then a single git repository works,
but if/when they change one really should look at separate repositories.
The main reasons for this revolve around the maven-release-plugin (
assuming you're using the standard release setup ) in that m-r-p really
likes to release from the root of the repository [1] and because of
git's repository wide tagging setup ( globally tagging all modules with
the version details of individual things gets quite noisy, and
problematic if you need to do back-port fixes on an individual module.
Mark
[1] I believe the forth-coming m-r-p 2.5 release has some bug fixes
around this, but not sure of the details.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
