You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Cole Greer (Jira)" <ji...@apache.org> on 2023/07/31 19:00:00 UTC
[jira] [Closed] (TINKERPOP-2954) Pass Gremlin Version from Maven to Java Without Manifests
[ https://issues.apache.org/jira/browse/TINKERPOP-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cole Greer closed TINKERPOP-2954.
---------------------------------
> Pass Gremlin Version from Maven to Java Without Manifests
> ---------------------------------------------------------
>
> Key: TINKERPOP-2954
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2954
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.5.6, 3.6.4
> Reporter: Cole Greer
> Assignee: Cole Greer
> Priority: Critical
> Fix For: 3.7.0, 3.5.7, 3.6.5
>
>
> Currently maven will store the current version of TinkerPop in the Manifest file which is packaged in all of the java jars where it can be read via jcabi manifests.
> While this system works well in most cases, it has proven unreliable in others. I have seen multiple cases where way in which users include TinkerPop into their project results in the manifest being lost, and the version becoming unavailable.
> It would be nice to switch to an alternative system which does not rely on extra files being packaged in distributions. It would also be nice to have a solution which could easily be extended to all GLV's. A possible solution would be configuring Maven to directly inject the version into source code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)