Oh, that's my problem.  I was looking in MPJAVADOC instead of MJAVADOC.
That's kind of confusing.  The MPJAVADOC project should probably get
renamed to clearly state it's the Maven 1 plugin (MJAVADOC is clear in
its title).

I found the bug I filed with its accompanying patch.  It's
http://jira.codehaus.org/browse/MJAVADOC-27. (and it's not marked fixed)

..David.. 


-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 09, 2006 3:38 PM
To: Maven Users List
Subject: Re: [M2] - maven-javadoc-plugin showPrivate bug

http://jira.codehaus.org/browse/MJAVADOC-37 ?

On 1/10/06, David Jackman <[EMAIL PROTECTED]> wrote:
> I reported this problem earlier and included a patch.  That was before

> they had separate JIRA projects for the plugins, so I can't find the 
> issue now.  I did see MPJAVADOC-37, which is marked as fixed.
>
> ..David..
>
>
> -----Original Message-----
> From: Tim Davies [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 09, 2006 8:32 AM
> To: Maven Users List
> Subject: [M2] - maven-javadoc-plugin showPrivate bug
>
> Ive just set up a pom using the maven-javadoc-plugin and want to 
> include the configuration option "showPrivate".
>
> If I simply add the tag like this,
>
>            <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-javadoc-plugin</artifactId>
>                 <configuration>
>                     <showPrivate>true</showPrivate>
>                 </configuration>
>             </plugin>
>
> the build fails with an error, "Embedded error: Exit code: 1 -
javadoc:
> More than one of -public, -private, -package, or -protected
specified".
> So I checked the doco and it says that the default is showPackage is 
> true. So If I now use:
>
>             <plugin>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-javadoc-plugin</artifactId>
>                 <configuration>
>                     <showPackage>false</showPackage>
>                     <showPrivate>true</showPrivate>
>                 </configuration>
>             </plugin>
>
> It works fine.
>
> So this isnt a particularly tricky workaround but not very elegant. 
> Just thought Id ask around before I submit it as a bug.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to