Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8A589545 for ; Mon, 29 Oct 2012 00:13:12 +0000 (UTC) Received: (qmail 18855 invoked by uid 500); 29 Oct 2012 00:13:12 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 18812 invoked by uid 500); 29 Oct 2012 00:13:12 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 18801 invoked by uid 99); 29 Oct 2012 00:13:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 00:13:12 +0000 Date: Mon, 29 Oct 2012 00:13:11 +0000 (UTC) From: "Chip Childers (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: <1117849992.37353.1351469592233.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CLOUDSTACK-422) XSL files missing license header MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Chip Childers created CLOUDSTACK-422: ---------------------------------------- Summary: XSL files missing license header Key: CLOUDSTACK-422 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-422 Project: CloudStack Issue Type: Bug Affects Versions: 4.0.0 Reporter: Chip Childers Priority: Critical Fix For: 4.1.0 These are in the 4.0 branch. > setup/apidoc/generateadmincommands.xsl > setup/apidoc/generatecommand.xsl > setup/apidoc/generatedomainadmincommands.xsl > setup/apidoc/generatetoc_footer.xsl > setup/apidoc/generateusercommands.xsl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira