I tried adding "*commitByProject<http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#commitByProject>" and that got me a bit further.
I can see it commit properly, but the push step is failing because it's trying to push a repo that hasn't had any changes in it yet. For instance, during the release prepare step, the build is started in the "aggregate" directory and a pom in ../jar is altered. But the push is trying to push the "aggregate" repository, NOT the "jar" repository. Any suggestions? * On Fri, Jan 27, 2012 at 11:43 AM, Maven User <maven.2.u...@gmail.com> wrote: > Hi all - > > I have a quick question about the release plugin. > > If your aggregate pom is NOT a parent pom, can you execute the release > from there? > > I keep running into an issue where because my modules are not directories > under the aggregate pom, the commit and tag of the scm project is failing. > > For instance: > > aggregate/pom.xml > = module -> ../jar > > in the jar/pom.xml it has an entirely different parent. > > Any suggestions? > > I'm just trying to use the aggregate pom to group up things I need the > maven release to run against.... >
