I have run into what I think is an issue with our SVN repository configuration 
as it relates, specifically, to the tagging that occurs during a maven release

Our SVN Repository is currently set up as a "multi-project"

SUITE
  + trunk
     + Master POM
     + Product 1
     + Product 2
  + tags
  + branches

Our Master POM has SCM set as follows:

                <scm>
                                <url>https://svn.domain.com/SUITE/</url>
                                
<connection>scm:svn:https://svn.domain.com/SUITE/trunk</connection>
                                
<developerConnection>scm:svn:https://svn.DOMAIN.com/SUITE/trunk</developerConnection>
                </scm>

When I perform a release on any of those products (or the Master POM) I get a 
tag of the entire repository - so if I release everything at once I end up with 
3 tags (master-pom-1.0.0, product-1-1.0.0 and product-2-1.0.0) and each tag has 
tagged the full repository, rather than just the project. Obviously, this can 
confuse things for people since they have (seemingly) 3 tags to choose from if 
they want to branch.

I know that I can reconstruct my SVN repository so that it looks like this:

SUITE
  + Master POM
      + trunk
      + tags
      + branches
   + Product 1
      + trunk
      + tags
      + branches
   + Product 2
      + trunk
      + tags
      + branches

And then set my <scm> tag within each projects POM to point to the correct 
location(s) - this will result in Maven only producing a tag on the specific 
project being released


My question is this - is there a way other than having to dump, filter and 
import my whole repo to get maven to do what I want (i.e. a tag with only the 
Product being released in it)?



Thanks
scott

Reply via email to