[MJAVADOC-354] isValidJavadocLink is too strict: doesn't support unnamed package

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8
• Fix Version/s: 2.9.1
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 28/Sep/12 19:27
• Updated: 06/Apr/15 00:41
• Resolved: 28/Sep/12 19:46

Description

see http://mail-archives.apache.org/mod_mbox/maven-dev/201209.mbox/[e-mail]%3E

because of MPLUGIN-227, we start to see such "unnamed" package in package-list

m-javadoc-p needs to be tolerant to this use case, which is valid but not supported by MJAVADOC-283

even if having code in unnamed package is either a bad practice or the result of a m-plugin-p bug...

Issue Links

• is related to: MPLUGIN-227 HelpMojo javadoc generated in "unnamed package"
• is related to: MJAVADOC-283 isValidJavadocLink should be more strict