Hello Alexandre,
I spent some time trying to tweak the storm-cassandra pom.xml. Although this
will end up in a pull request, the actual error in eclipse about "The package
java.util is accessible from more than one module: , java.base" will
remain.
I might try one or two other things today,
All Storm projects imported in Eclipse are using "JRE System Library
[JavaSE-11]", in all projects, Java compiler compliance level,
Generated classes compatibility and Source compatibility are all set
to 11.
I hope it answers your question.
Kind regards,
Alexandre
Le jeu. 31 août 2023 à 13:30, B
I will look into this later today.Your project (subproject) jvm shows
jdk/jvm-11 (as visible in eclipse in Package Explorer window?
On Thursday, August 31, 2023 at 06:15:55 AM PDT, Alexandre Vermeerbergen
wrote:
Hello,
Thank you very much Bipin for your advice.
I did it, and good new
Hello,
Thank you very much Bipin for your advice.
I did it, and good news, now the number of errors is much lower : from
several thousand errors to 73 errors.
First set of errors is very strange: in
/storm-cassandra/src/test/java/org/apache/storm/cassandra/trident/WeatherBatchSpout.java,
I have t
Looks like eclipse (Also IntelliJ) doesn’t know about the relocated (shaded)
class. Solution that I have used is to build Storm-shaded-deps directly in
maven (mvn install), and then closing the storm-shaded-deps subproject in
eclipse/IntelliJ. This forces the IDE to use the storm-shaded-jar from
Hello;
I have created a branch in my own fork of storm Github projet, and
merged Bipin's changes from these two branches on his own fork:
[STORM-3963] Add m2e plugin to storm-shaded-deps and few minor
pom.xml fixes => remotes/origin/storm-3963 =>
storm-shaded-deps/pom.xml
[STORM-3967] Specify g
I think you can fork the project, merge Bipin's changes and test with
Eclipse locally. If the changes solve the issues, it might be a good
thing otherwise we need to ensure, Eclipse users have a chance to be
onboarded :)
Am Dienstag, dem 29.08.2023 um 23:14 -0400 schrieb Alexandre
Vermeerbergen:
>
Hello Julien,
Here's the precise version of Eclipse IDE which I am using:
==
Eclipse IDE for Java Developers (includes Incubating components)
Version: 2023-06 (4.28.0)
Build id: 20230608-1333
=
As a first time user of eclipse on Storm project, I did encounter a lot "red"
compile error issues.Most of them go away when I built the storm-shaded-deps
project separately, added eclipse m2e plugin for the lifecycle management
setting, and then selected the sub-project and in the context menu
Hi Alexandre
I use Eclipse and have imported Storm with Import -> Existing Maven project
etc.. but am not getting the error message you mentioned. Which version of
Eclipse are you using?
I then get tons of compilation errors, like you do.
Julien
On Mon, 28 Aug 2023 at 02:23, Alexandre Vermeerbe
I also use IntelliJ.To test this out, I downloaded eclipse and imported the
maven project for Storm.It takes a long time for eclipse to complete the task
for loading the project fully. You can right click on the pom.xml (for a
sub-project) and see the progress "Progress Information" popup.I wou
I am using IntelliJ, so no idea about Eclipse. Sorry.
Am Sonntag, dem 27.08.2023 um 21:21 -0400 schrieb Alexandre
Vermeerbergen:
> Hello,
>
> I am trying to use my Eclipse IDE to work on a contribution on storm
> project.
>
> I must be missing something, because I though I was just a matter of
Hello,
I am trying to use my Eclipse IDE to work on a contribution on storm project.
I must be missing something, because I though I was just a matter of
using Eclipse's import projects... / Maven / Existing Maven Projects
and point to the root directory of my local Storm git directory.
But this
13 matches
Mail list logo
