Hello everybody,
My team is currently migrating a legacy Ant project with a bad Subversion
layout to Maven.
We're running into 2 problems with the Maven scm configuration.
Let me first sketch the Subversion layout:
ROOT
- trunk
-- department
- parent
- pom.xml
- project1
- pom.xml (inherits parent)
- project2
- pom.xml (inherits parent)
- release
- pom.xml (inherits parent)
- branches
- feature1
- department
- parent
- pom.xml
- project1
- pom.xml (inherits parent)
- project2
- pom.xml (inherits parent)
- release
- pom.xml (inherits parent)
- tags
- ...
When developping code, we work on branches, we then merge back to trunk and at
some point we make a new branch from trunk for the release.
Since we have our trunk and branches on a higher level than the projects, we
would have to add the branch name in the <scm> URL to gain a full path.
Of course this is not what we want, because the Maven release plugin won't know
how to make tags etc.
One possibility might be to use a compound of 2 variables (base url and branch
name) and a relative path, but this feels like a very dirty workaround.
Does any of you have experience with a setup like this?
Kind regards,
Melvyn de Kort
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
