You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2010/02/15 21:41:55 UTC
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210244#action_210244 ]
Lukas Theussl commented on DOXIA-380:
-------------------------------------
Can you attach a test project to reproduce the issue? (Just the velocity case, the snippet macro behaves as it should).
> Use of #include in APT page causes NullPointerException during page rendering
> -----------------------------------------------------------------------------
>
> Key: DOXIA-380
> URL: http://jira.codehaus.org/browse/DOXIA-380
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira