[ 
https://jira.codehaus.org/browse/MJAVADOC-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roberto Andrade updated MJAVADOC-391:
-------------------------------------

    Description: 
I just learned by looking at the plugin's source code that the 
{{excludePackageNames}} configuration only works if I specify a {{sourcepath}} 
configuration but could not find that documented anywhere.

I was assuming (perhaps incorrectly) that my project's source folders would be 
considered by default as the value of {{sourcepath}} given when I run the 
plugin without exclusions it actually finds the source in the right place to be 
able to generate the javadoc (more specifically, I was assuming the default 
value of it to be the same as {{project.build.sourceDirectory}}).

  was:
I just learned by looking at the plugin's source code that the 
{{excludePackageNames}} configuration only works if I specify a {{sourcepath}} 
configuration but could not find that documented anywhere.

I was assuming (perhaps incorrectly) that my project's source folders would be 
considered by default as the value of {{sourcepath}} given when I run the 
plugin without exclusions it actually finds the source in the right place to be 
able to generate the javadoc.


> excludePackageNames doesn't work if source path is not specified
> ----------------------------------------------------------------
>
>                 Key: MJAVADOC-391
>                 URL: https://jira.codehaus.org/browse/MJAVADOC-391
>             Project: Maven Javadoc Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.9.1
>         Environment: OSX 10.9, Maven 3.1
>            Reporter: Roberto Andrade
>
> I just learned by looking at the plugin's source code that the 
> {{excludePackageNames}} configuration only works if I specify a 
> {{sourcepath}} configuration but could not find that documented anywhere.
> I was assuming (perhaps incorrectly) that my project's source folders would 
> be considered by default as the value of {{sourcepath}} given when I run the 
> plugin without exclusions it actually finds the source in the right place to 
> be able to generate the javadoc (more specifically, I was assuming the 
> default value of it to be the same as {{project.build.sourceDirectory}}).



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to