[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320777#comment-320777 ] Simone Tripodi commented on MSKINS-80: -- OH thanks for reporting Michael, believe it or not but I banged my head on the wall for a long while to understand where that problems is! Are you in the position to provide a patch to fix that bug? TIA! > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320782#comment-320782 ] Michael Osipov commented on MSKINS-80: -- Simone, while I could provide a patch for site.vm for that specific issue but we should seriously take into account that there are highly likely other visuals broken which we haven't spotted yet. I wouldn't blindly go to version 2.3. I would rather even check the diff between 2.2 and 2.3 and see what has changed in order to reflect that in site.vm. > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[
https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSKINS-80:
-
Attachment: bootstrap-2.2-to-2.3.patch
Git diff between version 2.2 and 2.3 for less files only.
{{git diff v2.2.0 v2.3.0 -- less}}
> Upgrade to Bootstrap 2.3 breaks design
> --
>
> Key: MSKINS-80
> URL: https://jira.codehaus.org/browse/MSKINS-80
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
>Affects Versions: fluido-1.3.1
>Reporter: Michael Osipov
> Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap
> 2.3.png
>
>
> Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that
> many CSS styles aren't applied anymore because site.vm hasn't been adjusted
> for. Either go back to 2.2 or update site.vm accordingly.
> One example is li.divider, class is not applied due to changes. See attached
> screenshots. I guess there are more cases, this is one I have found on the
> first sight.
> At least for the given example it might be a bug in Bootstrap 2.3.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320786#comment-320786 ] Simone Tripodi commented on MSKINS-80: -- Thanks a lot for digging in that issue Michael, much more than appreciated! That is why anyway nobody cut and open a votes for a new fluido release. So, I'd propose to not taking an action for that issue and wait for next bootstrap release, before releasing next bootstrap version - WDYT? > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320788#comment-320788 ] Michael Osipov commented on MSKINS-80: -- There no reason to wait. That was a deliberate change in code. You *must* use a span for the divider now. The issue was closed months ago and examples changed. We should go for 2.3.1 and inspect the diff for changes, adapt site.vm and go on. I am not firm with the site.vm in this skin so you should be able to spot changes way faster than me. > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320789#comment-320789 ] Simone Tripodi commented on MSKINS-80: -- OH looks like I misinterpreted the previous messages - thanks a lot for the clarifications, I am going to fix it! :) > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320790#comment-320790 ] Michael Osipov commented on MSKINS-80: -- Fine, waiting for code to test. I am curious whether you will able to find other changes in the CSS styles. > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320792#comment-320792 ] Robert Scholte commented on MSKINS-80: -- I did a small change for MSKINS-79 related to this. > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-81) Make dateFormat use default format from site.xml
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320793#comment-320793 ] Olivier Lamy commented on DOXIASITETOOLS-81: I miss you. I just take care of possible NPE when calling siteRenderingContext.getDecoration().getPublishDate().getFormat() > Make dateFormat use default format from site.xml > > > Key: DOXIASITETOOLS-81 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-81 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site renderer >Affects Versions: 1.3 >Reporter: Michael Osipov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: dateformat.patch > > > Make dateFormat use default format from site.xml/publishDate/@format rather > than dependending on the VM's locale. > This unifies the date format to a single, configurable place: site.xml > This issue depends on DOXIASITETOOLS-80 which contains further details and > advantages of this approach. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-80) Decoration model missing Version and PublishDate default values
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed DOXIASITETOOLS-80. -- Resolution: Fixed Fix Version/s: 1.4 Assignee: Olivier Lamy applied http://svn.apache.org/r1452051 Thanks! > Decoration model missing Version and PublishDate default values > --- > > Key: DOXIASITETOOLS-80 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-80 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Decoration model >Affects Versions: 1.3 >Reporter: Michael Osipov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: model.patch, model.patch > > > 1.Version and PublishDate elements define default values for their attributes > but those aren't fully reflected in the model. > 2. Default Version and PublishDate aren't created in order to access default > values. > I have patched the doxia-decoration-model accordingly. The patch is > suboptimal due to: MODELLO-270 > The benefit of this fix is that the aforementioned attributes are also set in > the site.vm templates of all skins. This change will allow us to remove all > default setters (e.g. #publishDate macro) in those templates and have them in > one single place: DecorationModel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-81) Make dateFormat use default format from site.xml
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed DOXIASITETOOLS-81. -- Resolution: Fixed > Make dateFormat use default format from site.xml > > > Key: DOXIASITETOOLS-81 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-81 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Site renderer >Affects Versions: 1.3 >Reporter: Michael Osipov >Assignee: Olivier Lamy > Fix For: 1.4 > > Attachments: dateformat.patch > > > Make dateFormat use default format from site.xml/publishDate/@format rather > than dependending on the VM's locale. > This unifies the date format to a single, configurable place: site.xml > This issue depends on DOXIASITETOOLS-80 which contains further details and > advantages of this approach. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-361) Improve linguistic style of bottom
[ https://jira.codehaus.org/browse/MJAVADOC-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MJAVADOC-361. -- Resolution: Fixed Fix Version/s: 2.9.1 Assignee: Herve Boutemy patch applied in [r1452079|http://svn.apache.org/r1452079] thank you > Improve linguistic style of bottom > -- > > Key: MJAVADOC-361 > URL: https://jira.codehaus.org/browse/MJAVADOC-361 > Project: Maven 2.x Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.9 >Reporter: Michael Osipov >Assignee: Herve Boutemy >Priority: Minor > Fix For: 2.9.1 > > Attachments: bottom.patch > > > The current default value of bottom does not adhere to the English language > style: > 1. A hyphen is used to denote the year ranges which is incorrect. An en dash > must be used, see [http://en.wikipedia.org/wiki/En_dash#Ranges_of_values > here]. > 2. "All Rights Reserved" includes unnecessary/incorrect capitalization. > An appropriate patch has been attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-81) Make dateFormat use default format from site.xml
[
https://jira.codehaus.org/browse/DOXIASITETOOLS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321325#comment-321325
]
Michael Osipov commented on DOXIASITETOOLS-81:
--
Olivier, we can do better. You have fixed DOXIASITETOOLS-80. We know now that
decoration and publishDate are always populated. Therefore format is always
safe. getPublishDate return a new object when the internal is null. If you
really want to double-check for null which should happen anymore, if that case
I would rather do {{new SDF ( new PublishDate().getFormat() )}} instead of
using the doc locale.
Correct me if I am wrong!
> Make dateFormat use default format from site.xml
>
>
> Key: DOXIASITETOOLS-81
> URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-81
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 1.3
>Reporter: Michael Osipov
>Assignee: Olivier Lamy
> Fix For: 1.4
>
> Attachments: dateformat.patch
>
>
> Make dateFormat use default format from site.xml/publishDate/@format rather
> than dependending on the VM's locale.
> This unifies the date format to a single, configurable place: site.xml
> This issue depends on DOXIASITETOOLS-80 which contains further details and
> advantages of this approach.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-80) Upgrade to Bootstrap 2.3 breaks design
[ https://jira.codehaus.org/browse/MSKINS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321327#comment-321327 ] Michael Osipov commented on MSKINS-80: -- Robert, unfortunately MSKINS-79 doesn't do in this case. > Upgrade to Bootstrap 2.3 breaks design > -- > > Key: MSKINS-80 > URL: https://jira.codehaus.org/browse/MSKINS-80 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.3.1 >Reporter: Michael Osipov > Attachments: bootstrap 2.2.png, bootstrap-2.2-to-2.3.patch, bootstrap > 2.3.png > > > Tried 1.3.1-SNAPSHOT from trunk. Bootstrap 2.3 is so different from 2.2 that > many CSS styles aren't applied anymore because site.vm hasn't been adjusted > for. Either go back to 2.2 or update site.vm accordingly. > One example is li.divider, class is not applied due to changes. See attached > screenshots. I guess there are more cases, this is one I have found on the > first sight. > At least for the given example it might be a bug in Bootstrap 2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-224) Exclude any goals
[ https://jira.codehaus.org/browse/MPLUGIN-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321329#comment-321329 ] Robert Scholte commented on MPLUGIN-224: There's no such thing as internal goals. I'm pretty sure that such construction is not required and can be resolved with good refactoring. Move the business logic to a separate class and call those methods from the main-goals. > Exclude any goals > - > > Key: MPLUGIN-224 > URL: https://jira.codehaus.org/browse/MPLUGIN-224 > Project: Maven 2.x Plugin Tools > Issue Type: New Feature >Affects Versions: 3.1 >Reporter: Lefebvre JF > > Can you please add a way to exclude any goals for the report generation, > idealy by annotation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-224) Exclude any goals
[ https://jira.codehaus.org/browse/MPLUGIN-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321330#comment-321330 ] Lefebvre JF commented on MPLUGIN-224: - To make sûre Delivery the same packaging for all project, we have develop a complexe mojo wich generate à site with custom reports, generate javadoc, copy jar and war into spécific dirs ... Un our plugin, custom reports, for example must not be visible > Exclude any goals > - > > Key: MPLUGIN-224 > URL: https://jira.codehaus.org/browse/MPLUGIN-224 > Project: Maven 2.x Plugin Tools > Issue Type: New Feature >Affects Versions: 3.1 >Reporter: Lefebvre JF > > Can you please add a way to exclude any goals for the report generation, > idealy by annotation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5444) ModelSource API is not sufficient to resolve project hierachies
Igor Fedorenko created MNG-5444: --- Summary: ModelSource API is not sufficient to resolve project hierachies Key: MNG-5444 URL: https://jira.codehaus.org/browse/MNG-5444 Project: Maven 2 & 3 Issue Type: Bug Components: Embedding Affects Versions: 3.0.4 Reporter: Igor Fedorenko ModelSource API does not allow loading of parent POM from explicit or implicit . This effectively means the API cannot be used to load multimodule projects from non-filesystem backing store (git database, in my case). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5444) ModelSource API is not sufficient to resolve project hierachies
[ https://jira.codehaus.org/browse/MNG-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-5444. --- Resolution: Fixed Fix Version/s: 3.1.0 Implemented in master https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=9b58a3cfdccd4f7998f3f1d39a8687858248f76d > ModelSource API is not sufficient to resolve project hierachies > --- > > Key: MNG-5444 > URL: https://jira.codehaus.org/browse/MNG-5444 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Embedding >Affects Versions: 3.0.4 >Reporter: Igor Fedorenko > Fix For: 3.1.0 > > > ModelSource API does not allow loading of parent POM from explicit or > implicit . This effectively means the API cannot be used to > load multimodule projects from non-filesystem backing store (git database, in > my case). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-79) APT document with verbatim section including C #include causes NPE
[
https://jira.codehaus.org/browse/DOXIASITETOOLS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321340#comment-321340
]
Lukas Theussl commented on DOXIASITETOOLS-79:
-
Thanks! :)
> APT document with verbatim section including C #include causes NPE
> --
>
> Key: DOXIASITETOOLS-79
> URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-79
> Project: Maven Doxia Sitetools
> Issue Type: Bug
>Reporter: Andy Isaacson
>Assignee: Lukas Theussl
> Fix For: 1.4
>
> Attachments: mtest.tar.gz
>
>
> A simple apt.vm document including a C program fragment in a verbatim section
> causes "mvn site" to fail with a NPE. The failure can be worked around by
> escaping the # as backslash-# but the requirement to do this is not
> documented, nor AFAICS is the feature of supporting #include in verbatim
> sections.
> Attaching a complete testcase mtest.tar.gz.
> {noformat}
> % cat src/site/apt/hello.vm
>
>#include "stdio.h"
>int main(void) { printf("hello, world!\n"); return 0; }
>
> % mvn --version
> Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.6.6", arch: "amd64", family: "unix"
> % mvn site
> ...
> [WARNING] No project URL defined - decoration links will not be relativized!
> [INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
> skin.
> [ERROR] Parser Exception: /tmp/mtest/src/site/apt/hello.apt.vm
> [ERROR] org.apache.velocity.runtime.parser.ParseException: Encountered
> "\"stdio.h\"" at line 2, column 13.
> Was expecting:
> "(" ...
>
> at
> org.apache.velocity.runtime.parser.Parser.generateParseException(Parser.java:3360)
> at
> org.apache.velocity.runtime.parser.Parser.jj_consume_token(Parser.java:3237)
> ...
> [ERROR] ResourceManager.getResource() parse exception
> [ERROR] org.apache.velocity.exception.ParseErrorException: Encountered
> "\"stdio.h\"" at line 2, column 13 of /tmp/mtest/src/site/apt/hello.apt.vm
> Was expecting:
> "(" ...
>
> at org.apache.velocity.Template.process(Template.java:137)
> at
> org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:415)
> at
> org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:335)
> at
> org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1102)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:498)
> ...
> [ERROR] Error parsing /tmp/mtest/src/site/apt/hello.apt.vm as a velocity
> template, using as text.
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.798s
> [INFO] Finished at: Fri Jan 18 12:51:17 PST 2013
> [INFO] Final Memory: 11M/153M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on project
> mtest: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed.
> NullPointerException -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
