Hi Bertrand,
This approach would work and would be a useful addition if support for
repositories transiently sharing the DataStore is needed.
Though it would be an extremely rare case we need to be mindful about how
to signal a failure to refresh the expiration time and what action is to be
[
https://issues.apache.org/jira/browse/JCRVLT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated JCRVLT-155:
Resolution: Fixed
Fix Version/s: 3.1.40
Status: Resolved (was: Patch
On 2017-05-05 17:16, Alex Parvulescu wrote:
Hi,
I'm not sure what the latest is here, but isn't this regarded as bad
practice?
Maintenance branches have always been subsets of the subsequent branch: 1.0
< 1.2 < 1.4 < 1.6 and so on? Any 1.6 release should contain *all* of 1.4
(give or take a
