[
https://issues.apache.org/jira/browse/JENA-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239309#comment-16239309
]
ASF GitHub Bot commented on JENA-1418:
--------------------------------------
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/304#discussion_r148941258
--- Diff: jena-fuseki2/pom.xml ---
@@ -61,8 +61,7 @@
</licenses>
<properties>
- <ver.jetty>9.4.5.v20170502</ver.jetty>
- <ver.shiro>1.2.4</ver.shiro>
+ <ver.jetty>9.4.7.v20170914</ver.jetty>
--- End diff --
If you want to be consistent, this should be in jena-project.
The general idea was that this POM contained the Fuseki specific items,
hence versions limited in use to Fuseki were put here. Not sure how much this
style is used elsewhere in Jena.
An alternative is that we have no intermediate POM and put every in the
project's parent.
jena-project was done that way at short notice so may we make the top POM
also the parent.
All-in-all, how about making this PR about versions and having a wider
discussion about build design?
> Upgrade minor dependencies
> --------------------------
>
> Key: JENA-1418
> URL: https://issues.apache.org/jira/browse/JENA-1418
> Project: Apache Jena
> Issue Type: Dependency upgrade
> Affects Versions: Jena 3.5.0
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Trivial
> Fix For: Jena 3.6.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
