[ http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185717#action_185717 ]
Vincent Siveton commented on MJAVADOC-249: ------------------------------------------ Why do you want to add them by default in your existing Javadoc? Formatting reasons? Unify goal behaviours? Using or not <p/> has the same behaviour... and I don't think fix goal needs to modify the original javadoc. Having /* @inheritDoc */ in one line is the formatting exception in the mojo. It is common in modern projects and reduces code size. > javadoc:fix should wrap existing comments in <p></p> > ---------------------------------------------------- > > Key: MJAVADOC-249 > URL: http://jira.codehaus.org/browse/MJAVADOC-249 > Project: Maven 2.x Javadoc Plugin > Issue Type: New Feature > Affects Versions: 2.6 > Reporter: jieryn > > When I run the javadoc:fix mojo, freshly generated comments are wrapped > inside <p> </p> tags. However, comments which existed prior to the run are > not wrapped in such tags, even when they do not exist. This mojo does more > than just add missing javadoc comments, but also tries to fix them up (for > example, /**\n* {...@inheritdoc}\n*/ gets transformed to /** {...@inheritdoc} > */ ... which sets the precedent that the mojo is at least open to the idea of > fixing existing comments. > Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira