Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A0F518C51 for ; Sun, 31 Jan 2016 15:04:46 +0000 (UTC) Received: (qmail 57321 invoked by uid 500); 31 Jan 2016 15:04:46 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 57285 invoked by uid 500); 31 Jan 2016 15:04:46 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 57273 invoked by uid 99); 31 Jan 2016 15:04:45 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Jan 2016 15:04:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 1672618027C for ; Sun, 31 Jan 2016 15:04:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id j93GUGq4XUAt for ; Sun, 31 Jan 2016 15:04:33 +0000 (UTC) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id DFCB720271 for ; Sun, 31 Jan 2016 15:04:32 +0000 (UTC) Received: by mail-io0-f173.google.com with SMTP id 9so53846159iom.1 for ; Sun, 31 Jan 2016 07:04:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=JGKNk8MGHK1+iYsY2YvybuC6e/fftKn+XZPFXYcVQAQ=; b=qs75ou5BqqCuAiyTvxUbvD7j/RKXEXvt29YHvlFlkF0ty5Z/tGI5ZB5OlWY3zZbdgB AgPTTDZQAgUdj4YNXasr22VZqJvAFdwmcsGDFZ7WGe4FpIlj3hdmi6zpM+YRhcf3Ekp0 XHK5xP7BXmyV8uzCsTTEbA5GDmm8+ItEw7ppOyiJQL2/oMr9NAlVZKGZGUPt9xr5vnIF VQpcil9tyywM5o5OEOSsyZoAWr8Lb4kgLl9XygKT9jniiqC0MXNsc+bNpvr1rUlReX27 jPKJAkVqF3CU+7QO1su2uskLikHIm8OgvPX4pCiQTqXszmf40eBW2jIkJi3dg4gDZjyB 4PoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=JGKNk8MGHK1+iYsY2YvybuC6e/fftKn+XZPFXYcVQAQ=; b=HM4Du9muWattWnwJ6Xs0cgofhuT0uAD1NfOMhsbV4LCQJJ1i17QPtZAF4SUc/WqAhC L2r6gEshhzXWFMfDENQClmEKJBqcQWmOD9/wVdSKHX47KYD71lkTo3yUv2AW9RrELOis QZKgbQDH3RYE2Qa67kWZgB/fqS73F/aGZiZY6jyuNyCVNf2QOPd3sEAwfRNo3M7P9Y14 bg1si6gscZ1r2YPkOdPJsfA2O9Dne/km50y0oyCgeiTnZpruhA6NzadNP5UccBEGYNkU ren4dJmmLGazFQjN68f2f9rRO6197gCXa03vQSmwEg2hWe4lt+92NGy/mvbi0sMsquVH ppeQ== X-Gm-Message-State: AG10YORs6vXGn3nH5i75eriA+T1iWNFvum2jwqW4SeruzMwlrg4gOLQ485INJeJnEfod8Oqs7nNsNDjOJbI1UA== MIME-Version: 1.0 X-Received: by 10.107.16.8 with SMTP id y8mr14373640ioi.21.1454252672408; Sun, 31 Jan 2016 07:04:32 -0800 (PST) Received: by 10.79.38.23 with HTTP; Sun, 31 Jan 2016 07:04:32 -0800 (PST) In-Reply-To: References: Date: Sun, 31 Jan 2016 07:04:32 -0800 Message-ID: Subject: Re: A change to the site code UI From: Justin Ross To: "users@qpid.apache.org" , Keith Wall Content-Type: multipart/alternative; boundary=001a113fe9bcf3e4c1052aa2956d --001a113fe9bcf3e4c1052aa2956d Content-Type: text/plain; charset=UTF-8 Hi, Keith. Thanks for finding that failure. I've committed a fix. http://svn.apache.org/viewvc/qpid/site/python/generate.py?r1=1727820&r2=1727819&pathrev=1727820 On the other question, I think that may be fair behavior for the gen-* scripts. In this specific instance, it's the removes in gen_books that are doing this: http://svn.apache.org/repos/asf/qpid/site/scripts/gen-java-release-books If we didn't do that, we'd be mingling the output of multiple docbook invocations. My feeling is that it's better to resolve that manually when the output changes, rather than overlay multiple outputs. It seems like there's a very good chance that changes to a shared file would lead to inconsistent output. This problem shouldn't arise very often. We only rarely change the structure of the docbook output. Justin On Sun, Jan 31, 2016 at 1:20 AM, Keith W wrote: > Hi Justin, > > I gave the change a test drive. It looks like a useful improvement. > > I did notice a couple of problems when trying to render trunk, which I > don't think are related to the change. > > 1) Running "make clean gen-cpp-release RELEASE=trunk" dies with the > following message. > > gen-cpp-release-api-doc: Removing > 'input/releases/qpid-cpp-trunk/messaging-api' > Traceback (most recent call last): > File "scripts/gen-cpp-release-api-doc", line 88, in > gen_messaging_api(release, source_dir, release_dir) > File "scripts/gen-cpp-release-api-doc", line 27, in gen_messaging_api > gen_cpp_messaging_api(release, source_dir, component_dir) > File "scripts/gen-cpp-release-api-doc", line 45, in gen_cpp_messaging_api > output_dir=output_dir) > File "/home/keith/src/site/python/generate.py", line 196, in gen_doxygen > append(path, local_conf) > NameError: global name 'local_conf' is not defined > > > 2) "make clean gen-java-release RELEASE=trunk" works successfully, but > existing svn owned directories beneath input/ get removed by script, > which upsets the SVN. > I think this problem will occur when republishing any release that > already exists in the tree. I see: > > keith@ubuntu:~/src/site$ svn status > ~ input/releases/qpid-java-trunk/jms-client-0-8 > ~ input/releases/qpid-java-trunk/java-broker > M input/releases/qpid-java-trunk/index.md > > The same problem happens with gen-cpp-release RELEASE=trunk. > > What do you think? > > cheers, Keith > > > On 29 January 2016 at 01:01, Justin Ross wrote: > > I made a usability change that impacts those who update the Qpid site > code. > > > > Previously "make render" would render once to the output/ dir (so you > could > > look at with your browser) and once to the docs/ dir (with its URLs ready > > for publication). > > > > Now I've isolated the publish step. Use "make render" as before to > update > > output/ and see the rendered content. Once you've iterated and you're > > satisfied with the changes, run "make publish". It renders to docs/ and > > finishes by printing the svn status of your docs/ dir and reminding you > > that there's one more thing to do: > > > > https://gist.github.com/ssorj/063434d2c2acb44b8aae > > > > The upside is that "make render", which one typically does more > frequently, > > is a little faster, and "make publish" does a little more to help you see > > what you need to commit. > > > > Justin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org > For additional commands, e-mail: users-help@qpid.apache.org > > --001a113fe9bcf3e4c1052aa2956d--