Thanks for investigating this, Robert!
On Tue, May 19, 2015 at 10:08 PM, Robert Metzger
wrote:
> Okay .. it seems that maven is downloading the flink-compiler artifacts
> from a snapshots repository:
>
> [INFO]
>
> [INFO] B
Okay .. it seems that maven is downloading the flink-compiler artifacts
from a snapshots repository:
[INFO]
[INFO] Building flink-language-binding-generic 0.9-SNAPSHOT
[INFO] --
Probably all Flink dev's have the "flink-compiler" jar in their local ".m2"
directory.
Also on travis, we are caching the ".m2" directory to improve build times.
Maybe it would make sense to disable that on travis to detect those issues
in the future.
I'll try it out to see how it affects the build
Yes, those should definitely be renamed.
It is amazing that maven actually compiles this. I am a bit puzzled there...
On Tue, May 19, 2015 at 9:09 PM, Alexander Alexandrov <
alexander.s.alexand...@gmail.com> wrote:
> I think that these two should be renamed to flink-optimizer, no?
>
> ./flink-st
I think that these two should be renamed to flink-optimizer, no?
./flink-staging/flink-language-binding/flink-python/pom.xml:
flink-compiler
./flink-staging/flink-language-binding/flink-language-binding-generic/pom.xml:
flink-compiler
2015-05-19 21:07 GMT+02:00 Alexander Alexandrov <
alexander.s.
I had a different issue related to the fact that
flink-language-binding-generic was not able to find (a potentially
outdated) flink-compiler dependency. I had to wipe out the local flink
artifacts from my .m2/repository to make this work.
2015-05-19 18:06 GMT+02:00 Robert Metzger :
> We could act
We could actually add a check into the tools/qa-check.sh script. That way
we'll see at least a warning in pull requests introducing too long lines.
On Tue, May 19, 2015 at 6:03 PM, Stephan Ewen wrote:
> Chiwan proposed a good workaround.
>
> I think that, as a long term fix, we should rewrite th
Chiwan proposed a good workaround.
I think that, as a long term fix, we should rewrite the code a bit such
that it does not generate such long names.
On Tue, May 19, 2015 at 5:37 PM, Chiwan Park wrote:
> Hi.
>
> I think that you are building in encrypted file system such as ecryptfs.
> Some e
Hi.
I think that you are building in encrypted file system such as ecryptfs.
Some encrypted file systems do not support long file name, but scala classes
have long file name frequently.
You can choose two options to solve this problem.
1. Build in non-encrypted file system.
2. Add `-Xmax-classf
