Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 98613 invoked from network); 2 Nov 2010 21:38:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Nov 2010 21:38:45 -0000 Received: (qmail 93618 invoked by uid 500); 2 Nov 2010 21:39:14 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 93505 invoked by uid 500); 2 Nov 2010 21:39:13 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 93497 invoked by uid 99); 2 Nov 2010 21:39:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 21:39:13 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gcjtmu-turbine-maven-user-846@m.gmane.org designates 80.91.229.12 as permitted sender) Received: from [80.91.229.12] (HELO lo.gmane.org) (80.91.229.12) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Nov 2010 21:39:04 +0000 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PDOZ1-0004Ms-30 for users@maven.apache.org; Tue, 02 Nov 2010 22:38:43 +0100 Received: from hsi-kbw-078-042-101-027.hsi3.kabel-badenwuerttemberg.de ([78.42.101.27]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Nov 2010 22:38:43 +0100 Received: from joerg.schaible by hsi-kbw-078-042-101-027.hsi3.kabel-badenwuerttemberg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Nov 2010 22:38:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: users@maven.apache.org To: users@maven.apache.org From: =?UTF-8?B?SsO2cmc=?= Schaible Subject: Re: maven-resources-plugin & file-encoding Followup-To: gmane.comp.jakarta.turbine.maven.user Date: Tue, 02 Nov 2010 22:38:32 +0100 Lines: 29 Message-ID: References: <4CCEF2F9.9000105@adesso.at> <4CD04FC2.3030801@j-hohwiller.de> <4CD05270.4060203@adesso.at> <4CD05579.6030209@j-hohwiller.de> <4CD05A5A.6050401@adesso.at> <4CD061C8.7080301@adesso.at> Reply-To: joerg.schaible@gmx.de Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: hsi-kbw-078-042-101-027.hsi3.kabel-badenwuerttemberg.de Mail-Copies-To: nobody User-Agent: KNode/4.4.5 X-Virus-Checked: Checked by ClamAV on apache.org Hi Roland, Asmann, Roland wrote: > Hi Jörg, > > That plugin is tuned for single files, right? That would mean I'd have > to have all developers include the plugin with its configuration in > their POMs... I'd rather have a solution in a parent-POM (we use a > company-wide master)... > > Also, if there is at least one correct Umlaut in there, it will probably > say the file is correct as well, right? > > So, in all, it's a nice workaround, but still not an actual solution... > :-( yes, that would have been a single file solution only. However, the real problem is, that some people commit files with wrong encoding. If you tell Maven that the file *is* UTF-8, then you have to ensure, that only files in this encoding can be committed at all e.g. in Subversion using a commit hook. The problem is the *detection*. We normally force ASCII. This is fine for all kind of source code and easy to detect. If some non-ASCII character has to be in the code, you can always encode it with a Unicode notation (e.g. \uXXXX). This is true for Java, property files, JavaScript, XML, HTML, ... - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org