I’m wondering if we can remove the ILoopCompat duplication by checking and
reading the trait properties with reflection … but I have not discovered how to
do this.
> On Jul 4, 2017, at 3:57 AM, Piotr Nowojski wrote:
>
> Besides deactivating “scala-2.10” profile in the Intellij it might be
>
First of all by activating scala-2.10/2.11 profile we change two properties to
some predefined values:
2.10.6
2.10
To drop profile for that, one would have to overwrite both of those properties
simultaneously.
Secondly yes, we h
Is it possible to not use a profile for that, but only an actual property
variable?
Or do we use different dependencies with Scala 2.10 vs Scala 2.11 ?
On Tue, Jul 4, 2017 at 11:23 AM, 郭健 wrote:
> After deactivating scala-2.10 profile in IntelliJ, this issue is gone.
> Thank you all.
>
> On 7/4
After deactivating scala-2.10 profile in IntelliJ, this issue is gone.
Thank you all.
On 7/4/17, 17:11, "Piotr Nowojski" wrote:
Maybe try
$ mvn clean
Before reimporting and restarting/invalidating caches in IntelliJ? Did you
deactivate scala-2.10 profile in the IntelliJ?
You could also try the nuclear option of actually re-importing the
project into intellij (as if you just downloaded it), that worked for me.
On 04.07.2017 11:11, Piotr Nowojski wrote:
Maybe try
$ mvn clean
Before reimporting and restarting/invalidating caches in IntelliJ? Did you
deactivate
Maybe try
$ mvn clean
Before reimporting and restarting/invalidating caches in IntelliJ? Did you
deactivate scala-2.10 profile in the IntelliJ?
Piotrek
> On Jul 4, 2017, at 11:05 AM, 郭健 wrote:
>
> I have done all these but still got some issue in IDEA, especially in the
> flink-connecto
I have done all these but still got some issue in IDEA, especially in the
flink-connector project.
On 7/4/17, 15:57, "Piotr Nowojski" wrote:
Besides deactivating “scala-2.10” profile in the Intellij it might be
necessary to:
- reimport maven project:
1. Right click on root
Besides deactivating “scala-2.10” profile in the Intellij it might be necessary
to:
- reimport maven project:
1. Right click on root module: “flink-parent”
2. Maven
3. reimport
- invalidate caches and restart: File -> Invalidate caches and restart ->
invalidate /restart
-
+1
Meet the same problem. I have tried reimporting the maven project but have no
effect.
From: Jark Wu
Reply-To: "dev@flink.apache.org"
Date: Tuesday, July 4, 2017 at 11:56
To: "dev@flink.apache.org"
Subject: [外部邮件] Tips to fix IDEA strange problem after updating
Thanks for the hint!
> On 4. Jul 2017, at 06:03, Ted Yu wrote:
>
> Looks like the picture didn't go thru.
>
> Mind using third party site ?
>
> Thanks
>
> On Mon, Jul 3, 2017 at 8:56 PM, Jark Wu wrote:
>
>> Hi devs,
>>
>> Yesterday, I updated the master code which include [FLINK-7030]: Bui
Looks like the picture didn't go thru.
Mind using third party site ?
Thanks
On Mon, Jul 3, 2017 at 8:56 PM, Jark Wu wrote:
> Hi devs,
>
> Yesterday, I updated the master code which include [FLINK-7030]: Build
> with scala-2.11 by default. After that, I entered a strange problem with
> IDEA tha
Hi devs,
Yesterday, I updated the master code which include [FLINK-7030]: Build with
scala-2.11 by default. After that, I entered a strange problem with IDEA
that many classes can't be found, and the project can't be built/compiled
(in IDEA), but maven install worked good.
After a series of attem
12 matches
Mail list logo
