You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anton Klarén (JIRA)" <ji...@apache.org> on 2017/09/22 13:01:00 UTC
[jira] [Updated] (MJAVADOC-497) javadoc:aggregate ignores
excludePackageNames
[ https://issues.apache.org/jira/browse/MJAVADOC-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Klarén updated MJAVADOC-497:
----------------------------------
Description:
When running {{javadoc:aggregate}} and specifying {{subpackages}} and {{excludePackageNames}}, {{excludePackageNames}} is completely ignored.
According to the code, {{excludePackageNames}} is only considered when {{sourcepath}} is set. This is however not applicable to an aggregated project, or it might but I'm not seeing it. What happens in the code is that {{sourcepath}} is derived from the found sources during aggregation, unfortunately, this happens after the excluded packages have been calculated.
I have a patch for this that will be linked as soon as I have the issue number.
was:
When running {{javadoc:aggregate}} and specifying {{subpackage}} and {{excludePackageNames}}, {{excludePackageNames}} is completely ignored.
According to the code, {{excludePackageNames}} is only considered when {{sourcepath}} is set. This is however not applicable to an aggregated project, or it might but I'm not seeing it. What happens in the code is that {{sourcepath}} is derived from the found sources during aggregation, unfortunately, this happens after the excluded packages have been calculated.
I have a patch for this that will be linked as soon as I have the issue number.
> javadoc:aggregate ignores excludePackageNames
> ---------------------------------------------
>
> Key: MJAVADOC-497
> URL: https://issues.apache.org/jira/browse/MJAVADOC-497
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.0.0-M1
> Reporter: Anton Klarén
>
> When running {{javadoc:aggregate}} and specifying {{subpackages}} and {{excludePackageNames}}, {{excludePackageNames}} is completely ignored.
> According to the code, {{excludePackageNames}} is only considered when {{sourcepath}} is set. This is however not applicable to an aggregated project, or it might but I'm not seeing it. What happens in the code is that {{sourcepath}} is derived from the found sources during aggregation, unfortunately, this happens after the excluded packages have been calculated.
> I have a patch for this that will be linked as soon as I have the issue number.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)