is
> trunk/parent/pom.xml.
Why not let trunk/parent/pom.xml point to trunk/pom.xml as parent?
And trunk/module1/pom.xml youle point to trunk/parent/pom.xml as parent.
Then you should be able to release your project from trunk.
This used to work for me.
LieGrue,
strub
--- On Sun, 5/23/10, Juven
I met the same issue, and created a ticket:
http://jira.codehaus.org/browse/MRELEASE-562
2010/4/19 Thomas Scheffler
> Am 19.04.2010 12:47, schrieb Stephen Connolly:
>
> You need to run the release from the aggregator pom. not from the parent.
>>
>
> That was exactly the way I was doing it.
>
>
Am 19.04.2010 12:47, schrieb Stephen Connolly:
You need to run the release from the aggregator pom. not from the parent.
That was exactly the way I was doing it.
The SCM information will effectively be ignored by the release plugin in all
but the aggregator root.
But you will want the SCM i
You need to run the release from the aggregator pom. not from the parent.
The SCM information will effectively be ignored by the release plugin in all
but the aggregator root.
But you will want the SCM info in each project so that the project site will
contain the correct information
2010/4/19
Hi,
after migrating our old ant build system to maven our first non-SNAPSHOT
release is planned. But I have difficulties to get it work with the
release plugin.
SVN layout is this:
branches/
tags/
trunk/
|-- pom.xml
|-- parent/
| `-- pom.xml
|-- module1/
| `-- pom.xml
|--
