Replies: 3 comments 5 replies
-
|
Docker :) |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
docker +1 i mostly use jena/fuseki via: and in a similar fashion i mostly use sparql anything by building and running this image: |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Does anyone want to test the release? https://github.com/SPARQL-Anything/sparql.anything/releases/tag/v1.0.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, since we are preparing the v1.0.0 release (#538), I would like to discuss possible changes to the way we release sparql anything. At the moment, apart from releasing the zipped code archives, we include:
There have been discussions regarding the size of jars, which often include dependencies that are only needed for corner cases (see #484 #513).
I also want to mention that PySPARQL-Anything testing, upgrade, and release follow any SA Java release; we can discuss that as well, but consider it a separate workflow.
One way would be to have a light, mid, and full version by including only some formats. E.g.
(please note that I am not sure how to make a single binary for both CLI and Fuseki, but that's a different issue).
Opinions? Would anyone want a different way to package and release SA?
Beta Was this translation helpful? Give feedback.
All reactions