[
https://issues.apache.org/jira/browse/JENA-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101509#comment-15101509
]
ASF GitHub Bot commented on JENA-1118:
--------------------------------------
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/122#issuecomment-171907428
This makes "jena-sdb....distribution" becomes a binary product of the
release. No problem with that but we should do it formerly. When this is
running and distributions in the snapshots maven repo, could you email dev@
with a message asking for a review of the binary and specifically the N&L. We
have to do that at release - it seems to me to be easier to do the task now,
rather than at release when it's busy.
> Bringing back the SDB assembly (zip/tarball distribution)
> ---------------------------------------------------------
>
> Key: JENA-1118
> URL: https://issues.apache.org/jira/browse/JENA-1118
> Project: Apache Jena
> Issue Type: Improvement
> Components: SDB
> Affects Versions: Jena 3.0.1
> Reporter: Osma Suominen
> Assignee: Osma Suominen
> Priority: Minor
>
> I've been using the ancient jena-sdb-1.3.6 distribution but it's getting old.
> I wanted to have something newer to deploy to my server but compiling SDB
> using "mvn package" only builds the jar, not a full distribution with the
> command line scripts etc.
> I noticed that the Maven assembly plugin configuration to do this was
> commented out from jena-sdb/pom.xml in commit 807f8bf on 16 Feb 2014 and
> later removed entirely. Maybe there was a good reason to do so, I don't know.
> The assembly.xml file has since bitrotted slightly since it references files
> that no longer exist.
> In any case I'd like to have it back in working condition and I will open a
> PR shortly to do that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
