[ 
https://issues.apache.org/jira/browse/HBASE-27992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Somogyi resolved HBASE-27992.
-----------------------------------
    Fix Version/s: 2.6.0
                   2.4.18
                   2.5.6
                   3.0.0-beta-1
                   4.0.0-alpha-1
       Resolution: Fixed

Merged to branch-2.4+. Thanks for the review [~zhangduo]!

> Bump exec-maven-plugin to 3.1.0
> -------------------------------
>
>                 Key: HBASE-27992
>                 URL: https://issues.apache.org/jira/browse/HBASE-27992
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: Peter Somogyi
>            Assignee: Peter Somogyi
>            Priority: Trivial
>             Fix For: 2.6.0, 2.4.18, 2.5.6, 3.0.0-beta-1, 4.0.0-alpha-1
>
>
> I frequently see IOException in hbase-shaded-with-hadoop-check-invariants 
> make-sure-validation-files-are-in-sync phase. I'm not sure what is the root 
> cause but it worth to bump the plugin version to the latest.
> {noformat}
> [INFO] --- exec-maven-plugin:1.6.0:exec 
> (make-sure-validation-files-are-in-sync) @ 
> hbase-shaded-with-hadoop-check-invariants ---
> [ERROR] Command execution failed.
> java.io.IOException: Stream closed
>     at java.lang.ProcessBuilder$NullOutputStream.write 
> (ProcessBuilder.java:433)
>     at java.io.OutputStream.write (OutputStream.java:116)
>     at java.io.BufferedOutputStream.flushBuffer (BufferedOutputStream.java:82)
>     at java.io.BufferedOutputStream.flush (BufferedOutputStream.java:140)
>     at java.io.FilterOutputStream.close (FilterOutputStream.java:158)
>     at org.apache.commons.exec.DefaultExecutor.closeProcessStreams 
> (DefaultExecutor.java:306)
>     at org.apache.commons.exec.DefaultExecutor.executeInternal 
> (DefaultExecutor.java:387)
>     at org.apache.commons.exec.DefaultExecutor.execute 
> (DefaultExecutor.java:166)
>     at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804)
>     at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751)
>     at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:210)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:156)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:148)
>     at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
>  (MultiThreadedBuilder.java:190)
>     at 
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
>  (MultiThreadedBuilder.java:186)
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>     at java.util.concurrent.Executors$RunnableAdapter.call 
> (Executors.java:511)
>     at java.util.concurrent.FutureTask.run (FutureTask.java:266)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker 
> (ThreadPoolExecutor.java:1149)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run 
> (ThreadPoolExecutor.java:624)
>     at java.lang.Thread.run (Thread.java:748)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to