On Sep 22, 2010, at 10:30 AM, [email protected] wrote:
> Hi,
>
> is it possible to manipulate the SCM modification of the maven-release-plugin
> ?
>
> Our project is found under the following URL:
>
> https://svn-server/repository/svn/foobar/trunk/ourProject
>
> ourProject is a multimodule project with several children.
>
> when I ran the maven release plugin it creates as scm entry the URL
>
>
>
> https://svn-server/repository/svn/foobar/tags/release-0.1
>
> so we loose the ourProject information.
>
It sounds like your SVN layout might be a little bit off. The convention is
that for each project you have trunk, branches & tags:
<svn_root>/project_1/trunk
<svn_root>/project_1/branches
<svn_root>/project_1/tags
<svn_root>/project_2/trunk
<svn_root>/project_2/branches
<svn_root>/project_2/tags
So when you tag something, you should end up with:
<svn_root>/project_1/tags/R1
<svn_root>/project_1/tags/R2
<svn_root>/project_1/tags/R3
<svn_root>/project_2/tags/R1
<svn_root>/project_2/tags/R2, etc...
It sounds like *you* have:
<svn_root>/trunk/project_1
<svn_root>/trunk/project_2
and are hoping to get:
<svn_root>/tags/R1/project_1
<svn_root>/tags/R2/project_1
Do I have it right, and if so, is it possible for you to switch it around? Many
tools (maven included) assume this layout.
---
Nayan Hajratwala
http://agileshrugged.com
http://twitter.com/nhajratw
734.658.6032
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
