Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of
 gcjtmu-turbine-maven-user-846@m.gmane.org designates 80.91.229.3 as permitted
 sender)
To: users@maven.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: With mvn release:prepare,
 is it possible to instruct Maven to use a forward slash in the submodule pom
 locations for the commit command?
Date: Fri, 28 Jun 2013 23:21:18 +0200
Lines: 22
Message-ID: <kqkuo8$to0$1@ger.gmane.org>
References: 
 <CAMyxUi12_Y+=cZpd1Mj1h8Y5ykwZLmUwoyJYu=yvwdzM7wdpbQ@mail.gmail.com>
Reply-To: joerg.schaible@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/4.10.3

Hi Don,

Don Branson wrote:

> I'm trying to resolve an issue which I've posted at
> http://stackoverflow.com/questions/17367079/with-mvn-releaseprepare-is-it-possible-to-instruct-maven-to-use-a-forward-slas.
> Is this a known issue with Maven+git+Cygwin? Is there a solution?

Years ago I was in this situation with Maven+svn+Cygwin. I simply 
deinstalled the Cygwin svn and used a Windows version of the command line. 
You just have to ensure that you checkout your sources in a directory that 
is mounted with Cygwin's text flag i.e. my sources had all CR/LF EOL's and 
all the Cygwin tools expected that because of the text mount.

Maybe you can use a similar setup with git ...

The main problem was (and is IIRC) that you don't have a Cygwin version of a 
JDK and therefore all Java applications were using Windows paths. However, 
10 years ago, you had no option, but today you might be able to build 
icedtea. Maybe it is in the meanwhile available for Cygwin?

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org