Skip to content
Skip to breadcrumbs
Skip to header menu
Skip to action menu
Skip to quick search
Quick Search
Browse
Pages
Blog
Labels
Attachments
Mail
Advanced
What’s New
Space Directory
Feed Builder
Keyboard Shortcuts
Confluence Gadgets
Log In
Dashboard
Maven User
Copy Page
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account. You can also
Sign Up
for a new account.
This page is being edited by
.
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
More colours
Strikethrough
Subscript
Superscript
Monospace
Clear Formatting
Bullet list
Numbered list
Outdent
Indent
Align left
Align center
Align right
Link
Table
Insert
Insert Content
Image
Link
Attachment
Symbol
Emoticon
Wiki Markup
Horizontal rule
tinymce.confluence.insert_menu.macro_desc
Info
JIRA Issue
Status
Gallery
Tasklist
Table of Contents
Other Macros
Page Layout
No Layout
Two column (simple)
Two column (simple, left sidebar)
Two column (simple, right sidebar)
Three column (simple)
Two column
Two column (left sidebar)
Two column (right sidebar)
Three column
Three column (left and right sidebars)
Undo
Redo
Find/Replace
Keyboard Shortcuts Help
<p>The following example shows how to generate two sets of Javadoc into different directories. The first set of code is in src/main/java/pkg1 and the second is in src/main/java/pkg2. Running "mvn site" creates the two sets of doc in target/site. This does not seem to be documented explicitly anywhere else.</p> <p>There appears to be no way to explicitly specify the packages passed to the underlying javadoc tool, however, the subpackages can be specified. When specifying subpackages, all the packages under those named are included. Specific packages can be excluded from the report using <excludePackageNames> in the configuration.</p> <p>By uncommenting the line with test-javadoc, the javadoc for the test source can generated similarly.</p> <p>Note that the id element under reportSet is critical. Without it, only one set of documentation will be generated. The reporting plugin may be using the id as a key into a map or similar. </p> <table class="wysiwyg-macro" data-macro-name="noformat" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e25vZm9ybWF0fQ&locale=en_GB&version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre> <reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <reportSets> <reportSet> <id>package-1</id> <configuration> <subpackages>pkg1</subpackages> <name>Javadoc for Package 1</name> <destDir>apidoc-package1</destDir> <windowtitle>Package 1 API Documentation</windowtitle> </configuration> <reports> <report>javadoc</report> </reports> </reportSet> <reportSet> <id>package-2</id> <configuration> <subpackages>pkg2</subpackages> <name>Javadoc for Package 2</name> <destDir>apidoc-package2</destDir> <windowtitle>Package 2 API Documentation</windowtitle> </configuration> <reports> <report>javadoc</report> <!-- <report>test-javadoc</report> --> </reports> </reportSet> </reportSets> </plugin> </plugins> </reporting> </pre></td></tr></table>
Please type the word appearing in the picture.
Attachments
Labels
Location
Watch this page
< Edit
Preview >
Loading…
Save
Cancel
Next hint
search
attachments
weblink
advanced