Return-Path: X-Original-To: apmail-continuum-dev-archive@www.apache.org Delivered-To: apmail-continuum-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 EE987CC1E for ; Sat, 22 Jun 2013 15:59:06 +0000 (UTC) Received: (qmail 6341 invoked by uid 500); 22 Jun 2013 15:59:06 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 6188 invoked by uid 500); 22 Jun 2013 15:58:59 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 6178 invoked by uid 99); 22 Jun 2013 15:58:58 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Jun 2013 15:58:58 +0000 Received: from localhost (HELO mail-oa0-f45.google.com) (127.0.0.1) (smtp-auth username batkinson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Jun 2013 15:58:57 +0000 Received: by mail-oa0-f45.google.com with SMTP id j1so10357738oag.4 for ; Sat, 22 Jun 2013 08:58:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=pxqXMxc21xvX8GLQjQwc20+VjkOh8U5mbuCcMlfGr3o=; b=Hu6Zabq+X5EYw5jVQgp8QXlS1dW7ewEI5vzxoMkihL3RYW/kowV102UQ4DAHYFf6XM U7wEwSrE6iPo9mSWvuOB9QhzImY/vOUbEMt4OqkBI7thpiZDo9aTDCh845c/O+CK36nq rN1NtRytAXbnMohdE0vIU6Jp6oh3ZOpFkqcWNG88BlQB9mXyiXczeQWLXFY1u/i73zwZ 1HS6/snWdChmpQ32qAuN4P7zhMhsaK5jEv1H3tj8nx37uNbF8V5Cu6UgNu3XQWlL+T0H q0Qcr6OUG+z8Y6SJjhGNvk0/rzuBOa5gLg3QfLIw2ccKy2M5Vnw6nWOPFfJzPWGUePOg Y+Rw== MIME-Version: 1.0 X-Received: by 10.60.174.111 with SMTP id br15mr8186967oec.130.1371916736831; Sat, 22 Jun 2013 08:58:56 -0700 (PDT) Received: by 10.60.2.10 with HTTP; Sat, 22 Jun 2013 08:58:56 -0700 (PDT) Date: Sat, 22 Jun 2013 11:58:56 -0400 Message-ID: Subject: Patching javadocs From: Brent Atkinson To: dev Content-Type: multipart/alternative; boundary=089e011603f2c2aa5b04dfc04128 --089e011603f2c2aa5b04dfc04128 Content-Type: text/plain; charset=ISO-8859-1 Greetings, I have some time to patch frame injection vulnerability in the project javadocs. Since this is the first time publishing the docs, I'd like someone to verify the process for me. From http://continuum.apache.org/development/publishing-site.html it appears that I: * check out the source under http://svn.apache.org/repos/asf/continuum/site-publish * patch the docs * run "mvn site site:stage scm-publish:publish-scm" That should update the existing docs. How should we ensure new docs don't get published with the vulnerability? Would that be something we'd do with enforcer and require versions? Brent --089e011603f2c2aa5b04dfc04128--