You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2012/09/29 02:27:36 UTC

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

Herve Boutemy created MJAVADOC-354:
--------------------------------------

             Summary: isValidJavadocLink is too strict: doesn't support unnamed package
                 Key: MJAVADOC-354
                 URL: https://jira.codehaus.org/browse/MJAVADOC-354
             Project: Maven 2.x Javadoc Plugin
          Issue Type: Bug
    Affects Versions: 2.8
            Reporter: Herve Boutemy


see http://mail-archives.apache.org/mod_mbox/maven-dev/201209.mbox/%3C50661F5A.5050302@apache.org%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... :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MJAVADOC-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy closed MJAVADOC-354.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9.1
         Assignee: Herve Boutemy

fixed in [r1391706|http://svn.apache.org/viewvc?rev=1391706&view=rev]
                
> isValidJavadocLink is too strict: doesn't support unnamed package
> -----------------------------------------------------------------
>
>                 Key: MJAVADOC-354
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-354
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.8
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>             Fix For: 2.9.1
>
>
> see http://mail-archives.apache.org/mod_mbox/maven-dev/201209.mbox/%3C50661F5A.5050302@apache.org%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... :)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira