(DEPRECATED) Apache Flink Mailing List archive.

Eclipse import errors after akka update

Classic

List

Threaded

8 messages Options

Gyula Fóra

Eclipse import errors after akka update

Hey guys,

Since the last Akka update pull request from Till, I am getting a lot of
import errors (AkkaUtils, and other related packages) in Eclipse and I
cannot build the project. With Eclipse Luna there is no chance it gives
like a 100 erros. With the eclipse scala ide based on Kepler I still get
scala compilation and import errors.

For instance:

in TypeInfomrationGen.scala:
"value q is not member of StringContext"

Any ideas what could cause these and how to fix it?
Is there anyone who can actually build this in eclipse?

Cheers,
Gyula

Stephan Ewen

Re: Eclipse import errors after akka update

I will try and look into this tomorrow. I suspect it is something either
about Scala versions or compiler plugins...

Greetings,
Stephan
Am 19.12.2014 00:23 schrieb "Gyula Fóra" <[hidden email]>:

> Hey guys,
>
> Since the last Akka update pull request from Till, I am getting a lot of
> import errors (AkkaUtils, and other related packages) in Eclipse and I
> cannot build the project. With Eclipse Luna there is no chance it gives
> like a 100 erros. With the eclipse scala ide based on Kepler I still get
> scala compilation and import errors.
>
> For instance:
>
> in TypeInfomrationGen.scala:
> "value q is not member of StringContext"
>
>
> Any ideas what could cause these and how to fix it?
> Is there anyone who can actually build this in eclipse?
>
> Cheers,
> Gyula
>

Till Rohrmann

Re: Eclipse import errors after akka update

Hi Gyula,

I just tried to build the current master with Eclipse Luna and the ScalaIDE
4.0.0 and it worked. What you have to make sure is that the Scala compiler
for the sub modules requiring Scala is set to Scala 2.10. This is
configured under Properties (Module) -> Scala Compiler. Otherwise you get
errors saying that a library is build for a wrong Scala version (namely
2.10). The sub modules requiring a Scala nature are flink-runtime,
flink-scala, flink-scala-examples, flink-test-utils and flink-tests, if I'm
not mistaken.

The second thing are the quasi quotes in the flink-scala module. Either you
simply close the project and everything should work or you add the required
Scala macro plugin paradise_2.10.4-2.0.1.jar to the compiler. You have to
specify it in Properties (Module) -> Scala compiler -> Advanced -> Xplugin.
You should find the paradise jar in your local maven repository, if you
built the project at least once with maven: Something like
~/.m2/repository/org/scalamacros/paradise_2.10.4/2.0.1/paradise_2.10.4-2.0.1.jar.
That is basically the same thing you have to do in IntelliJ as well to be
able to compile the flink-scala module out of IntelliJ.

I hope this solves your problems with Eclipse and sorry for the trouble I
caused you with my changes.

Greets,

Till

On Fri, Dec 19, 2014 at 1:34 AM, Stephan Ewen <[hidden email]> wrote:

>
> I will try and look into this tomorrow. I suspect it is something either
> about Scala versions or compiler plugins...
>
> Greetings,
> Stephan
> Am 19.12.2014 00:23 schrieb "Gyula Fóra" <[hidden email]>:
>
> > Hey guys,
> >
> > Since the last Akka update pull request from Till, I am getting a lot of
> > import errors (AkkaUtils, and other related packages) in Eclipse and I
> > cannot build the project. With Eclipse Luna there is no chance it gives
> > like a 100 erros. With the eclipse scala ide based on Kepler I still get
> > scala compilation and import errors.
> >
> > For instance:
> >
> > in TypeInfomrationGen.scala:
> > "value q is not member of StringContext"
> >
> >
> > Any ideas what could cause these and how to fix it?
> > Is there anyone who can actually build this in eclipse?
> >
> > Cheers,
> > Gyula
> >
>

Gyula Fóra

Re: Eclipse import errors after akka update

Hey,

Thanks Till for the description, I actually thought that I had the things set already what you described since I have been working on the scala code anyways.

It turned out that the xplugin path self updated itself by pasting my workspace path in front of path. So when I checked if I have everything set it looked good since the beginning of the path is same but was actually an invalid…

Sorry I missed that somehow

Gyula

> On 19 Dec 2014, at 02:38, Till Rohrmann <[hidden email]> wrote:
>
> Hi Gyula,
>
> I just tried to build the current master with Eclipse Luna and the ScalaIDE
> 4.0.0 and it worked. What you have to make sure is that the Scala compiler
> for the sub modules requiring Scala is set to Scala 2.10. This is
> configured under Properties (Module) -> Scala Compiler. Otherwise you get
> errors saying that a library is build for a wrong Scala version (namely
> 2.10). The sub modules requiring a Scala nature are flink-runtime,
> flink-scala, flink-scala-examples, flink-test-utils and flink-tests, if I'm
> not mistaken.
>
> The second thing are the quasi quotes in the flink-scala module. Either you
> simply close the project and everything should work or you add the required
> Scala macro plugin paradise_2.10.4-2.0.1.jar to the compiler. You have to
> specify it in Properties (Module) -> Scala compiler -> Advanced -> Xplugin.
> You should find the paradise jar in your local maven repository, if you
> built the project at least once with maven: Something like
> ~/.m2/repository/org/scalamacros/paradise_2.10.4/2.0.1/paradise_2.10.4-2.0.1.jar.
> That is basically the same thing you have to do in IntelliJ as well to be
> able to compile the flink-scala module out of IntelliJ.
>
> I hope this solves your problems with Eclipse and sorry for the trouble I
> caused you with my changes.
>
> Greets,
>
> Till
>
> On Fri, Dec 19, 2014 at 1:34 AM, Stephan Ewen <[hidden email]> wrote:
>>
>> I will try and look into this tomorrow. I suspect it is something either
>> about Scala versions or compiler plugins...
>>
>> Greetings,
>> Stephan
>> Am 19.12.2014 00:23 schrieb "Gyula Fóra" <[hidden email]>:
>>
>>> Hey guys,
>>>
>>> Since the last Akka update pull request from Till, I am getting a lot of
>>> import errors (AkkaUtils, and other related packages) in Eclipse and I
>>> cannot build the project. With Eclipse Luna there is no chance it gives
>>> like a 100 erros. With the eclipse scala ide based on Kepler I still get
>>> scala compilation and import errors.
>>>
>>> For instance:
>>>
>>> in TypeInfomrationGen.scala:
>>> "value q is not member of StringContext"
>>>
>>>
>>> Any ideas what could cause these and how to fix it?
>>> Is there anyone who can actually build this in eclipse?
>>>
>>> Cheers,
>>> Gyula
>>>
>>

Chen Xu

Re: Eclipse import errors after akka update

Hi,

I have the same import errors so that I can not build successfully in
Eclipse Luna.

For example, some class
e.g.org.apache.flink.runtime.messages.ExecutionGraphMessages,
org.apache.flink.runtime.akka.AkkaUtils
can not be found.

So, how to fix it?

Cheers!
-Chen

2014-12-19 6:58 GMT+01:00 Gyula Fora <[hidden email]>:

> Hey,
>
> Thanks Till for the description, I actually thought that I had the things
> set already what you described since I have been working on the scala code
> anyways.
>
> It turned out that the xplugin path self updated itself by pasting my
> workspace path in front of path. So when I checked if I have everything set
> it looked good since the beginning of the path is same but was actually an
> invalid…
>
> Sorry I missed that somehow
>
> Gyula
>
> > On 19 Dec 2014, at 02:38, Till Rohrmann <[hidden email]> wrote:
> >
> > Hi Gyula,
> >
> > I just tried to build the current master with Eclipse Luna and the
> ScalaIDE
> > 4.0.0 and it worked. What you have to make sure is that the Scala
> compiler
> > for the sub modules requiring Scala is set to Scala 2.10. This is
> > configured under Properties (Module) -> Scala Compiler. Otherwise you get
> > errors saying that a library is build for a wrong Scala version (namely
> > 2.10). The sub modules requiring a Scala nature are flink-runtime,
> > flink-scala, flink-scala-examples, flink-test-utils and flink-tests, if
> I'm
> > not mistaken.
> >
> > The second thing are the quasi quotes in the flink-scala module. Either
> you
> > simply close the project and everything should work or you add the
> required
> > Scala macro plugin paradise_2.10.4-2.0.1.jar to the compiler. You have to
> > specify it in Properties (Module) -> Scala compiler -> Advanced ->
> Xplugin.
> > You should find the paradise jar in your local maven repository, if you
> > built the project at least once with maven: Something like
> >
> ~/.m2/repository/org/scalamacros/paradise_2.10.4/2.0.1/paradise_2.10.4-2.0.1.jar.
> > That is basically the same thing you have to do in IntelliJ as well to be
> > able to compile the flink-scala module out of IntelliJ.
> >
> > I hope this solves your problems with Eclipse and sorry for the trouble I
> > caused you with my changes.
> >
> > Greets,
> >
> > Till
> >
> > On Fri, Dec 19, 2014 at 1:34 AM, Stephan Ewen <[hidden email]> wrote:
> >>
> >> I will try and look into this tomorrow. I suspect it is something either
> >> about Scala versions or compiler plugins...
> >>
> >> Greetings,
> >> Stephan
> >> Am 19.12.2014 00:23 schrieb "Gyula Fóra" <[hidden email]>:
> >>
> >>> Hey guys,
> >>>
> >>> Since the last Akka update pull request from Till, I am getting a lot
> of
> >>> import errors (AkkaUtils, and other related packages) in Eclipse and I
> >>> cannot build the project. With Eclipse Luna there is no chance it gives
> >>> like a 100 erros. With the eclipse scala ide based on Kepler I still
> get
> >>> scala compilation and import errors.
> >>>
> >>> For instance:
> >>>
> >>> in TypeInfomrationGen.scala:
> >>> "value q is not member of StringContext"
> >>>
> >>>
> >>> Any ideas what could cause these and how to fix it?
> >>> Is there anyone who can actually build this in eclipse?
> >>>
> >>> Cheers,
> >>> Gyula
> >>>
> >>
>
>

Gyula Fóra

Re: Eclipse import errors after akka update

Hey,

The easiest fix for the eclipse issues is to avoid using luna and instead
use the eclipse scala-ide (which you can also use for java development,
this is what I do). This is basically an eclipse kepler with preinstalled
scala plugins which are actually working.

You can download it from here:
http://scala-ide.org/download/prev-stable.html

Make sure you download the version for Scala 2.10
<http://download.scala-ide.org/sdk/helium/e38/scala210/stable/site>.

When you imported the project the last thing to do is to set the compiler
plugin for the flink-scala project as described by till:
" You have to specify it in Properties (Module) -> Scala compiler ->
Advanced -> Xplugin.
You should find the paradise jar in your local maven repository, if you
built the project at least once with maven: Something like
~/.m2/repository/org/scalamacros/paradise_2.10.4/2.
0.1/paradise_2.10.4-2.0.1.jar."

I hope this helps, worked fine for me and others.

Cheers,
Gyula

On Wed, Dec 24, 2014 at 12:48 AM, Chen Xu <[hidden email]> wrote:

> Hi,
>
> I have the same import errors so that I can not build successfully in
> Eclipse Luna.
>
> For example, some class
> e.g.org.apache.flink.runtime.messages.ExecutionGraphMessages,
> org.apache.flink.runtime.akka.AkkaUtils
> can not be found.
>
> So, how to fix it?
>
> Cheers!
> -Chen
>
> 2014-12-19 6:58 GMT+01:00 Gyula Fora <[hidden email]>:
>
> > Hey,
> >
> > Thanks Till for the description, I actually thought that I had the things
> > set already what you described since I have been working on the scala
> code
> > anyways.
> >
> > It turned out that the xplugin path self updated itself by pasting my
> > workspace path in front of path. So when I checked if I have everything
> set
> > it looked good since the beginning of the path is same but was actually
> an
> > invalid…
> >
> > Sorry I missed that somehow
> >
> > Gyula
> >
> > > On 19 Dec 2014, at 02:38, Till Rohrmann <[hidden email]> wrote:
> > >
> > > Hi Gyula,
> > >
> > > I just tried to build the current master with Eclipse Luna and the
> > ScalaIDE
> > > 4.0.0 and it worked. What you have to make sure is that the Scala
> > compiler
> > > for the sub modules requiring Scala is set to Scala 2.10. This is
> > > configured under Properties (Module) -> Scala Compiler. Otherwise you
> get
> > > errors saying that a library is build for a wrong Scala version (namely
> > > 2.10). The sub modules requiring a Scala nature are flink-runtime,
> > > flink-scala, flink-scala-examples, flink-test-utils and flink-tests, if
> > I'm
> > > not mistaken.
> > >
> > > The second thing are the quasi quotes in the flink-scala module. Either
> > you
> > > simply close the project and everything should work or you add the
> > required
> > > Scala macro plugin paradise_2.10.4-2.0.1.jar to the compiler. You have
> to
> > > specify it in Properties (Module) -> Scala compiler -> Advanced ->
> > Xplugin.
> > > You should find the paradise jar in your local maven repository, if you
> > > built the project at least once with maven: Something like
> > >
> >
> ~/.m2/repository/org/scalamacros/paradise_2.10.4/2.0.1/paradise_2.10.4-2.0.1.jar.
> > > That is basically the same thing you have to do in IntelliJ as well to
> be
> > > able to compile the flink-scala module out of IntelliJ.
> > >
> > > I hope this solves your problems with Eclipse and sorry for the
> trouble I
> > > caused you with my changes.
> > >
> > > Greets,
> > >
> > > Till
> > >
> > > On Fri, Dec 19, 2014 at 1:34 AM, Stephan Ewen <[hidden email]>
> wrote:
> > >>
> > >> I will try and look into this tomorrow. I suspect it is something
> either
> > >> about Scala versions or compiler plugins...
> > >>
> > >> Greetings,
> > >> Stephan
> > >> Am 19.12.2014 00:23 schrieb "Gyula Fóra" <[hidden email]>:
> > >>
> > >>> Hey guys,
> > >>>
> > >>> Since the last Akka update pull request from Till, I am getting a lot
> > of
> > >>> import errors (AkkaUtils, and other related packages) in Eclipse and
> I
> > >>> cannot build the project. With Eclipse Luna there is no chance it
> gives
> > >>> like a 100 erros. With the eclipse scala ide based on Kepler I still
> > get
> > >>> scala compilation and import errors.
> > >>>
> > >>> For instance:
> > >>>
> > >>> in TypeInfomrationGen.scala:
> > >>> "value q is not member of StringContext"
> > >>>
> > >>>
> > >>> Any ideas what could cause these and how to fix it?
> > >>> Is there anyone who can actually build this in eclipse?
> > >>>
> > >>> Cheers,
> > >>> Gyula
> > >>>
> > >>
> >
> >
>

Paris Carbone

RE: Eclipse import errors after akka update

As Gyula described, the combination of scala 2.10.4 with paradise_2.10.4-2.0.1 as a compiler plugin worked for me as well for both the scala IDE and Intellij 14 CE.

In case an Intellij user finds it useful, I did things in the following order:

1) mvn clean package
2) (re)importing the project in intellij
3) adding scala 2.10.4 under Project Structure->Global Libraries
4) adding the path to paradise_2.10.4-2.0.1.jar (got it via maven) under General->Build,Execution,Deployment->Compiler->Scala Compiler-Compiler Plugins

I just found out that there is a reference already in the faq [1] regarding the compilation issue.

Paris

[1] https://github.com/apache/incubator-flink/blob/master/docs/faq.md#in-eclipse-i-get-compilation-errors-in-the-scala-projects
________________________________________
From: Gyula Fóra [[hidden email]]
Sent: Wednesday, December 24, 2014 12:56 AM
To: [hidden email]
Subject: Re: Eclipse import errors after akka update

Hey,

The easiest fix for the eclipse issues is to avoid using luna and instead
use the eclipse scala-ide (which you can also use for java development,
this is what I do). This is basically an eclipse kepler with preinstalled
scala plugins which are actually working.

You can download it from here:
http://scala-ide.org/download/prev-stable.html

Make sure you download the version for Scala 2.10
<http://download.scala-ide.org/sdk/helium/e38/scala210/stable/site>.

When you imported the project the last thing to do is to set the compiler
plugin for the flink-scala project as described by till:
" You have to specify it in Properties (Module) -> Scala compiler ->
Advanced -> Xplugin.
You should find the paradise jar in your local maven repository, if you
built the project at least once with maven: Something like
~/.m2/repository/org/scalamacros/paradise_2.10.4/2.
0.1/paradise_2.10.4-2.0.1.jar."

I hope this helps, worked fine for me and others.

Cheers,
Gyula

On Wed, Dec 24, 2014 at 12:48 AM, Chen Xu <[hidden email]> wrote:

Stephan Ewen

RE: Eclipse import errors after akka update

These are good findings. We should write them down in the Readme.md

Stephan
Am 24.12.2014 11:15 schrieb "Paris Carbone" <[hidden email]>:

>
> As Gyula described, the combination of scala 2.10.4 with
> paradise_2.10.4-2.0.1 as a compiler plugin worked for me as well for both
> the scala IDE and Intellij 14 CE.
>
> In case an Intellij user finds it useful, I did things in the following
> order:
>
> 1) mvn clean package
> 2) (re)importing the project in intellij
> 3) adding scala 2.10.4 under Project Structure->Global Libraries
> 4) adding the path to paradise_2.10.4-2.0.1.jar (got it via maven) under
> General->Build,Execution,Deployment->Compiler->Scala Compiler-Compiler
> Plugins
>
> I just found out that there is a reference already in the faq [1]
> regarding the compilation issue.
>
> Paris
>
>
> [1]
> https://github.com/apache/incubator-flink/blob/master/docs/faq.md#in-eclipse-i-get-compilation-errors-in-the-scala-projects
> ________________________________________
> From: Gyula Fóra [[hidden email]]
> Sent: Wednesday, December 24, 2014 12:56 AM
> To: [hidden email]
> Subject: Re: Eclipse import errors after akka update
>
> Hey,
>
> The easiest fix for the eclipse issues is to avoid using luna and instead
> use the eclipse scala-ide (which you can also use for java development,
> this is what I do). This is basically an eclipse kepler with preinstalled
> scala plugins which are actually working.
>
> You can download it from here:
> http://scala-ide.org/download/prev-stable.html
>
> Make sure you download the version for Scala 2.10
> <http://download.scala-ide.org/sdk/helium/e38/scala210/stable/site>.
>
> When you imported the project the last thing to do is to set the compiler
> plugin for the flink-scala project as described by till:
> " You have to specify it in Properties (Module) -> Scala compiler ->
> Advanced -> Xplugin.
> You should find the paradise jar in your local maven repository, if you
> built the project at least once with maven: Something like
> ~/.m2/repository/org/scalamacros/paradise_2.10.4/2.
> 0.1/paradise_2.10.4-2.0.1.jar."
>
> I hope this helps, worked fine for me and others.
>
> Cheers,
> Gyula
>
>
> On Wed, Dec 24, 2014 at 12:48 AM, Chen Xu <[hidden email]> wrote:
>
> > Hi,
> >
> > I have the same import errors so that I can not build successfully in
> > Eclipse Luna.
> >
> > For example, some class
> > e.g.org.apache.flink.runtime.messages.ExecutionGraphMessages,
> > org.apache.flink.runtime.akka.AkkaUtils
> > can not be found.
> >
> > So, how to fix it?
> >
> > Cheers!
> > -Chen
> >
> > 2014-12-19 6:58 GMT+01:00 Gyula Fora <[hidden email]>:
> >
> > > Hey,
> > >
> > > Thanks Till for the description, I actually thought that I had the
> things
> > > set already what you described since I have been working on the scala
> > code
> > > anyways.
> > >
> > > It turned out that the xplugin path self updated itself by pasting my
> > > workspace path in front of path. So when I checked if I have everything
> > set
> > > it looked good since the beginning of the path is same but was actually
> > an
> > > invalid…
> > >
> > > Sorry I missed that somehow
> > >
> > > Gyula
> > >
> > > > On 19 Dec 2014, at 02:38, Till Rohrmann <[hidden email]>
> wrote:
> > > >
> > > > Hi Gyula,
> > > >
> > > > I just tried to build the current master with Eclipse Luna and the
> > > ScalaIDE
> > > > 4.0.0 and it worked. What you have to make sure is that the Scala
> > > compiler
> > > > for the sub modules requiring Scala is set to Scala 2.10. This is
> > > > configured under Properties (Module) -> Scala Compiler. Otherwise you
> > get
> > > > errors saying that a library is build for a wrong Scala version
> (namely
> > > > 2.10). The sub modules requiring a Scala nature are flink-runtime,
> > > > flink-scala, flink-scala-examples, flink-test-utils and flink-tests,
> if
> > > I'm
> > > > not mistaken.
> > > >
> > > > The second thing are the quasi quotes in the flink-scala module.
> Either
> > > you
> > > > simply close the project and everything should work or you add the
> > > required
> > > > Scala macro plugin paradise_2.10.4-2.0.1.jar to the compiler. You
> have
> > to
> > > > specify it in Properties (Module) -> Scala compiler -> Advanced ->
> > > Xplugin.
> > > > You should find the paradise jar in your local maven repository, if
> you
> > > > built the project at least once with maven: Something like
> > > >
> > >
> >
> ~/.m2/repository/org/scalamacros/paradise_2.10.4/2.0.1/paradise_2.10.4-2.0.1.jar.
> > > > That is basically the same thing you have to do in IntelliJ as well
> to
> > be
> > > > able to compile the flink-scala module out of IntelliJ.
> > > >
> > > > I hope this solves your problems with Eclipse and sorry for the
> > trouble I
> > > > caused you with my changes.
> > > >
> > > > Greets,
> > > >
> > > > Till
> > > >
> > > > On Fri, Dec 19, 2014 at 1:34 AM, Stephan Ewen <[hidden email]>
> > wrote:
> > > >>
> > > >> I will try and look into this tomorrow. I suspect it is something
> > either
> > > >> about Scala versions or compiler plugins...
> > > >>
> > > >> Greetings,
> > > >> Stephan
> > > >> Am 19.12.2014 00:23 schrieb "Gyula Fóra" <[hidden email]>:
> > > >>
> > > >>> Hey guys,
> > > >>>
> > > >>> Since the last Akka update pull request from Till, I am getting a
> lot
> > > of
> > > >>> import errors (AkkaUtils, and other related packages) in Eclipse
> and
> > I
> > > >>> cannot build the project. With Eclipse Luna there is no chance it
> > gives
> > > >>> like a 100 erros. With the eclipse scala ide based on Kepler I
> still
> > > get
> > > >>> scala compilation and import errors.
> > > >>>
> > > >>> For instance:
> > > >>>
> > > >>> in TypeInfomrationGen.scala:
> > > >>> "value q is not member of StringContext"
> > > >>>
> > > >>>
> > > >>> Any ideas what could cause these and how to fix it?
> > > >>> Is there anyone who can actually build this in eclipse?
> > > >>>
> > > >>> Cheers,
> > > >>> Gyula
> > > >>>
> > > >>
> > >
> > >
> >