From dev-return-86978-archive-asf-public=cust-asf.ponee.io@sling.apache.org Mon Feb 26 22:07:20 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7E72C18067A for ; Mon, 26 Feb 2018 22:07:19 +0100 (CET) Received: (qmail 64645 invoked by uid 500); 26 Feb 2018 21:07:08 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 63755 invoked by uid 99); 26 Feb 2018 21:07:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2018 21:07:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 37A63C6109 for ; Mon, 26 Feb 2018 21:07:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id W_b8ietvdwaC for ; Mon, 26 Feb 2018 21:07:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EFE495FC4D for ; Mon, 26 Feb 2018 21:07:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 3E20CE0222 for ; Mon, 26 Feb 2018 21:07:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 90BB8255FC for ; Mon, 26 Feb 2018 21:07:02 +0000 (UTC) Date: Mon, 26 Feb 2018 21:07:02 +0000 (UTC) From: "Robert Munteanu (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SLING-3629) Provide an XML formatter for content.xml files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SLING-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3629: ----------------------------------- Fix Version/s: (was: Sling Eclipse IDE 1.2.2) Sling Eclipse IDE 1.2.4 > Provide an XML formatter for content.xml files > ---------------------------------------------- > > Key: SLING-3629 > URL: https://issues.apache.org/jira/browse/SLING-3629 > Project: Sling > Issue Type: Improvement > Components: IDE > Reporter: Robert Munteanu > Priority: Minor > Fix For: Sling Eclipse IDE 1.2.4 > > > When editing resource properties through the JCR properties view, we format the corresponding XML according to the vault canonical format. At the same time, there is no such provision for working with content.xml files directly in the editor. > While I don't think that we should format them automatically, it would be useful to have a formatter which can be manually invoked. -- This message was sent by Atlassian JIRA (v7.6.3#76005)