if I read Jazz SCM url format [1], in a multi-module build, scm info automatically calculated from root to modules (ie appending artifact-id) will give wrong scm info, no? did you try it?
there are 2 other parts: - m-release-p: did you add any logic to deal with plugin scm info modification when tagging a version? - m-pir-p: when you do a checkout (or clone, or view, I don't know the exact term for Jazz), IIUC, you get a repository copy: did you write some instructions in the generated page to cd to module base directory? (again for multi-module builds) Regards, Hervé [1] http://maven.apache.org/scm/jazz.html Le dimanche 1 septembre 2013 09:54:39 Chris Graham a écrit : > I did something similar in the Jazz provider. It's a complex URL, or can be > if it needs to be, but it's still a single line. > > It's just a matter of making the parser smarted. And that's local to the > provider, so go nuts. I also put lots of unit tests in there to illustrate > the correct and incorrect usage. > > -Chris > > On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY <[email protected]>wrote: > > Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit : > > > I agree that a single SCM line doesn't really match anymore with systems > > > like DSCM (git, Mercurial) > > > It would have been better if we could think of a better way to define > > > > this > > > > > in a newer POM-model. > > > > it was overkill at the time Maven was done, and even today, splitting scm > > developerConnection into 3 parts seems overkill for classical SCMs, even > > if > > doable > > > > notice that even with "single SCM line", we can have multiple fields, like > > we > > already have for example with git to distinguish fetch and push urls: > > <developerConnection>scm:git: > > [fetch=] > > http://mywebserver.org/path_to_repository[push=]ssh://username@otherserver > > :8898/~/repopath.git </developerConnection> > > > > in the same spirit, we could support a branch and a path parts > > <developerConnection>scm:git: > > https://git-wip-us.apache.org/repos/asf/maven.git[branch=]maven-3.0.x[path > > =]/maven-core </developerConnection> > > > > with such scm url format, we have the structure we like without POM format > > change, and module value inheritance by adding artifact-id to the url > > stays > > simple and consistent > > > > > > Regards, > > > > Hervé > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
