Re: Build error: package does not exist
And I've tried just `mvn clean install -DskipTests -Drat.skip=true -DskipITs` as well. It takes around half an hour, so I'm not too keen to try all the possibilities. I guess there might be some other SDKs/libraries that I'm missing and Maven won't tell me? Or just some random incompatibility? Thanks for any tips, Hynek po 28. 10. 2019 v 20:24 odesílatel Hynek Noll napsal: > Dear Pritam, > I've tried that as well, specifically I ran: > `mvn clean install -DskipTests -Drat.skip=true -DskipITs -Pinclude-kinesis > -Daws.kinesis-kpl.version=0.12.6` > But the result is still the same. During the build, the packages that I > suppose should be generated by Maven based on Amazon Kinesis are missing. > > Best regards, > Hynek > > po 28. 10. 2019 v 19:57 odesílatel Pritam Sadhukhan < > sadhukhan.pri...@gmail.com> napsal: > >> Hi Hynek, >> >> please run mvn clean install -DskipTests -Drat.skip=true. >> >> It should build properly but takes time. >> >> Regards >> >> On Mon, Oct 28, 2019, 10:06 PM Hynek Noll wrote: >> >> > 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 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 >> 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 写道: >> > > > > >> > > > > package seems to be missing on GitHub: >> > > > >> > > > >> > > >> > >> >
Re: Build error: package does not exist
Hi Hynek, I used `mvn clean install -DskipTests -Drat.skip=true` on the root directory. I have build release 1.9 branch and took me around 1hr 23 minutes to complete with no errors. Regards, Pritam. On Tue, 29 Oct 2019 at 01:02, Hynek Noll wrote: > And I've tried just > `mvn clean install -DskipTests -Drat.skip=true -DskipITs` > as well. It takes around half an hour, so I'm not too keen to try all the > possibilities. > > I guess there might be some other SDKs/libraries that I'm missing and Maven > won't tell me? Or just some random incompatibility? > > Thanks for any tips, > Hynek > > po 28. 10. 2019 v 20:28 odesílatel Hynek Noll napsal: > > > And I've tried just > > `mvn clean install -DskipTests -Drat.skip=true -DskipITs` > > as well. It takes around half an hour, so I'm not too keen to try all the > > possibilities. > > > > I guess there might be some other SDKs/libraries that I'm missing and > > Maven won't tell me? Or just some random incompatibility? > > > > Thanks for any tips, > > Hynek > > > > po 28. 10. 2019 v 20:24 odesílatel Hynek Noll > > napsal: > > > >> Dear Pritam, > >> I've tried that as well, specifically I ran: > >> `mvn clean install -DskipTests -Drat.skip=true -DskipITs > >> -Pinclude-kinesis -Daws.kinesis-kpl.version=0.12.6` > >> But the result is still the same. During the build, the packages that I > >> suppose should be generated by Maven based on Amazon Kinesis are > missing. > >> > >> Best regards, > >> Hynek > >> > >> po 28. 10. 2019 v 19:57 odesílatel Pritam Sadhukhan < > >> sadhukhan.pri...@gmail.com> napsal: > >> > >>> Hi Hynek, > >>> > >>> please run mvn clean install -DskipTests -Drat.skip=true. > >>> > >>> It should build properly but takes time. > >>> > >>> Regards > >>> > >>> On Mon, Oct 28, 2019, 10:06 PM Hynek Noll > wrote: > >>> > >>> > 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 > 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 > >>> 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 写道: > >>> > > > > > >>> > > > > package seems to be missing on GitHub: > >>> > > > > >>> > > > > >>> > > > >>> > > >>> > >> >
Re: Build error: package does not exist
And I've tried just `mvn clean install -DskipTests -Drat.skip=true -DskipITs` as well. It takes around half an hour, so I'm not too keen to try all the possibilities. I guess there might be some other SDKs/libraries that I'm missing and Maven won't tell me? Or just some random incompatibility? Thanks for any tips, Hynek po 28. 10. 2019 v 20:28 odesílatel Hynek Noll napsal: > And I've tried just > `mvn clean install -DskipTests -Drat.skip=true -DskipITs` > as well. It takes around half an hour, so I'm not too keen to try all the > possibilities. > > I guess there might be some other SDKs/libraries that I'm missing and > Maven won't tell me? Or just some random incompatibility? > > Thanks for any tips, > Hynek > > po 28. 10. 2019 v 20:24 odesílatel Hynek Noll > napsal: > >> Dear Pritam, >> I've tried that as well, specifically I ran: >> `mvn clean install -DskipTests -Drat.skip=true -DskipITs >> -Pinclude-kinesis -Daws.kinesis-kpl.version=0.12.6` >> But the result is still the same. During the build, the packages that I >> suppose should be generated by Maven based on Amazon Kinesis are missing. >> >> Best regards, >> Hynek >> >> po 28. 10. 2019 v 19:57 odesílatel Pritam Sadhukhan < >> sadhukhan.pri...@gmail.com> napsal: >> >>> Hi Hynek, >>> >>> please run mvn clean install -DskipTests -Drat.skip=true. >>> >>> It should build properly but takes time. >>> >>> Regards >>> >>> On Mon, Oct 28, 2019, 10:06 PM Hynek Noll wrote: >>> >>> > 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 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 >>> 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 写道: >>> > > > > >>> > > > > package seems to be missing on GitHub: >>> > > > >>> > > > >>> > > >>> > >>> >>
Re: Build error: package does not exist
Dear Pritam, I've tried that as well, specifically I ran: `mvn clean install -DskipTests -Drat.skip=true -DskipITs -Pinclude-kinesis -Daws.kinesis-kpl.version=0.12.6` But the result is still the same. During the build, the packages that I suppose should be generated by Maven based on Amazon Kinesis are missing. Best regards, Hynek po 28. 10. 2019 v 19:57 odesílatel Pritam Sadhukhan < sadhukhan.pri...@gmail.com> napsal: > Hi Hynek, > > please run mvn clean install -DskipTests -Drat.skip=true. > > It should build properly but takes time. > > Regards > > On Mon, Oct 28, 2019, 10:06 PM Hynek Noll wrote: > > > 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 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 > 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 写道: > > > > > > > > > > package seems to be missing on GitHub: > > > > > > > > > > > > > >
Re: Build error: package does not exist
Hi Hynek, please run mvn clean install -DskipTests -Drat.skip=true. It should build properly but takes time. Regards On Mon, Oct 28, 2019, 10:06 PM Hynek Noll wrote: > 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 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 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 写道: > > > > > > > > package seems to be missing on GitHub: > > > > > > > > >
Re: Build error: package does not exist
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 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 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 写道: > > > > > > package seems to be missing on GitHub: > > > > >
Re: Build error: package does not exist
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 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 写道: > > > > package seems to be missing on GitHub: > >
Re: Build error: package does not exist
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 写道: > > package seems to be missing on GitHub:
Re: build error
Hi Ameet, The new issue that you are facing is caused by a build-time validator that checks if every file in Flink sources has an Apache license text in it. It suggests that there are two files without a proper license: * build_log_maven_flink * log.oracle.jdk If you remove them or move from the Flink source folder this error will go away. Best regards, Ivan. On Thu, 15 Sep 2016 at 15:57 Ameet BDwrote: > Hi Ivan, > > Thanks for reply. I tried installing Oracle JDK. The build error log is > attached for details. > Error reported is "Too many files with unapproved license". > The file rat.txt is attached. > > Please tell me what could be going wrong. I am using Ubuntu 14.04, Maven > 3.0.5 and Oracle JDK 8. > Regards, > Ameet > > On Thu, Sep 15, 2016 at 5:45 PM, Ivan Mushketyk > wrote: > >> Hi Ameet, >> >> This seems like a possible JVM bug. >> Could you try to build Flink using OracleJDK instead? >> >> Best regards, >> Ivan. >> >> On Thu, 15 Sep 2016 at 12:30 Ameet BD wrote: >> >> > Hi All, >> > >> > I am trying to build latest Flink code from github.com by running >> command >> > >> > $ git clone https://github.com/apache/flink >> > After that I am running command >> > $ mvn clean install -DskipTests >> > >> > The build fails I have attached the build log. >> > >> > Kindly let me know why it may be failing. >> > >> > Regards. >> > Ameet >> > >> > >
Re: build error
I agree with Ivan. This does not look like a Flink specific problem. Have you tried building other projects with your maven and JDK version? Cheers, Till On Thu, Sep 15, 2016 at 2:15 PM, Ivan Mushketykwrote: > Hi Ameet, > > This seems like a possible JVM bug. > Could you try to build Flink using OracleJDK instead? > > Best regards, > Ivan. > > On Thu, 15 Sep 2016 at 12:30 Ameet BD wrote: > > > Hi All, > > > > I am trying to build latest Flink code from github.com by running > command > > > > $ git clone https://github.com/apache/flink > > After that I am running command > > $ mvn clean install -DskipTests > > > > The build fails I have attached the build log. > > > > Kindly let me know why it may be failing. > > > > Regards. > > Ameet > > >
Re: build error
Hi Ameet, This seems like a possible JVM bug. Could you try to build Flink using OracleJDK instead? Best regards, Ivan. On Thu, 15 Sep 2016 at 12:30 Ameet BDwrote: > Hi All, > > I am trying to build latest Flink code from github.com by running command > > $ git clone https://github.com/apache/flink > After that I am running command > $ mvn clean install -DskipTests > > The build fails I have attached the build log. > > Kindly let me know why it may be failing. > > Regards. > Ameet >