maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: mvn release with pom.xml not in root of git repo
Date Fri, 18 Jul 2014 14:25:26 GMT

> To: users@maven.apache.org
> Subject: Re: mvn release with pom.xml not in root of git repo
> From: Alejandro.Endo@miranda.com
> 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:   "domi@fortysix.ch" <domi@fortysix.ch>
> To:     Maven Users List <users@maven.apache.org>, 
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 
> 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.
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message