A bug sneaked in...

I think Till just pushed a fix for that, so if you pull now, it should work
again...



On Fri, May 29, 2015 at 10:28 AM, Chiwan Park <chiwanp...@icloud.com> wrote:

> Hi :)
>
> I tried building current master branch with `mvn clean package
> -DskipTests` command.
> But I got a error following:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 08:11 min
> [INFO] Finished at: 2015-05-29T17:21:45+09:00
> [INFO] Final Memory: 151M/1524M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs)
> on project flink-scala-shell: MavenReportException: Error while creating
> archive:
> [ERROR] Exit code: 1 - javadoc: warning - No source files for package
> org.apache.flink.api.java
> [ERROR] javadoc: warning - No source files for package
> org.apache.flink.api.java
> [ERROR] javadoc: error - No public or protected classes found to document.
> [ERROR]
> [ERROR] Command line was:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin/javadoc
> @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> '/Users/chiwanpark/IdeaProjects/flink/flink-staging/flink-scala-shell/target/apidocs'
> dir.
> [ERROR] -> [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 :flink-scala-shell
>
> I ran the command in OS X 10.10.3, Oracle JDK 1.8.0_45, Maven 3.3.1.
> How can I solve this problem?
>
>
> Regards,
> Chiwan Park
>
>
>
>

Reply via email to