maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Alberghini (JIRA)" <>
Subject [jira] Commented: (DOXIA-380) Use of #include in APT page causes NullPointerException during page rendering
Date Tue, 16 Feb 2010 10:59:55 GMT


Alan Alberghini commented on DOXIA-380:

Sure, no problem.
I just stripped down my maven project and included a sample test page (index.apt.vm).
The target site is rendered using "mvn site:site".
The #set directive works, but the #include heavily messes things up.

> Use of #include in APT page causes NullPointerException during page rendering
> -----------------------------------------------------------------------------
>                 Key: DOXIA-380
>                 URL:
>             Project: Maven Doxia
>          Issue Type: Bug
>          Components: Site Renderer
>         Environment: maven 2.2.1
>            Reporter: Alan Alberghini
>            Priority: Minor
>         Attachments: apt-include.log
> In the last 2 days I tried to get this thing working.
> The situation is the following: I'm working on a maven site project and, for some pages,
I'm currently using the APT format.
> I'd really like to be able to include existing APT pages inside an APT page, in order
to make the collaboration between the 4 members of the project much easier and smoother.
> To give an idea, I'd like to do this:
> merged-page.apt:
>   ---
>   Title
>   ---
>   ---
>   ---
>   Develeper 1 proposal:
>   <include page 1>
>   Developer 2 proposal:
>   <include page 2>
>   etc.
> At first, I tried using the %snippet DOXIA macro, but the included APT page would not
be rendered to HTML even setting verbatim=false.
> Then, I tried the #include macro from Velocity. I renamed my APT file to filename.apt.vm
in order to trigger the Velocity processor on it and put the #include line in the file, but,
whenever I launch maven site I keep getting this error:
> and the page is not generated.
> Is there a way to fix this?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message