www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Schaefer (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-4699) Use svnpubsub for all Logging and all of its subprojects
Date Thu, 31 May 2012 02:17:23 GMT

    [ https://issues.apache.org/jira/browse/INFRA-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286267#comment-13286267
] 

Joe Schaefer edited comment on INFRA-4699 at 5/31/12 2:16 AM:
--------------------------------------------------------------

Here's how you'd do this using view.pm/path.pm:

in path.pm:
--------------------------------------------------------------
my %POM_ARGS = (
   ... unravel the pom and place the args here in key=>value form
);

our @patterns = (
    [ qx!\.twig$!, page => \%POM_ARGS ],
);

1;
--------------------------------------------------------------
in view.pm
--------------------------------------------------------------
use Dotiac::DTL qw/Template *TEMPLATE_DIRS/;
use Dotiac::DTL::Addon::markup;
our @TEMPLATE_DIRS = "templates";

sub page {
    my %args = @_;
    Template($args{path})->render(\%args), html => \%args;
}

1;
---------------------------------------------------------------

All you'd need to do is reorg the site so it's not arranged
like a maven site (ie all content in content/ is merged
in its proper place without the resources|pages directory split).
And use {% comment %} {% endcomment %} for django comments,
as well as repositioning the {% extends %} directive to lie on the first
line in the file.

HTH

The upside is that if your site ever gets larger than a few pages,
the perl build system is much faster than anything available in php.
And you are using standard supported tools ;-).

                
      was (Author: joes):
    Here's how you'd do this using view.pm/path.pm:

in path.pm:
--------------------------------------------------------------
my %POM_ARGS = (
   ... unravel the pom and place the args here in key=>value form
);

our @patterns = (
    [ qx!\.twig$!, page => \%POM_ARGS ],
);

1;
--------------------------------------------------------------
in view.pm
--------------------------------------------------------------
use Dotiac::DTL qw/Template *TEMPLATE_DIRS/;
use Dotiac::DTL::Addon::markup;
our @TEMPLATE_DIRS = "templates";

sub page {
    my %args = @_;
    Template($args{path})->render(\%args) => html;
}

1;
---------------------------------------------------------------

All you'd need to do is reorg the site so it's not arranged
like a maven site (ie all content in content/ is merged
in its proper place without the resources|pages directory split).
And use {% comment %} {% endcomment %} for django comments,
as well as repositioning the {% extends %} directive to lie on the first
line in the file.

HTH

The upside is that if your site ever gets larger than a few pages,
the perl build system is much faster than anything available in php.
And you are using standard supported tools ;-).

                  
> Use svnpubsub for all Logging and all of its subprojects
> --------------------------------------------------------
>
>                 Key: INFRA-4699
>                 URL: https://issues.apache.org/jira/browse/INFRA-4699
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: SvnPubSub, Website
>            Reporter: Ralph Goers
>
> We would like to have the Logging project site and all of the Logging subproject sites
published via svnpubsub
> Here are the svn urls and the expected website urls: 
> * https://svn.apache.org/repos/asf/logging/site/main/live/ to be deployed at http://logging.apache.org/

> * https://svn.apache.org/repos/asf/logging/site/log4j/live/ to be deployed at http://logging.apache.org/log4j

> * https://svn.apache.org/repos/asf/logging/site/log4j2/live/ to be deployed at http://logging.apache.org/log4j2

> * https://svn.apache.org/repos/asf/logging/site/log4php/live/ to be deployed at http://logging.apache.org/log4php

> * https://svn.apache.org/repos/asf/logging/site/log4cxx/live/ to be deployed at http://logging.apache.org/log4cxx
> * https://svn.apache.org/repos/asf/logging/site/log4net/live/ to be deployed at http://logging.apache.org/log4net
> * https://svn.apache.org/repos/asf/logging/site/chainsaw/live/ to be deployed at http://logging.apache.org/chainsaw

> * https://svn.apache.org/repos/asf/logging/site/companions/live/ to be deployed at http://logging.apache.org/companions

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message