Re: Building only flink-java8 module

2017-06-02 Thread Aljoscha Krettek
Unfortunately I don’t know how to suppress running the tests in the dependency modules that are also built. > On 2. Jun 2017, at 11:44, Chesnay Schepler wrote: > > If all else fails, hard-code the scala versions into all poms. Simple text > search + replace. > > On 02.06.2017 11:30, Dawid Wys

Re: Building only flink-java8 module

2017-06-02 Thread Chesnay Schepler
If all else fails, hard-code the scala versions into all poms. Simple text search + replace. On 02.06.2017 11:30, Dawid Wysakowicz wrote: Unfortunately I had no luck with both of those approaches. The first one runs tests for all dependent modules, while the second one (which I already tried us

Re: Building only flink-java8 module

2017-06-02 Thread Dawid Wysakowicz
Unfortunately I had no luck with both of those approaches. The first one runs tests for all dependent modules, while the second one (which I already tried using fails with the provided error). Maybe some ideas how can I run/compiles tests using eclipse compiler from IntelliJ? I need to test lambdas

Re: Building only flink-java8 module

2017-06-01 Thread Dawid Wysakowicz
I tried the second approach before and it results in the error with scala.binary.version I attached, which is the same Ted got. I use it though for other modules and it works. I will try the first approach soon. Z pozdrowieniami! / Cheers! Dawid Wysakowicz *Data/Software Engineer* Skype: dawid

Re: Building only flink-java8 module

2017-06-01 Thread Ted Yu
That removes the error. However, looks like tests from other module(s) are run as well. Just an example: 16:12:53,103 INFO org.apache.flink.runtime.taskmanager.TaskManagerRegistrationTest - =

Re: Building only flink-java8 module

2017-06-01 Thread Aljoscha Krettek
Ah, I forgot that you also have to add “-Pjdk8” to activate the Java 8 profile. Otherwise the flink-java8 module will not be referenced in the main pom. > On 1. Jun 2017, at 17:42, Ted Yu wrote: > > When using the second approach (install followed by 'mvn verify'), I got > the following: > > [

Re: Building only flink-java8 module

2017-06-01 Thread Ted Yu
When using the second approach (install followed by 'mvn verify'), I got the following: [ERROR] Failed to execute goal on project flink-java8_2.10: Could not resolve dependencies for project org.apache.flink:flink-java8_2.10:jar:1.4-SNAPSHOT: Failed to collect dependencies at org.apache.flink:flin

Re: Building only flink-java8 module

2017-06-01 Thread Ted Yu
When I used the command given by Aljoscha, I got: https://pastebin.com/8WTGvdFQ FYI On Thu, Jun 1, 2017 at 8:17 AM, Aljoscha Krettek wrote: > Hi, > > I think you can use something like > > mvn verify -am -pl flink-java8 > > (From the base directory) > > The -pl flag will tell maven to only do

Re: Building only flink-java8 module

2017-06-01 Thread Aljoscha Krettek
Hi, I think you can use something like mvn verify -am -pl flink-java8 (From the base directory) The -pl flag will tell maven to only do that module while -am tells it to also builds its dependencies. This might or might not also run the tests on the dependent-upon projects, I’m not sure. As

Building only flink-java8 module

2017-06-01 Thread Dawid Wysakowicz
Hi devs! Recently I tried running* mvn verify* just for the *flink-java8* module (to run those tests locally) and it fails with the following error: [ERROR] Failed to execute goal on project flink-java8_2.10: Could not > resolve dependencies for project > org.apache.flink:flink-java8_2.10:jar:1.4