You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/12/01 15:58:00 UTC
[jira] [Closed] (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:all-tabpanel ]
Robert Scholte closed MJAVADOC-445.
-----------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Fix Version/s: 3.0.2
Fixed in [85729d5640875380b1f7dfb58dc64d04219354c0|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commit;h=85729d5640875380b1f7dfb58dc64d04219354c0]
Thanks for the patch!
> 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
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0.2
>
> Attachments: MJavadoc445Test.java, 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
(v7.6.3#76005)