laurentgo commented on issue #41571:
URL: https://github.com/apache/arrow/issues/41571#issuecomment-2123679316
The issue seems to be because `maven-shade-plugin` generates and attach a
new pom file containing the following dependency:
```
<dependency>
<groupId>org.apache.arrow</groupId>
<artifactId>arrow-format</artifactId>
<version>17.0.0-SNAPSHOT</version>
<scope>provided</scope>
</dependency>
```
which is exactly what the plugin [is supposed to be
doing](https://github.com/apache/arrow/blob/main/java/vector/pom.xml#L233)
I have the same resulting pom by using `maven-shade-plugin` 3.3.0, and going
through changes, I found [this
change](https://github.com/apache/maven-shade-plugin/commit/6ea8543b8b380bd4ebc0e876970957426bb46808)
which is a bugfix to the plugin for this
[issue](https://issues.apache.org/jira/browse/MSHADE-321)
As to how to address this within the Arrow project, I'd need some
perspective. The main issue is that a Maven module has a unique `pom.xml`
definition for all the artifacts attached to it. But when attaching shaded
artifacts the list of dependencies is not quite the same, and this is
definitively conflicting.
I have no idea which project is actually using the shaded version of
`arrow-vector`, but Spark isn't and so if we agree that the pom.xml should
reflect the dependencies for the main artifact, then we should tell
`maven-shade-plugin` to not generate a new `pom.xml` file. If we need both
dependencies, then we are quite in a predicament I'd guess (and same would
apply to the other plugins using `maven-shade-plugin`)
--
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]
