Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0BCAA18CF6 for ; Sat, 12 Dec 2015 10:42:34 +0000 (UTC) Received: (qmail 79757 invoked by uid 500); 12 Dec 2015 10:42:33 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 79682 invoked by uid 500); 12 Dec 2015 10:42:33 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 79670 invoked by uid 99); 12 Dec 2015 10:42:33 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2015 10:42:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0A147C0F62 for ; Sat, 12 Dec 2015 10:42:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.554 X-Spam-Level: X-Spam-Status: No, score=-0.554 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.554, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 1lkpKBl97k0f for ; Sat, 12 Dec 2015 10:42:30 +0000 (UTC) Received: from vps.schulte.it (vps.schulte.it [176.28.31.178]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 46F7521271 for ; Sat, 12 Dec 2015 10:42:30 +0000 (UTC) Received: from t60.schulte.it (p5DE905E7.dip0.t-ipconnect.de [93.233.5.231]) (authenticated bits=0) by vps.schulte.it (8.14.3/8.14.3/Debian-9.4) with ESMTP id tBCAgMNd019537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 12 Dec 2015 11:42:23 +0100 X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.7 at vps.schulte.it Subject: Re: svn commit: r1719483 - in /maven/doxia/doxia/trunk: doxia-core/src/main/java/org/apache/maven/doxia/markup/ doxia-core/src/main/java/org/apache/maven/doxia/parser/ doxia-core/src/main/java/org/apache/maven/doxia/sink/ doxia-core/src/test/java/org/apach... To: Maven Developers List References: <20151211180120.8CF753A01D9@svn01-us-west.apache.org> <566B3997.9000003@schulte.it> <2693618.GQqBs1V6AS@herve-desktop> From: Christian Schulte Message-ID: <566BFA0E.5060404@schulte.it> Date: Sat, 12 Dec 2015 11:42:22 +0100 User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <2693618.GQqBs1V6AS@herve-desktop> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.7 (vps.schulte.it [176.28.31.178]); Sat, 12 Dec 2015 11:42:23 +0100 (CET) Am 12/12/15 um 11:20 schrieb Herv� BOUTEMY: > is an API change in Doxia Sink API really necessary to add this HTML-specific > feature (in very specific context)? Not really that HTML-specific any more. I just renamed the method from 'ssi' to 'directive' locally. > Because whatever how the method is named, it won't have general meaning for > most parsers and sink implementations Depends on how it is used. It's just a comment starting with a '#' character which is handled differently than comments not starting with that character. > notice that this API change was detected and the CI is now failing... Noticed it. Nobody can ever enhance the Sink API? > And instead of accepting this Sink API change, I would prefer to avoid it for > this feature If a new method cannot be added to the Sink API, the only option would be to handle the directives in every implementation of the following method. /** * Add a comment. * * @param comment The comment to write. * @since 1.1 */ void comment( String comment ); So every Sink implementation would need to start parsing comments then. I'd like to avoid that. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org