You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jean CADOT (JIRA)" <ji...@apache.org> on 2016/02/26 13:32:18 UTC

[jira] [Comment Edited] (MJAVADOC-445) JavadocOptionsXpp3Reader doesn't deserialize the placement element in Tag

    [ https://issues.apache.org/jira/browse/MJAVADOC-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168899#comment-15168899 ] 

Jean CADOT edited comment on MJAVADOC-445 at 2/26/16 12:31 PM:
---------------------------------------------------------------

Attaching patch to apply from the project root: maven-javadoc-plugin folder.


was (Author: jeancadot):
Attaching patch to apply from the project root :maven-javadoc-plugin folder.

> JavadocOptionsXpp3Reader doesn't deserialize the placement element in Tag
> -------------------------------------------------------------------------
>
>                 Key: MJAVADOC-445
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-445
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.10.3
>            Reporter: Jean CADOT
>         Attachments: javadocOptions.mdo, javadocOptions.mdo.patch
>
>
> The generated class JavadocOptionsXpp3Reader doesn't deserialize the placement in the generated Tag class. 
> The end result is that in some cases custom tags are not replaced in the produced java documentation.
> In order to fix the issue you have to change the placement declaration in the Tag class in the model description (javadocOptions.mdo). 
> A modified version containing the fix has been attached to this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)