-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
difference between the maven central apoc-core jar and the one on the release page for version 5.x #259
Comments
Hey! I tried this out and couldn't reproduce the issue, are you able to share the Docker command you used with me? Thanks! |
Hi Gem, thanks for your response! We build our custom docker image using the docker maven plugin from fabric8. Below the relevant part of our project pom.xml file. As a bit of context: we build a custom docker image, based on the neo4j official community image. In our custom image we package our entire project as customer stored procedures and user functions. (rtim is our project name)
Cheers, |
Thanks for that, from my understanding, the APOC jar downloaded here is simply not containing all compiled dependencies needed for the other functions. I added a few:
And
(see list of needed on Maven central) and was able to load the missing ones in my Docker container. When you download the jar from github, or manually download the 'fat' jar from Maven, the dependencies (as well as APOC common) are included. Hope this helps :) |
Ah okay, I was under the assumption that the maven central JAR would be exactly the same as the jar from github (because they have the same name). For now as a workaround we manually included the github 'fat jar' in our build cycle. I think we'll keep this approach, since managing the required dependencies ourselves would be a bit of a hassle. Is there a specific reason not to make the fat jar available as a download in maven central? (maybe with an "all" classifier or something?). That would make our build cycle a bit easier, instead of either having to manually download new versions, or to make sure we include all the dependencies of the apoc libraries ourselves. Thanks a bunch already for the help, |
We have done a lot of shifting around with APOC since the 4.x series, I will make a ticket for us to investigate our workflow to see if we should be altering how our Maven uploads work :) Sorry about the hassel and thanks for letting us know :) |
No worries, many thanks for looking into it and for the follow-up! |
Possibly related: The jar in Maven Central doesn't seem to work in the test harness for 5.x - it results in runtime exceptions, see: https://community.neo4j.com/t5/neo4j-graph-platform/using-apoc-with-test-harness-in-5-x/td-p/62849 |
We found a core-classifier which has the same content as the jar on the release versions.
|
This issues seems to resolved by the last message on Jan 25, 2023. Closing now. |
Expected Behavior (Mandatory)
That including
in my project would have the same result as me manually downloading the apoc-core jar from the github releases page.
Actual Behavior (Mandatory)
Instead the version coming in through maven is missing some key functions, as compared to the one on the github page. An example of such a function which is missing in the maven central jar is apoc.coll.sort (which I ran into), but there are a lot of others also missing
How to Reproduce the Problem
set up a local docker container of neo4j, where you mount the apoc-core.jar (version 5.1 and up) you downloaded from maven central into the plugins dir of the container
apoc.coll.sort won't be available (amongst other functions which are also missing)
Steps (Mandatory)
Specifications (Mandatory)
not sure what to write here, apologies
Currently used versions
5.2.1
Versions
The text was updated successfully, but these errors were encountered: