X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_50,TW_MV X-Spam-Check-By: sourceware.org Message-ID: <4BE81BBF.7040700@bopp.net> Date: Mon, 10 May 2010 09:44:15 -0500 From: Jeremy Bopp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: MS-DOS path warning with maven References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 5/10/2010 4:21 AM, David Balažic wrote: > Hi! > > I have cygwin 1.7.5 (up to date as of now) on Windows XP Pro SP3 and > maven v 2.2.1. > > When I start mvn from a shell (I use mintty running bash): i get a warning: > > > cygwin warning: > MS-DOS style path detected: F:\winsux\prg\apache-maven-2.2.1/boot/ > Preferred POSIX equivalent is: /cygdrive/f/winsux/prg/apache-maven-2.2.1/boot/ > CYGWIN environment variable option "nodosfilewarning" turns off this warning. > Consult the user's guide for more details about POSIX paths: > http://cygwin.com/cygwin-ug-net/using.html#using-pathnames > > > I found it strange, since maven is cygwin aware and should use cygwin paths. > > Is this some bug? I'm unable to reproduce your problem when running a simple mvn -version command. After looking through the mvn script included with the Maven installation, I also can't see anywhere that script would directly attempt to use a Windows-style path where a POSIX style path would be required to avoid this warning. My best guess is that you are either defining the JAVACMD environment variable to point to a Cygwin program, defining JAVA_HOME to point to a Cygwin-based JRE/JDK, or have a Cygwin-based java.exe in your path. In all of those cases, the mvn script will attempt to feed Windows-style paths to a Cygwin program, and that would likely trigger this warning. If that's not the problem, it could be that whatever target you're trying to run ultimately attempts to run some Cygwin program with a Windows-style path. In all cases, Cygwin is functioning as designed. To diagnose the problem further, you need to first eliminate all of your build logic as the cause. Running mvn -version as I did should do that for you. Then make sure that you're not somehow causing a Cygwin program to be used in place of Sun's java.exe as noted above. If you do that and still see this warning, then you need to talk with the Maven developers and/or the developers of whatever Maven plugins you're using. HTH. -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple