Hi Bruce and Jark,
Thank you for the tip, but I already did the similar by clicking "Generate
Sources and Update Folders". I tried the suggested command(s), but without
success unfortunately.
Executing  `mvn clean install -DskipTests` resulted in an error: "Too many
files with unapproved license: 2 See RAT report ...". (In the report it
states the two files are:
flink-core/src/test/resources/abstractID-with-toString-field
    flink-core/src/test/resources/abstractID-with-toString-field-set
) While `mvn clean package -DskipTests` actually runs for 30+ minutes (much
longer that the first command but maybe that stops early because of the
error) and finishes fine but I have the same problems afterwards.

I've tried switching to Maven 3.1.1 (from 3.6.1).

Now the one thing that resolved the above stated missing package was
switching to Scala 2.11.12 SDK (instead of 2.12)!

The steps I've been taking were (within IntelliJ) Invalidate caches &
restart (alternatively Exit and delete the .idea folder) -> Open IntelliJ
again -> Maven Reimport -> Maven Generate Sources and Update Folders ->
Build Project. That results in further package(s) missing:


*Error:(21, 53) java: package org.apache.flink.kinesis.shaded.com.amazonaws
does not exist*
Maybe it now has to do with just the dependency shading?

Best regards,
Hynek

ne 27. 10. 2019 v 15:02 odesílatel Jark Wu <imj...@gmail.com> napsal:

> Hi Hynek,
>
> Bruce is right, you should build Flink source code first before developing
> by `mvn clean package -DskipTests` in the root directory of Flink.
> This may take 10 minutes or more depends on your machine.
>
> Best,
> Jark
>
> On Sun, 27 Oct 2019 at 20:46, yanjun qiu <qiuyanjun...@gmail.com> wrote:
>
> > Hi Hynek,
> > I think you should run maven build first, execute mvn clean install
> > -DskipTests. Because the Flink SQL parser is used apache calcite
> framework
> > to generate the sql parser source code.
> >
> > Regards,
> > Bruce
> >
> > > 在 2019年10月27日,上午12:09,Hynek Noll <nollh...@fel.cvut.cz> 写道:
> > >
> > > package seems to be missing on GitHub:
> >
> >
>

Reply via email to