On Fri, Aug 28, 2009 at 6:09 AM, <johannes.konstantini...@capgemini-sdm.com> wrote: > Hello everyone, > > we have a problem with the Release Plugin due to our flat multi-project > structure in both the developer's hard drive and the CVS repository. > The bug is described in http://jira.codehaus.org/browse/MRELEASE-225, > which is marked as duplicate of http://jira.codehaus.org/browse/MRELEASE-261 > although I think they describe slightly different problems.
It sounds likes you have a bunch of issues that aren't easily addressed. A non-maven workaround might be to manually release each project. Modules give you the "helper" ability to run a maven command at the top of a project and for the same command to be applied to all modules (recursively). But this doesn't affect the dependency declarations in anyway (they stay the same regardless of whether there are modules present or not) I'm assuming you have customized parent/relativePath in your poms to get the flat structure. If maven can't find the parent then it will use the installed version instead. You will need to delete parent/relativePath to try this. So if you remove all modules (and parent/relativePath) and then manually invoke mvn release on each project in the same order that the module defintions would have you should have the correct behaviour. You should be able to see if this is a viable solution after the first couple of released projects. If it is viable you can then script the maven commands. Another alternative is to manually release the project. If release:prepare is working for you, then just checkout the tagged version and run mvn deploy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
