[
https://issues.apache.org/jira/browse/MJAVADOC-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786484#comment-16786484
]
Thomas Mortagne edited comment on MJAVADOC-584 at 3/7/19 7:51 AM:
------------------------------------------------------------------
{quote}
a wildcard at the beginning should match 1 or more folders
any other wildcard must match exactly one folder
{quote}
Does it means it not possible anymore to match any number of subpackages ? Like
excluding everything under {{com.mycompany.myapp.package3}} in the example.
was (Author: tmortagne):
{quote}
a wildcard at the beginning should match 1 or more folders
any other wildcard must match exactly one folder
{quote}
Does it means it not possible anymore to match any number of sumpackages ? Like
excluding everything under {{com.mycompany.myapp.package3}} in the example.
> excludePackageNames is not working as documented anymore
> --------------------------------------------------------
>
> Key: MJAVADOC-584
> URL: https://issues.apache.org/jira/browse/MJAVADOC-584
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Thomas Mortagne
> Priority: Minor
>
> We have the following configuration at XWiki:
> https://github.com/xwiki/xwiki-commons/blob/xwiki-commons-11.1/pom.xml#L1946.
> We don't want to produce javadoc for internal packages. This is very similar
> to the example given on
> https://maven.apache.org/plugins/maven-javadoc-plugin/examples/exclude-package-names.html.
> When I upgrade to 3.1.0 the exclude is not taken into account anymore (I get
> error related to classes located in internal packages). For example:
> {noformat}
> /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-commons_master/xwiki-commons-core/xwiki-commons-extension/xwiki-commons-extension-api/src/main/java/org/xwiki/extension/version/internal/DefaultVersionConstraint.java:49:
> error: reference not found
> * @see org.sonatype.aether.util.version.GenericVersionConstraint
> {noformat}
> I noticed MJAVADOC-548 but since the documentation did not changed I assumed
> my use case was still OK.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)