I put the pom.xml right at the root of the repo and it works. I would still like to know more about how mercurial and scm work (such as tagging, branching and 'push'. Because they don't appear to be documented anywhere.
On Mon, Feb 15, 2010 at 2:15 PM, Andrew Hughes <[email protected]> wrote: > Hi All, > > I'm suck on the Mercurial SCM plugin, my repo's @ * > C:\Mercurial\Clones\project-xyz\* > > And it contain's *./project-xyz/pom.xml* and thus gives: * > C:\Mercurial\Clones\project-xyz\project-xyz\pom.xml* > > Follwing this blog: > http://www.chrissearle.org/blog/technical/using_maven2_scm_and_release_plugins_with_mercurialhg > > I should only need to have: > > <scm> > <connection>scm:hg:file://${basedir}</connection> > <developerConnection>scm:hg:file://${basedir}</developerConnection> > </scm> > > But maven (scm) seems to want the repository root, for example: > > *[DEBUG] abort: repository C:\Mercurial\Clones\project-xyz\project-xyz not > found!* > > > This would work in SVN, but not in mercurial. Which seems to want the > pom.xml in the root of the repo: *C:\Mercurial\Clones\project-xyz\pom.xml > which > seems quite restrictive and stupid (when someone just wants to release a > module).* > > Documentation is very sparse. So any help explaining how this is configured > would be *most* welcome :) > > Cheers :) >
