Thanks, I want to build full tarball with site doc. So I modified my script three build steps. The build was a success.
________________________________________ 보낸 사람: Stack <st...@duboce.net> 보낸 날짜: 2019년 7월 16일 화요일 00:48 받는 사람: Hbase-User 제목: Re: Failed to create assembly On Mon, Jul 15, 2019 at 2:31 AM Kang Minwoo <minwoo.k...@outlook.com> wrote: > Hello Users, > > I try to build HBase 2.1.5 but I got a failure on Apache HBase - Assembly > Project. > Error Message is below. > > --- > [INFO] Apache HBase - External Block Cache ................ SUCCESS [ > 1.750 s] > [INFO] Apache HBase - Assembly ............................ FAILURE [ > 11.643 s] > [INFO] Apache HBase Shaded Packaging Invariants ........... SKIPPED > [INFO] Apache HBase Shaded Packaging Invariants (with Hadoop bundled) > SKIPPED > [INFO] Apache HBase - Archetypes .......................... SKIPPED > [INFO] Apache HBase - Exemplar for hbase-client archetype . SKIPPED > [INFO] Apache HBase - Exemplar for hbase-shaded-client archetype SKIPPED > [INFO] Apache HBase - Archetype builder ................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 15:13 min > [INFO] Finished at: 2019-07-15T18:20:54+09:00 > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single (default-cli) > on project hbase-assembly: Failed to create assembly: Error adding file > 'org.apache.hbase:hbase-common:test-jar:tests:2.1.5' to archive: > /ws/hbase-2.1.5-src/hbase-common/target/test-classes isn't a file. -> [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 > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <goals> -rf :hbase-assembly > --- > > I didn't know why the assembly plugin tries to add > 'hbase-common/target/test-classes'. > I didn’t know what was wrong. > > Best regards, > Minwoo Kang > What Wellington said but if you want to build full tarball with site doc, it is a little messy. I've seen the complaint about a dir not being a file in the past. Currently release builds does this from master branch dev-support/create-release/release-build.sh -- i.e. creates the artifact in three build steps: # Three invocations of maven. This seems to work. One to # populate the repo, another to build the site, and then # a third to assemble the binary artifact. Trying to do # all in the one invocation fails; a problem in our # assembly spec to in maven. TODO. Meantime, three invocations. MAVEN_OPTS="${MAVEN_OPTS}" ${MVN} --settings $tmp_settings \ clean install -DskipTests \ -Dmaven.repo.local=${tmp_repo} MAVEN_OPTS="${MAVEN_OPTS}" ${MVN} --settings $tmp_settings \ site -DskipTests \ -Dmaven.repo.local=${tmp_repo} MAVEN_OPTS="${MAVEN_OPTS}" ${MVN} --settings $tmp_settings \ install assembly:single -DskipTests \ -Dcheckstyle.skip=true ${PUBLISH_PROFILES} \ -Dmaven.repo.local=${tmp_repo} Need to spend the time to make the build more efficient but meantime the mess is contained by the scripts in dev-support/create-release. S
