You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alan Alberghini (JIRA)" <ji...@codehaus.org> on 2010/02/14 01:00:55 UTC
[jira] Created: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Alan Alberghini (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210673#action_210673 ]
Alan Alberghini commented on DOXIA-380:
---------------------------------------
bq. If you don't specify the version of a plugin, maven will use whatever is given in the super pom, ie it depends on the maven version you are using.That's why it is strongly recommended to always pin down the versions of all plugins you are using.
I see. Thanks for the info.
Do you think I should close the bug? The exceptions are still there...
> 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, VelocityTest.tar.gz
>
>
> 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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Alan Alberghini (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210302#action_210302 ]
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: 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
[jira] Updated: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated DOXIA-380:
--------------------------------
Description:
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:
{noformat} ---
Title
---
---
---
Develeper 1 proposal:
<include page 1>
Developer 2 proposal:
<include page 2>
etc.{noformat}
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?
was:
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?
> Use of #include in APT page causes NullPointerException during page rendering
> -----------------------------------------------------------------------------
>
> Key: DOXIA-380
> URL: https://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, VelocityTest.tar.gz
>
>
> 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:
> {noformat} ---
> Title
> ---
> ---
> ---
> Develeper 1 proposal:
> <include page 1>
> Developer 2 proposal:
> <include page 2>
> etc.{noformat}
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-68) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg moved DOXIA-380 to DOXIASITETOOLS-68:
-----------------------------------------------------
Component/s: (was: Site Renderer)
Site renderer
Key: DOXIASITETOOLS-68 (was: DOXIA-380)
Project: Maven Doxia Sitetools (was: Maven Doxia)
> Use of #include in APT page causes NullPointerException during page rendering
> -----------------------------------------------------------------------------
>
> Key: DOXIASITETOOLS-68
> URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-68
> Project: Maven Doxia Sitetools
> Issue Type: Bug
> Components: Site renderer
> Environment: maven 2.2.1
> Reporter: Alan Alberghini
> Priority: Minor
> Attachments: apt-include.log, VelocityTest.tar.gz
>
>
> 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:
> {noformat} ---
> Title
> ---
> ---
> ---
> Develeper 1 proposal:
> <include page 1>
> Developer 2 proposal:
> <include page 2>
> etc.{noformat}
> 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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Alan Alberghini (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210422#action_210422 ]
Alan Alberghini commented on DOXIA-380:
---------------------------------------
> For reference: this has been reported before: http://www.mail-archive.com/users@maven.apache.org/msg98932.html
I saw that message, but the issue was not resolved so I decided to open a bug report.
>Using site-plugin 2.1 (ie Doxia-1.1) I get the same error message but the resulting index.html is actually correct. Can you confirm?
Yes, the HTML page is rendered now correctly but the exceptions continue to show up. A bit odd, but I can live with that :). Thank you very much for the help.
Out of curiosity, why version 2.1 of the site-plugin is not automatically chosen if I don't specify the artifact version in the POM? Is it because of the major changes involved in Doxia 1.1?
> 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, VelocityTest.tar.gz
>
>
> 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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210355#action_210355 ]
Lukas Theussl commented on DOXIA-380:
-------------------------------------
Using site-plugin 2.1 (ie Doxia-1.1) I get the same error message but the resulting index.html is actually correct. Can you confirm?
> 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, VelocityTest.tar.gz
>
>
> 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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210354#action_210354 ]
Lukas Theussl commented on DOXIA-380:
-------------------------------------
For reference: this has been reported before: http://www.mail-archive.com/users@maven.apache.org/msg98932.html
> 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, VelocityTest.tar.gz
>
>
> 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
[jira] Updated: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Alan Alberghini (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Alberghini updated DOXIA-380:
----------------------------------
Attachment: VelocityTest.tar.gz
> 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, VelocityTest.tar.gz
>
>
> 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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210943#action_210943 ]
Lukas Theussl commented on DOXIA-380:
-------------------------------------
Let's leave it open for reference until somebody figures out what is going on exactly...
> 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, VelocityTest.tar.gz
>
>
> 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
[jira] Commented: (DOXIA-380) Use of #include in APT page causes
NullPointerException during page rendering
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210621#action_210621 ]
Lukas Theussl commented on DOXIA-380:
-------------------------------------
bq. I saw that message, but the issue was not resolved so I decided to open a bug report.
Well done! :)
bq. Out of curiosity, why version 2.1 of the site-plugin is not automatically chosen if I don't specify the artifact version in the POM? Is it because of the major changes involved in Doxia 1.1?
If you don't specify the version of a plugin, maven will use whatever is given in the super pom, ie it depends on the maven version you are using.That's why it is strongly recommended to always pin down the versions of all plugins you are using.
> 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, VelocityTest.tar.gz
>
>
> 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