Having recently switched from svn to git for most of my projects, I have an opinion.
I think you should create a JIRA ticket and consider this a bug. What we're dealing with here is a bit of svn-centric thinking during design. It needs to be fixed. -K On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote: > We're considering migrating from svn to git, we stumble on the > maven-release-plugin usage with git. > We think we prefer to use a single repository for many independently built > projects like : > > foobar-repo.git > |-> project-foo/ > | |-> pom.xml > | |–> module A/ > | |-> module B/ > | > |-> project-bar/ > |-> pom.xml > > > project-bar scm url looks like : > <connection>scm:git:ssh://somehost.nowhere:/foobar-repo.git </connection> > > This hints to the right repository but I can't write that the actual > project-bar is in the project-bar subdirectory. > > mvn release:prepare goes well and ends succesfully. > > mvn release:perform fails whenever it tries to build the project from the > tag. It effectively clone correctly the repository. > But use the root of the repository rather than going into project-bar > subdirectory whenever it tries to clean deploy the tag. > > This prevent using git and multiple projects in the same directory. > Some may think we should use gitmodules but > 1) the release plugin does not support it [1] > 2) gitmodules is an aggregate of single repository > > Should I issue a "new feature" ticket into jira project MRELEASE or SCM ? > Or should I fall back to the current convention of 1 project = 1 git > repository ?? > Or maybe someone managed to do it ? > > any advice appreciated. > > [1] : http://jira.codehaus.org/browse/SCM-530 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
