[
https://issues.apache.org/jira/browse/TINKERPOP-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538376#comment-16538376
]
stephen mallette commented on TINKERPOP-2000:
---------------------------------------------
It's a custom key, stamped into the manifest file and simply refers to the
"TinkerPop Version" - if there is a standard key that specifies that then I'm
fine to change it. I seem to recall there being some discussion about
Specification-Version (and other "-Version" standard fields) not being the
right thing to use for this case which is why we have this custom one. If you
have some knowledge to share in this area please let us know.
> MANIFEST.MF contains invalid key
> --------------------------------
>
> Key: TINKERPOP-2000
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2000
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.3.3
> Reporter: Horacio Hoyos Rodriguez
> Priority: Critical
>
> The MANIFEST.MF file for tinerpop-core contains an invalid key (line 8):
> version: 3.3.3
> Some tools (like the Eclipse Bundle Recipes) check for the MANIFEST integrity
> and this line causes an error. Perhaps this is the Specification-Version?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
