[
https://issues.apache.org/jira/browse/JENA-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940812#comment-16940812
]
ASF subversion and git services commented on JENA-1764:
-------------------------------------------------------
Commit f1a1f6d7bf4f9a2a9f32fbf4d653f19422ebacae in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=f1a1f6d ]
Merge pull request #612 from apache/JENA-1764
JENA-1764: Fix Automatic-Module-Name metadata
> Fix missing and duplicate Automatic-Module-Name metadata
> --------------------------------------------------------
>
> Key: JENA-1764
> URL: https://issues.apache.org/jira/browse/JENA-1764
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 3.12.0
> Environment: Using Jena on Java11 when Jena artifacts are on the
> module path (rather than the class path)
> Reporter: Aaron Coburn
> Assignee: Aaron Coburn
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The Java9+ module system makes use of the MANIFEST header:
> Automatic-Module-Name. This header is optional, but if present it needs to be
> globally unique and must follow certain formatting rules (e.g. no hyphens).
> The Automatic-Module-Name header in the jena-dboe-storage artifact is empty
> (not missing), which is invalid.
> In addition, the various jena-elephas-* and jena-jdbc-* artifacts contain
> duplicate module name declarations
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
