Return-Path: X-Original-To: apmail-flink-user-archive@minotaur.apache.org Delivered-To: apmail-flink-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8866A184A6 for ; Thu, 11 Feb 2016 23:51:16 +0000 (UTC) Received: (qmail 5517 invoked by uid 500); 11 Feb 2016 23:51:16 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 5420 invoked by uid 500); 11 Feb 2016 23:51:16 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 5409 invoked by uid 99); 11 Feb 2016 23:51:16 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Feb 2016 23:51:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 21134C0873 for ; Thu, 11 Feb 2016 23:51:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6-dnko1V6S-y for ; Thu, 11 Feb 2016 23:51:13 +0000 (UTC) Received: from mail-io0-f169.google.com (mail-io0-f169.google.com [209.85.223.169]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 59EED2565F for ; Thu, 11 Feb 2016 23:51:12 +0000 (UTC) Received: by mail-io0-f169.google.com with SMTP id g203so49532742iof.2 for ; Thu, 11 Feb 2016 15:51:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=MIlzvQILd/dxyC7RJ7JLUkb2PQRXgpJCJVoxsm0y3d0=; b=XId3qFcSBwzBr4RpGDEelJ9A41NbUJbFVKwcNJZTxTroERWBPPj19p7fHLXoiFj6E4 /XH4OVlfism/yXS4z4cQSlfkPlVKvmb5OXeoAMoQn3nVPNDWPc5GdNpaGYVt9sEMEnoS WYrXg7c5RaxMgfvuee8GjBPDsfJkj69Sh0XaipYdbOk7sztxOHhS+S/hET1VT21msUig DYA5/rS95tJjeA63IJzC+sRJ6gnBw9IbBXdhRNazPwGm28rZVHY+QfL2ftJn/2qZzWNH PgKu6EtZlh98Dnkem0O36doA+aKK//GOVWYthet9KNOeUGlaHAcI8gsXXTQQ39rUVzUa 5FqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=MIlzvQILd/dxyC7RJ7JLUkb2PQRXgpJCJVoxsm0y3d0=; b=D67cElzsQvZH5sTzVj3EmfsalFg90cE8FcF2TK7uvLuCZOKJPSPhGPa1E4Wkbrdgp9 TS5jo9a3FKI5CpYHT4FMrnf08rXEwutaTLailQHSPksdl9a1HFIaVzbmx4tDRl9N+yVV h2iJTJ/vt8F0mseekuFU3mxUhHoiWK1MqE6zdmq2KGK5pZIUlVuzVtLfLypoyjszuhoq oV7/IWrvj6VoLU6jc82y7h8ZT3w/MKUZA1tS2dZDyOLmUrQev2ozKdUO5klGyjB5tskT RqTEPRpTR00sODHUohDjbC8GdQf0Chd4Xh8nXcXzAcQGZTkH3MlWg6d/Yvm38H25zcLS Ff5g== X-Gm-Message-State: AG10YOTGSln3xbEOO4BjgpyH0mFnxP1mu57PtnnY2XcURSQUVFdqxQyJIMUqfSTHYKwcwhTeSJCnb3Vgdnq7ZA== MIME-Version: 1.0 X-Received: by 10.107.160.83 with SMTP id j80mr46898374ioe.23.1455234665644; Thu, 11 Feb 2016 15:51:05 -0800 (PST) Sender: ewenstephan@gmail.com Received: by 10.107.159.194 with HTTP; Thu, 11 Feb 2016 15:51:05 -0800 (PST) In-Reply-To: References: Date: Fri, 12 Feb 2016 00:51:05 +0100 X-Google-Sender-Auth: 9JgelUAzcSy3WKHsED-4PS7iSIw Message-ID: Subject: Re: Compile issues with Flink 1.0-SNAPSHOT and Scala 2.11 From: Stephan Ewen To: user@flink.apache.org Content-Type: multipart/alternative; boundary=001a11405e324f8cf6052b8739bf --001a11405e324f8cf6052b8739bf Content-Type: text/plain; charset=UTF-8 Hi! The CI system has just finished uploading an new snapshot. In that one, the scalatest dependency is now correctly at 2.11 again. https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-test-utils_2.11/1.0-SNAPSHOT/flink-test-utils_2.11-1.0-20160211.232156-288.pom I am very puzzled, we did not touch any parts that seem to affect this. I am wondering if it is possible that Maven had a hiccup... Can you retry (force dependency update), see if the dependencies are correct again? Greetings, Stephan On Fri, Feb 12, 2016 at 12:23 AM, Stephan Ewen wrote: > Hi! > > I examined the Apache Snapshot Repository, and I could see that in the > latest snapshot a "scalatest_2.10" version was introduced. I could not > figure out how, yet. I could not find a "flink-core_2.10" or > "flink-annotations_2.10" dependency, yet. > > > Previous snapshot: > https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-test-utils_2.11/1.0-SNAPSHOT/flink-test-utils_2.11-1.0-20160211.162913-286.pom > > Latest Snapshot: > https://repository.apache.org/content/repositories/snapshots/org/apache/flink/flink-test-utils_2.11/1.0-SNAPSHOT/flink-test-utils_2.11-1.0-20160211.201205-287.pom > > > We'll try and fix this ASAP. Sorry for that, this is quite a mystery right > now... > > Best, > Stephan > > On Thu, Feb 11, 2016 at 11:56 PM, Cory Monty > wrote: > >> Ufuk, >> >> Thanks for the link. I've double-checked everything in our dependencies >> list and it's all correct. >> >> Stephan, >> >> We don't explicitly depend on "flink-java", so there should be no suffix. >> It's curious, to me, that scalatest is showing in the stack trace. I also >> tried clearing ~/.sbt/staging and it did not help. Our build server >> (CircleCI) is also experiencing the same issue, so I don't think it's local >> to my machine. >> >> On Thu, Feb 11, 2016 at 4:09 PM, Stephan Ewen wrote: >> >>> Hi Cory! >>> >>> Hmmm, curios... I just double check the code, there are no more >>> references to a Scala-versioned "flink-core" and "flink-annotations" >>> project in the code base. >>> >>> The projects you use with Scala version suffix look good, actually. Just >>> to be safe, can you check that the "flink-java" dependency is without >>> suffix? >>> >>> One other thing I can imagine is a mixed up dependency cache. Can you >>> try to refresh all snapshot dependencies (maybe clear "~/.sbt/staging/"). >>> >>> >>> It is high-time for a 1.0 release, so you need not work on the SNAPSHOT >>> versions any more. That should really solve this version conflict pain. >>> If we are fast tomorrow, there may be a nice surprise coming up in the >>> next days... >>> >>> Greetings, >>> Stephan >>> >>> >>> On Thu, Feb 11, 2016 at 10:24 PM, Cory Monty < >>> cory.monty@getbraintree.com> wrote: >>> >>>> Hmm. We don't explicitly include "flink-annotations" and we do not >>>> append the Scala suffix for "flink-core": >>>> >>>> `"org.apache.flink" % "flink-core" % "1.0-SNAPSHOT"` >>>> >>>> Here are the packages we currently include with a Scala suffix: >>>> >>>> flink-scala >>>> flink-clients >>>> flink-streaming-scala >>>> flink-connector-kafka-0.8 >>>> flink-test-utils >>>> flink-streaming-contrib >>>> >>>> If there is any documentation you can point to regarding when to >>>> include the Scala suffix on Flink packages, let me know. >>>> >>>> >>>> >>>> On Thu, Feb 11, 2016 at 2:55 PM, Stephan Ewen wrote: >>>> >>>>> Hi Cory! >>>>> >>>>> "flink-core" and "flink-annotations" should not have Scala suffixes, >>>>> because they do not depend on Scala. >>>>> >>>>> So far, we mark the Scala independent projects without suffixes. Is >>>>> that very confusing, or does that interfere with build tools? >>>>> >>>>> Greetings, >>>>> Stephan >>>>> >>>>> >>>>> On Thu, Feb 11, 2016 at 9:50 PM, Cory Monty < >>>>> cory.monty@getbraintree.com> wrote: >>>>> >>>>>> As of this afternoon, SBT is running into issues compiling with the >>>>>> following error: >>>>>> >>>>>> [error] Modules were resolved with conflicting cross-version suffixes >>>>>> in >>>>>> [error] org.scalatest:scalatest _2.10, _2.11 >>>>>> [error] org.apache.flink:flink-core _2.11, >>>>>> [error] org.apache.flink:flink-annotations _2.11, >>>>>> java.lang.RuntimeException: Conflicting cross-version suffixes in: >>>>>> org.scalatest:scalatest, org.apache.flink:flink-core, >>>>>> org.apache.flink:flink-annotations >>>>>> at scala.sys.package$.error(package.scala:27) >>>>>> at >>>>>> sbt.ConflictWarning$.processCrossVersioned(ConflictWarning.scala:46) >>>>>> at sbt.ConflictWarning$.apply(ConflictWarning.scala:32) >>>>>> at sbt.Classpaths$$anonfun$66.apply(Defaults.scala:1164) >>>>>> at sbt.Classpaths$$anonfun$66.apply(Defaults.scala:1161) >>>>>> at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47) >>>>>> at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40) >>>>>> at sbt.std.Transform$$anon$4.work(System.scala:63) >>>>>> at >>>>>> sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226) >>>>>> at >>>>>> sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226) >>>>>> at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17) >>>>>> at sbt.Execute.work(Execute.scala:235) >>>>>> at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226) >>>>>> at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226) >>>>>> at >>>>>> sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159) >>>>>> at sbt.CompletionService$$anon$2.call(CompletionService.scala:28) >>>>>> 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:1142) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>>>> at java.lang.Thread.run(Thread.java:745) >>>>>> >>>>>> Any thoughts are greatly appreciated! >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Cory >>>>>> >>>>> >>>>> >>>> >>> >> > --001a11405e324f8cf6052b8739bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi!

The CI system has just finished upl= oading an new snapshot. In that one, the scalatest dependency is now correc= tly at 2.11 again.


I am very puzzled, we did not touch= any parts that seem to affect this. I am wondering if it is possible that = Maven had a hiccup...

Can you retry (force dep= endency update), see if the dependencies are correct again?

<= /div>

Greetings,
Stephan

<= /div>

On Fri, Feb = 12, 2016 at 12:23 AM, Stephan Ewen <sewen@apache.org> wrote:<= br>
Hi!

<= /div>
I examined the Apache Snapshot Repository, and I could see that i= n the latest snapshot a "scalatest_2.10" version was introduced. = I could not figure out how, yet. I could not find a "flink-core_2.10&q= uot; or "flink-annotations_2.10" dependency, yet.

We'll try and fix this ASAP. Sorry for t= hat, this is quite a mystery right now...

Best,
Stephan

On Thu, Feb 11, 2016 at 1= 1:56 PM, Cory Monty <cory.monty@getbraintree.com> = wrote:
Ufuk,

Thanks for the link. I've double-checked everything in our depe= ndencies list and it's all correct.=C2=A0

Step= han,

We don't explicitly depend on "flink= -java", so there should be no suffix. It's curious, to me, that sc= alatest is showing in the stack trace. I also tried clearing ~/.sbt/staging= and it did not help. Our build server (CircleCI) is also experiencing the = same issue, so I don't think it's local to my machine.
<= div>

On Thu, = Feb 11, 2016 at 4:09 PM, Stephan Ewen <sewen@apache.org> wrot= e:
Hi Cory!

=
Hmmm, curios... I just double check the code, there are no more = references to a Scala-versioned "flin= k-core" and "flink-annotations" project in the code bas= e.

The projects you use with Scala version = suffix look good, actually. Just to be safe, can you check that the "f= link-java" dependency is without suffix?

One other= thing I can imagine is a mixed up dependency cache. Can you try to refresh= all snapshot dependencies (maybe clear "~/.sbt/staging/").
<= br>

It is high-time for a 1.0 release, so you need= not work on the SNAPSHOT versions any more. That should really solve this = version conflict pain.
If we are fast tomorrow, there may be a ni= ce surprise coming up in the next days...

Greeting= s,
Stephan


On Thu, Feb 11, 2016 at 10:24 PM, C= ory Monty <cory.monty@getbraintree.com> wrote:
=
Hmm. We don't explicitl= y include "flink-annotations" and we do not append the Scala suff= ix for "flink-core":

`"org.apache.flink&q= uot; % "flink-core" % "1.0-SNAPSHOT"`
Here are the packages we currently include with a Scala suffix:=

flink-scala
flink-clients
fli= nk-streaming-scala
flink-connector-kafka-0.8
flink-test= -utils
flink-streaming-contrib

If there = is any documentation you can point to regarding when to include the Scala s= uffix on Flink packages, let me know.



On = Thu, Feb 11, 2016 at 2:55 PM, Stephan Ewen <sewen@apache.org>= wrote:
Hi Cory!
"flink-core" and "flink-annotations" should= not have Scala suffixes, because they do not depend on Scala.
So far, we mark the Scala independent projects without suffixe= s. Is that very confusing, or does that interfere with build tools?

Greetings,
Stephan


On Thu, F= eb 11, 2016 at 9:50 PM, Cory Monty <cory.monty@getbraintree.com<= /a>> wrote:
As= of this afternoon, SBT is running into issues compiling with the following= error:

[error] Modules were resolved with conflict= ing cross-version suffixes in=C2=A0
[error] =C2=A0 =C2=A0org.scal= atest:scalatest _2.10, _2.11
[error] =C2=A0 =C2=A0org.apache.flin= k:flink-core _2.11, <none>
[error] =C2=A0 =C2=A0org.apache.= flink:flink-annotations _2.11, <none>
java.lang.RuntimeExce= ption: Conflicting cross-version suffixes in: org.scalatest:scalatest, org.= apache.flink:flink-core, org.apache.flink:flink-annotations
at scala.sys.package$.error(package= .scala:27)
at sbt.Co= nflictWarning$.processCrossVersioned(ConflictWarning.scala:46)
at sbt.ConflictWarning$.apply(Co= nflictWarning.scala:32)
at sbt.Classpaths$$anonfun$66.apply(Defaults.scala:1164)
at sbt.Classpaths$$anonfun$66.appl= y(Defaults.scala:1161)
at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
at sbt.$tilde$greater$$anonf= un$$u2219$1.apply(TypeFunctions.scala:40)
at sbt.std.Transform$$anon$4.work(System.scala:63)
at sbt.Execute$$anonfu= n$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
at sbt.Execute$$anonfun$submit$1$$anonfun= $apply$1.apply(Execute.scala:226)
at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
at sbt.Execute.work(Exe= cute.scala:235)
at s= bt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
at sbt.Execute$$anonfun$submit$1.apply(Ex= ecute.scala:226)
at = sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.= scala:159)
at sbt.Co= mpletionService$$anon$2.call(CompletionService.scala:28)
at java.util.concurrent.FutureTask.run= (FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511= )
at java.util.concu= rrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(= ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE= xecutor.java:617)
at= java.lang.Thread.run(Thread.java:745)

Any t= houghts are greatly appreciated!

Cheers,

Cory






--001a11405e324f8cf6052b8739bf--