Maven Doxia Sitetools

Use of #include in APT page causes NullPointerException during page rendering

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Site renderer
  • Labels:
    None
  • Environment:
    maven 2.2.1
  • Number of attachments :
    2

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:

  ---
  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?

  1. Text File
    apt-include.log
    13/Feb/10 6:00 PM
    7 kB
    Alan Alberghini
  2. GZip Archive
    VelocityTest.tar.gz
    16/Feb/10 5:00 AM
    210 kB
    Alan Alberghini

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Lukas Theussl added a comment -

Can you attach a test project to reproduce the issue? (Just the velocity case, the snippet macro behaves as it should).

Show
Lukas Theussl added a comment - Can you attach a test project to reproduce the issue? (Just the velocity case, the snippet macro behaves as it should).
Hide
Permalink
Alan Alberghini added a comment -

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.

Show
Alan Alberghini added a comment - 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.
Hide
Permalink
Lukas Theussl added a comment -

For reference: this has been reported before: http://www.mail-archive.com/users@maven.apache.org/msg98932.html

Show
Lukas Theussl added a comment - For reference: this has been reported before: http://www.mail-archive.com/users@maven.apache.org/msg98932.html
Hide
Permalink
Lukas Theussl added a comment -

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?

Show
Lukas Theussl added a comment - 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?
Hide
Permalink
Alan Alberghini added a comment -

> 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?

Show
Alan Alberghini added a comment - > 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?
Hide
Permalink
Lukas Theussl added a comment -

I saw that message, but the issue was not resolved so I decided to open a bug report.

Well done!

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.

Show
Lukas Theussl added a comment - I saw that message, but the issue was not resolved so I decided to open a bug report. Well done! 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.
Hide
Permalink
Alan Alberghini added a comment -

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...

Show
Alan Alberghini added a comment - 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...
Hide
Permalink
Lukas Theussl added a comment -

Let's leave it open for reference until somebody figures out what is going on exactly...

Show
Lukas Theussl added a comment - Let's leave it open for reference until somebody figures out what is going on exactly...

People

  • Assignee:
    Unassigned
    Reporter:
    Alan Alberghini
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: