[
https://issues.apache.org/jira/browse/YETUS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660715#comment-16660715
]
Sean Busbey commented on YETUS-15:
----------------------------------
Failure to build site on clean checkout:
{code}
$ mvn site install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Yetus Project [pom]
[INFO] Apache Yetus - MiniMaven Plugin [maven-plugin]
[INFO] Apache Yetus - Assemblies [jar]
[INFO] Apache Yetus - Audience Annotations [jar]
[INFO] Apache Yetus - Audience Annotations JDiff Doclet [jar]
[INFO] Apache Yetus - Audience Annotations Component [pom]
[INFO] Apache Yetus - Precommit [pom]
[INFO] Apache Yetus - releasedocmaker [jar]
[INFO] Apache Yetus - shelldocs [jar]
[INFO] Apache Yetus - Website/Documentation [pom]
[INFO] Apache Yetus - Distribution [pom]
[INFO] Apache Yetus - Maven Plugin [maven-plugin]
[INFO]
[INFO] -------------------< org.apache.yetus:yetus-project >-------------------
[INFO] Building Apache Yetus Project 0.9.0-SNAPSHOT [1/12]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-site-plugin:3.5.1:site (default-site) @ yetus-project ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.9
[INFO] configuring report plugin
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Yetus Project 0.9.0-SNAPSHOT ................ FAILURE [ 6.823 s]
[INFO] Apache Yetus - MiniMaven Plugin .................... SKIPPED
[INFO] Apache Yetus - Assemblies .......................... SKIPPED
[INFO] Apache Yetus - Audience Annotations ................ SKIPPED
[INFO] Apache Yetus - Audience Annotations JDiff Doclet ... SKIPPED
[INFO] Apache Yetus - Audience Annotations Component ...... SKIPPED
[INFO] Apache Yetus - Precommit ........................... SKIPPED
[INFO] Apache Yetus - releasedocmaker ..................... SKIPPED
[INFO] Apache Yetus - shelldocs ........................... SKIPPED
[INFO] Apache Yetus - Website/Documentation ............... SKIPPED
[INFO] Apache Yetus - Distribution ........................ SKIPPED
[INFO] Apache Yetus - Maven Plugin 0.9.0-SNAPSHOT ......... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.196 s
[INFO] Finished at: 2018-10-23T08:28:46-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project
yetus-project: failed to get report for
org.apache.maven.plugins:maven-javadoc-plugin: Plugin
org.apache.yetus:yetus-minimaven-plugin:0.9.0-SNAPSHOT or one of its
dependencies could not be resolved: Could not find artifact
org.apache.yetus:yetus-minimaven-plugin:jar:0.9.0-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{code}
We either need to fix the pom ordering so that you can do a site build from a
clean checkout and local repository (preferred) or we need to update the site
building instructions to call out that we have some hacky thing you have to do
(like an install prior to doing a site build).
The specific problem here is that our top level pom's reporting refers to
reactor modules that haven't been built yet. The maven way to fix this would be
to put an intermediary between the top level pom and those submodules that need
to be included in the reporting. e.g.
{code}
- pom
\
|
|- module-needed-in-reporting
|
- reported-on-stuff <-- maven reporting section here
\
|- leaf module
|- leaf module
{code}
What are we trying to cover in the aggregate javadocs? can we rearrange the
inter module dependencies to remove the current loop?
> build environment
> -----------------
>
> Key: YETUS-15
> URL: https://issues.apache.org/jira/browse/YETUS-15
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Affects Versions: 0.1.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: HADOOP-12137.HADOOP-12111.00.patch,
> HADOOP-12137.HADOOP-12111.01.patch, YETUS-15.000.patch, YETUS-15.002.patch,
> YETUS-15.004.patch, YETUS-15.005.patch, YETUS-15.006.patch,
> YETUS-15.007.patch, YETUS-15.008.patch, YETUS-15.009.patch,
> YETUS-15.03.patch, YETUS-15.ea-maven-001.patch
>
>
> We need to have some way to build (esp the documentation!) and unit tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
