X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 11 May 2010 10:23:35 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: MS-DOS path warning with maven Message-ID: <20100511142335.GB728@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4BE81BBF DOT 7040700 AT bopp DOT net> <4BE855DD DOT 4090506 AT bopp DOT net> <4BE86F45 DOT 9080606 AT bopp DOT net> <4BE95E6C DOT 7000304 AT bopp DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BE95E6C.7000304@bopp.net> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Tue, May 11, 2010 at 08:41:00AM -0500, Jeremy Bopp wrote: >On 5/11/2010 3:51 AM, David Bala??ic wrote: >> On 10 May 2010 22:40, Jeremy Bopp wrote: >>> On 5/10/2010 3:11 PM, David Bala??ic wrote: >>>> On 10 May 2010 20:52, Jeremy Bopp wrote: >>>>> What's the output when you run the following? >>>>> >>>>> $ sh -x "$(which mvn)" -version >>>> >>>> I attached it. >>> >>> I don't see the Cygwin warning message in that output. What I did see >>> in the output, though, tells me that there shouldn't be anything causing >>> that message at all. >>> >>> Try running the following to see if it captures the warning message: >>> >>> $ sh -x "$(which mvn)" -version >mvn.log 2>&1 >> >> Attached, this time including the warning. > >The attachment appears to have been stripped by the list server. I'm >not sure what it will take to work around the server, so please send log >file to me directly. Given that this issue with Maven isn't a Cygwin >problem, this list is not the most appropriate forum for this discussion >anyway. The list server does not strip attachments but, regardless, you're right: this is not the appropriate list for this discussion. We can't debug problems with every program that uses cygwin1.dll here. cgf -- 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