I tried it with the m-r-p 2.5 and 1.9 of the jgit provider - same issue it does not work /Domi
On 18 Jul 2014, at 17:01, [email protected] wrote: > i do have the latest m-release-p, but the git version i don't know how to > set that nor what it currently is. How can i check that? > > Thank you Martin > > Alejandro Endo | Software Designer/Concepteur de logiciels > > > > > > From: Martin Gainty <[email protected]> > To: "[email protected]" <[email protected]>, > Date: 2014-07-18 10:26 > Subject: RE: mvn release with pom.xml not in root of git repo > > > > >> To: [email protected] >> Subject: Re: mvn release with pom.xml not in root of git repo >> From: [email protected] >> Date: Fri, 18 Jul 2014 09:53:50 -0400 >> >> I've been tracking this bug for a while now >> Still no progress >> >> You can track it here. There is a workaround there that i haven't tried >> >> Let us know if you try it and whether it works >> >> https://jira.codehaus.org/browse/MRELEASE-875 >> >> Alejandro Endo | Software Designer/Concepteur de logiciels > MG>Alejando- > MG>did you try latest maven-release-plugin with GIT 2.5 (as robert > suggested) ? > MG>Saludos desde EEUU/Salutations aux États-Unis > MG>Martin >> >> >> >> >> From: "[email protected]" <[email protected]> >> To: Maven Users List <[email protected]>, >> Date: 2014-07-18 00:39 >> Subject: mvn release with pom.xml not in root of git repo >> >> >> >> Hi, >> >> This question has been asked quite a couple of times already, but I > never >> found a real solution nor do I know if this should really be supported: >> Is it possible to do a release with the maven-release-plugin when the >> parent pom.xml is not in the root of the git repo? >> This is no problem with Subversion, but with git I have never managed to > >> get this working. >> >> so layout is like this: >> >> repo-dir >> |_.git >> |_subdir/pom.xml >> |_subdir/subsubdir/pom.xml >> >> has anyone done this? how? >> >> Domi >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> >> DISCLAIMER: >> Privileged and/or Confidential information may be contained in this >> message. If you are not the addressee of this message, you may not >> copy, use or deliver this message to anyone. In such event, you >> should destroy the message and kindly notify the sender by reply >> e-mail. It is understood that opinions or conclusions that do not >> relate to the official business of the company are neither given >> nor endorsed by the company. >> Thank You. > > > DISCLAIMER: > Privileged and/or Confidential information may be contained in this > message. If you are not the addressee of this message, you may not > copy, use or deliver this message to anyone. In such event, you > should destroy the message and kindly notify the sender by reply > e-mail. It is understood that opinions or conclusions that do not > relate to the official business of the company are neither given > nor endorsed by the company. > Thank You. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
