Hi,
I am trying to get an understanding of how users are using the Maven
toolset with SCM tools such as Perforce to handle branching strategies.
Does anyone know of any such white papers or further reading or be
willing to share current practices?
Do users tend to use a dense hierarchical
branch by artifact when necessary but I have found that the use of ranges and
api artifacts has almost completely removed the need for traditional
branching. By defining the ranges in the deployables you get a consistent
deliverable and can have parallel development and patching without
This is roughly what I seem to be moving towards. Over the past couple
of days I have been converting a hierarchical project into an approach
similar to what you listed to get a feel for things
I have:
trunk/
/area1 - all dev code located under such
/group1
/artifact1
/artifact2
On Thu, 29 May 2008 23:52:35 Bracewell, Robert wrote:
This is roughly what I seem to be moving towards. Over the past couple
of days I have been converting a hierarchical project into an approach
similar to what you listed to get a feel for things
One key thing is that my pom hierachy looks
