maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAVADOC-445) JavadocOptionsXpp3Reader doesn't deserialize the placement element in Tag
Date Sat, 01 Dec 2018 16:17:00 GMT

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

Hudson commented on MJAVADOC-445:
---------------------------------

Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » master #83

See https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/83/

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

Mime
View raw message