Thanks :)

Regards,
Chiwan Park

> On May 29, 2015, at 10:05 PM, Márton Balassi <balassi.mar...@gmail.com> wrote:
> 
> Thanks, Max.
> 
> On Fri, May 29, 2015 at 3:04 PM, Maximilian Michels <m...@apache.org 
> <mailto:m...@apache.org>> wrote:
> Fixed it on the master.
> 
> Problem were some classes belonging to package "org.apache.flink.api.java" 
> were in the folder "src/main/java/org.apache.flink/api/java/" instead of 
> "src/main/java/org/apache/flink/api/java/".
> 
> On Fri, May 29, 2015 at 2:04 PM, Maximilian Michels <m...@apache.org 
> <mailto:m...@apache.org>> wrote:
> Yes, clearly this is related to the merge of the scala shell.
> 
> On Fri, May 29, 2015 at 12:17 PM, Ufuk Celebi <u...@apache.org 
> <mailto:u...@apache.org>> wrote:
> I think it is unrelated to Till's fix, no? It's a different issue.
> 
> Does Travis *not* detect this because of the caches?
> 
> On Fri, May 29, 2015 at 12:03 PM, Maximilian Michels <m...@apache.org 
> <mailto:m...@apache.org>> wrote:
> I can confirm that "mvn clean package" fails. However, Travis builds fine 
> after Till's fix: https://travis-ci.org/apache/flink/builds/64537794 
> <https://travis-ci.org/apache/flink/builds/64537794>
> 
> On Fri, May 29, 2015 at 11:51 AM, Till Rohrmann <trohrm...@apache.org 
> <mailto:trohrm...@apache.org>> wrote:
> Yes, this is another error. Seems to be related to the new scala shell.
> 
> On Fri, May 29, 2015 at 11:00 AM, Chiwan Park <chiwanp...@icloud.com 
> <mailto:chiwanp...@icloud.com>> wrote:
> I fetched master branch and ran again. But I got the same error.
> It seems that the problem is related to javadoc. Till’s fix is related to 
> renaming in flink-ml package.
> 
> Regards,
> Chiwan Park
> 
> 
>> On May 29, 2015, at 5:39 PM, Stephan Ewen <se...@apache.org 
>> <mailto:se...@apache.org>> wrote:
>> 
>> 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 
>> <mailto: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 
>> <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