[
https://issues.apache.org/jira/browse/JENA-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359054#comment-16359054
]
ASF GitHub Bot commented on JENA-1483:
--------------------------------------
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/355#discussion_r167362604
--- Diff: pom.xml ---
@@ -735,6 +735,7 @@
<artifactId>maven-compiler-plugin</artifactId>
<version>3.7.0</version>
<configuration>
+ <showDeprecation>false</showDeprecation>
--- End diff --
This crept in. We don't build with `-Xlint:deprecation` and all the output
is
```
[INFO] ....java: Some input files use or override a deprecated API.
[INFO] ....java: Recompile with -Xlint:deprecation for details.
```
so it does not given much information. Being an old codebase, and valuing
legacy continuity, using/overriding deprecation happens.
> Allow different promote() modes.
> --------------------------------
>
> Key: JENA-1483
> URL: https://issues.apache.org/jira/browse/JENA-1483
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Priority: Major
>
> This follows on from JENA-1458.
> In the previous work, there is one promote operation, {{promote()}}, that
> takes the transaction type to determine whether to promote with or without
> "read commits" effects.
> This ticket introduces {{promote(Promote mode)}} where the mode can be given
> explicitly.
> {{promote()}} becomes a default method of the interface that chooses the
> promote mode based on the way the transaction was started.
> This ticket also changes {{promote}} to return boolean false, and leave the
> transaction still valid, if an attempt is made to promote a read-only
> transaction. This is more uniform between the transaction type and any
> intermediate writer blocking promotion in READ_PROMOTE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
