jduo commented on issue #347:
URL: https://github.com/apache/arrow-cookbook/issues/347#issuecomment-2049707554
I was able to get past the above error by adding an explicit dependency on
protobuf to the demo pom too:
```
<dependency>
<groupId>com.google.protobuf</groupId>
<artifactId>protobuf-java</artifactId>
<version>3.23.1</version>
</dependency>
```
It seems that unnamed modules cannot access other dependencies in the
unnamed module that have been brought in transitively, but can when they have
been brought in explicitly:
https://stackoverflow.com/questions/70439672/illegalaccesserror-classa-and-class-b-are-in-unnamed-module-of-loader-app
> Hmm so are we just invoking JShell wrongly then?
The right thing to do is likely to correctly build module-path and classpath
separately when using Arrow 16+. We probably should step back and think about
what we want to support though (for example do we intend users to put Arrow in
the unnamed module? If so, how do we make this friendlier -- alternate
artifacts that skip adding module-info.java perhaps)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
