[jira] [Commented] (JCR-5062) Attempt to return connection twice
[
https://issues.apache.org/jira/browse/JCR-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849201#comment-17849201
]
Julian Reschke commented on JCR-5062:
-
We could add debug information to find out why the connection is closed twice.
But it's a bit of work. (We have similar code in Oak's RDB code).
> Attempt to return connection twice
> --
>
> Key: JCR-5062
> URL: https://issues.apache.org/jira/browse/JCR-5062
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.20.16
>Reporter: Henrik Hald Nørgaard
>Priority: Minor
> Attachments: stacktrace.txt
>
>
> We are using a JackRabbit content repository and are going to update some
> nodes with a new mixin. While iterating through the nodes that should be
> updated, the following warning sometimes appears in the log:
> {{WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool]
> (ServerService Thread Pool -- 88) IJ000609: Attempt to return connection
> twice:
> org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@f6ff104[state=NORMAL
> managed
> connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7f3ceaf7
> connection handles=0 lastReturned=1715156332529 lastValidated=1715156332529
> lastCheckedOut=1715156332528 trackByTx=false
> pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@16cc91e8
> mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@53f6d09[pool=DezideAuthorJackrabbit]]:
> java.lang.Throwable: STACKTRACE}}
> I have attached a stacktrace.
> It seems that the database connection handled by the
> BundleDbPersistenceManager can in some situations be closed twice?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCR-5064) Update mockito dependency to 5.12.0
[ https://issues.apache.org/jira/browse/JCR-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849023#comment-17849023 ] Julian Reschke commented on JCR-5064: - trunk: [f16352ab1|https://github.com/apache/jackrabbit/commit/f16352ab1a996db8c41a10b1f1a787928218652e] > Update mockito dependency to 5.12.0 > --- > > Key: JCR-5064 > URL: https://issues.apache.org/jira/browse/JCR-5064 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: java11 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5064) Update mockito dependency to 5.12.0
[ https://issues.apache.org/jira/browse/JCR-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5064. - Fix Version/s: 2.21.27 Resolution: Fixed > Update mockito dependency to 5.12.0 > --- > > Key: JCR-5064 > URL: https://issues.apache.org/jira/browse/JCR-5064 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: java11 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5064) Update mockito dependency to 5.12.0
Julian Reschke created JCR-5064: --- Summary: Update mockito dependency to 5.12.0 Key: JCR-5064 URL: https://issues.apache.org/jira/browse/JCR-5064 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5064) Update mockito dependency to 5.12.0
[ https://issues.apache.org/jira/browse/JCR-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5064: Fix Version/s: (was: 2.21.26) > Update mockito dependency to 5.12.0 > --- > > Key: JCR-5064 > URL: https://issues.apache.org/jira/browse/JCR-5064 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: java11 > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5063) Update build-helper-maven-plugin to version 3.6.0
[ https://issues.apache.org/jira/browse/JCR-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848995#comment-17848995 ] Julian Reschke commented on JCR-5063: - trunk: [d381445a8|https://github.com/apache/jackrabbit/commit/d381445a8c11fd28b816d7a4b56e2735e6079087] > Update build-helper-maven-plugin to version 3.6.0 > - > > Key: JCR-5063 > URL: https://issues.apache.org/jira/browse/JCR-5063 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5063) Update build-helper-maven-plugin to version 3.6.0
[ https://issues.apache.org/jira/browse/JCR-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5063: Labels: candidate_jackrabbit_2.20 (was: ) > Update build-helper-maven-plugin to version 3.6.0 > - > > Key: JCR-5063 > URL: https://issues.apache.org/jira/browse/JCR-5063 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5063) Update build-helper-maven-plugin to version 3.6.0
[ https://issues.apache.org/jira/browse/JCR-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5063. - Fix Version/s: 2.21.27 Resolution: Fixed > Update build-helper-maven-plugin to version 3.6.0 > - > > Key: JCR-5063 > URL: https://issues.apache.org/jira/browse/JCR-5063 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5063) Update build-helper-maven-plugin to version 3.6.0
Julian Reschke created JCR-5063: --- Summary: Update build-helper-maven-plugin to version 3.6.0 Key: JCR-5063 URL: https://issues.apache.org/jira/browse/JCR-5063 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.23, 2.20.15 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5063) Update build-helper-maven-plugin to version 3.6.0
[ https://issues.apache.org/jira/browse/JCR-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5063: Fix Version/s: (was: 2.21.23) (was: 2.20.15) > Update build-helper-maven-plugin to version 3.6.0 > - > > Key: JCR-5063 > URL: https://issues.apache.org/jira/browse/JCR-5063 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5055) update Apache parent pom to version 32
[ https://issues.apache.org/jira/browse/JCR-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5055. - Resolution: Fixed > update Apache parent pom to version 32 > -- > > Key: JCR-5055 > URL: https://issues.apache.org/jira/browse/JCR-5055 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5062) Attempt to return connection twice
[
https://issues.apache.org/jira/browse/JCR-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847254#comment-17847254
]
Julian Reschke commented on JCR-5062:
-
Potentially.
Jackrabbit Classic is more on less on life support, with a few components still
in use outside (such as utils, spi, webdav). That is, almost no work is
happening on core components anymore.
Is there any chance to write a test case that reproduces this? Alternatively,
it might be helpful to add better diagnostics to the DB handling code.
PRs welcome :-)
> Attempt to return connection twice
> --
>
> Key: JCR-5062
> URL: https://issues.apache.org/jira/browse/JCR-5062
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Affects Versions: 2.20.16
>Reporter: Henrik Hald Nørgaard
>Priority: Minor
> Attachments: stacktrace.txt
>
>
> We are using a JackRabbit content repository and are going to update some
> nodes with a new mixin. While iterating through the nodes that should be
> updated, the following warning sometimes appears in the log:
> {{WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool]
> (ServerService Thread Pool -- 88) IJ000609: Attempt to return connection
> twice:
> org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@f6ff104[state=NORMAL
> managed
> connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@7f3ceaf7
> connection handles=0 lastReturned=1715156332529 lastValidated=1715156332529
> lastCheckedOut=1715156332528 trackByTx=false
> pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@16cc91e8
> mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@53f6d09[pool=DezideAuthorJackrabbit]]:
> java.lang.Throwable: STACKTRACE}}
> I have attached a stacktrace.
> It seems that the database connection handled by the
> BundleDbPersistenceManager can in some situations be closed twice?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCRVLT-754) check-release does not work for filevault anymore
[ https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846886#comment-17846886 ] Julian Reschke commented on JCRVLT-754: --- For the basenames, can we switch it for filevault maintenance releases as well, or would it better just to support both (by inspecting the release folder)? > check-release does not work for filevault anymore > - > > Key: JCRVLT-754 > URL: https://issues.apache.org/jira/browse/JCRVLT-754 > Project: Jackrabbit FileVault > Issue Type: Task >Reporter: Julian Reschke >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.7.4 > > > Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated > anymore; however, this is what is put into the generated vote template. > The proper fix likely would be to put the SHA512 checksum into the vote > template. > Furthermore, the basename of the source artefact changed from"src" to > "source-release". This needs to be adjusted in the check script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-754) check-release does not work for filevault anymore
[
https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846885#comment-17846885
]
Julian Reschke commented on JCRVLT-754:
---
Yes. So for the SHA1, the options appear to be:
- do not use it (put the SHA256 into the vote template)m or
- compute it on demand in check-release.
The latter would be something like:
{noformat}
@@ -175,6 +175,14 @@
SHA_OK=true
fi
done
+if [ $SHA_OK != 0 ]; then
+ # compute SHA1 of artefact and compare that
+ EXPECTED_SHA1="`openssl "sha1" "$BASEDIR/$RCDIR/$NAME" 2>> "$LOGFILE" | sed
's/.*= *//'`"
+ if [ $EXPECTED_SHA1 = $SHA ]; then
+info " (using computed SHA1 of $BASEDIR/$RCDIR/$NAME for SHA argument
comparison)"
+SHA_OK=true
+ fi
+fi
if $SHA_OK; then
info " OK: $SHA"
{noformat}
> check-release does not work for filevault anymore
> -
>
> Key: JCRVLT-754
> URL: https://issues.apache.org/jira/browse/JCRVLT-754
> Project: Jackrabbit FileVault
> Issue Type: Task
>Reporter: Julian Reschke
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.7.4
>
>
> Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated
> anymore; however, this is what is put into the generated vote template.
> The proper fix likely would be to put the SHA512 checksum into the vote
> template.
> Furthermore, the basename of the source artefact changed from"src" to
> "source-release". This needs to be adjusted in the check script.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JCRVLT-754) check-release does not work for filevault anymore
[
https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846885#comment-17846885
]
Julian Reschke edited comment on JCRVLT-754 at 5/16/24 9:12 AM:
Yes. So for the SHA1, the options appear to be:
- do not use it (put the SHA256 into the vote template) or
- compute it on demand in check-release.
The latter would be something like:
{noformat}
@@ -175,6 +175,14 @@
SHA_OK=true
fi
done
+if [ $SHA_OK != 0 ]; then
+ # compute SHA1 of artefact and compare that
+ EXPECTED_SHA1="`openssl "sha1" "$BASEDIR/$RCDIR/$NAME" 2>> "$LOGFILE" | sed
's/.*= *//'`"
+ if [ $EXPECTED_SHA1 = $SHA ]; then
+info " (using computed SHA1 of $BASEDIR/$RCDIR/$NAME for SHA argument
comparison)"
+SHA_OK=true
+ fi
+fi
if $SHA_OK; then
info " OK: $SHA"
{noformat}
was (Author: reschke):
Yes. So for the SHA1, the options appear to be:
- do not use it (put the SHA256 into the vote template)m or
- compute it on demand in check-release.
The latter would be something like:
{noformat}
@@ -175,6 +175,14 @@
SHA_OK=true
fi
done
+if [ $SHA_OK != 0 ]; then
+ # compute SHA1 of artefact and compare that
+ EXPECTED_SHA1="`openssl "sha1" "$BASEDIR/$RCDIR/$NAME" 2>> "$LOGFILE" | sed
's/.*= *//'`"
+ if [ $EXPECTED_SHA1 = $SHA ]; then
+info " (using computed SHA1 of $BASEDIR/$RCDIR/$NAME for SHA argument
comparison)"
+SHA_OK=true
+ fi
+fi
if $SHA_OK; then
info " OK: $SHA"
{noformat}
> check-release does not work for filevault anymore
> -
>
> Key: JCRVLT-754
> URL: https://issues.apache.org/jira/browse/JCRVLT-754
> Project: Jackrabbit FileVault
> Issue Type: Task
>Reporter: Julian Reschke
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.7.4
>
>
> Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated
> anymore; however, this is what is put into the generated vote template.
> The proper fix likely would be to put the SHA512 checksum into the vote
> template.
> Furthermore, the basename of the source artefact changed from"src" to
> "source-release". This needs to be adjusted in the check script.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCRVLT-754) check-release does not work for filevault anymore
[ https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-754: -- Fix Version/s: 3.7.4 > check-release does not work for filevault anymore > - > > Key: JCRVLT-754 > URL: https://issues.apache.org/jira/browse/JCRVLT-754 > Project: Jackrabbit FileVault > Issue Type: Task >Reporter: Julian Reschke >Priority: Major > Fix For: 3.7.4 > > > Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated > anymore; however, this is what is put into the generated vote template. > The proper fix likely would be to put the SHA512 checksum into the vote > template. > Furthermore, the basename of the source artefact changed from"src" to > "source-release". This needs to be adjusted in the check script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-754) check-release does not work for filevault anymore
[ https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-754: -- Description: Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated anymore; however, this is what is put into the generated vote template. The proper fix likely would be to put the SHA512 checksum into the vote template. Furthermore, the basename of the source artefact changed from"src" to "source-release". This needs to be adjusted in the check script. was: Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated anymore; however, this is what is put into the generated vote template. The proper fix likely would be to put the SHA512 checksum into the vote template. > check-release does not work for filevault anymore > - > > Key: JCRVLT-754 > URL: https://issues.apache.org/jira/browse/JCRVLT-754 > Project: Jackrabbit FileVault > Issue Type: Task >Reporter: Julian Reschke >Priority: Major > > Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated > anymore; however, this is what is put into the generated vote template. > The proper fix likely would be to put the SHA512 checksum into the vote > template. > Furthermore, the basename of the source artefact changed from"src" to > "source-release". This needs to be adjusted in the check script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Moved] (JCRVLT-754) check-release does not work for filevault anymore
[ https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke moved JCR-5061 to JCRVLT-754: Key: JCRVLT-754 (was: JCR-5061) Project: Jackrabbit FileVault (was: Jackrabbit Content Repository) > check-release does not work for filevault anymore > - > > Key: JCRVLT-754 > URL: https://issues.apache.org/jira/browse/JCRVLT-754 > Project: Jackrabbit FileVault > Issue Type: Task >Reporter: Julian Reschke >Priority: Major > > Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated > anymore; however, this is what is put into the generated vote template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-754) check-release does not work for filevault anymore
[ https://issues.apache.org/jira/browse/JCRVLT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-754: -- Description: Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated anymore; however, this is what is put into the generated vote template. The proper fix likely would be to put the SHA512 checksum into the vote template. was:Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated anymore; however, this is what is put into the generated vote template. > check-release does not work for filevault anymore > - > > Key: JCRVLT-754 > URL: https://issues.apache.org/jira/browse/JCRVLT-754 > Project: Jackrabbit FileVault > Issue Type: Task >Reporter: Julian Reschke >Priority: Major > > Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated > anymore; however, this is what is put into the generated vote template. > The proper fix likely would be to put the SHA512 checksum into the vote > template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5061) check-release does not work for filevault anymore
Julian Reschke created JCR-5061: --- Summary: check-release does not work for filevault anymore Key: JCR-5061 URL: https://issues.apache.org/jira/browse/JCR-5061 Project: Jackrabbit Content Repository Issue Type: Task Reporter: Julian Reschke Since https://issues.apache.org/jira/browse/JCRVLT-742, no sha1 is generated anymore; however, this is what is put into the generated vote template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-753) FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception in AEM Replication
[
https://issues.apache.org/jira/browse/JCRVLT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846706#comment-17846706
]
Julian Reschke commented on JCRVLT-753:
---
Re IT: actually, the system behaves as expected, so I wouldn't call it
"failing"...
> FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception
> in AEM Replication
> --
>
> Key: JCRVLT-753
> URL: https://issues.apache.org/jira/browse/JCRVLT-753
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Danilo Banjac
>Assignee: Konrad Windszus
>Priority: Major
> Labels: vault
>
> {*}Issue Description{*}:
> Recent updates to the replication conflict resolution strategy in Adobe
> Experience Manager (AEM) using JCR Filevault have led to failures when
> attempting to replicate content packages. Specifically, the shift from the
> *LEGACY* to the *FORCE_REMOVE_CONFLICTING_ID* strategy causes
> *javax.jcr.nodetype.ConstraintViolationException: OakConstraint0026* due to
> the attempted deletion of mandatory child nodes during the replication
> process.
> {*}Steps to Reproduce{*}:
> 1. Create a content package with a primary node of type *nt:file* and a
> mandatory child node {*}jcr:content{*}.
> 2. Update the version of the content package, ensuring the *jcr:uuid* of the
> *jcr:content* node remains unchanged.
> 3. Replicate the updated content package.
> {*}Observed Behavior{*}:
> - The replication framework attempts to remove the conflicting *jcr:content*
> node due to the identical {*}jcr:uuid{*}.
> - The deletion operation fails because the parent *nt:file* node requires the
> *jcr:content* child node, resulting in a {*}ConstraintViolationException{*}:
> "{*}Mandatory child node jcr:content cannot be removed.{*}"
> {*}Root Cause{*}:
> The *FORCE_REMOVE_CONFLICTING_ID* conflict resolution strategy does not
> account for the constraints of mandatory child nodes in the JCR repository,
> leading to violations when trying to remove these nodes.
> {*}Impact{*}:
> This issue prevents successful replication of updated content packages in
> AEM, disrupting content management workflows and generating errors in the log.
> *Nodes Used for Testing*
> {noformat}
> {
> "jcr:primaryType": "nt:file",
> "jcr:createdBy": "sling-distribution-importer",
> "jcr:created": "Tue May 14 2024 10:13:41 GMT+",
> "jcr:content": {
> "jcr:primaryType": "nt:resource",
> "jcr:mixinTypes": [
> "vlt:Package"
> ],
> "jcr:lastModifiedBy": "admin",
> "jcr:mimeType": "application/zip",
> "jcr:lastModified": "Tue May 14 2024 10:13:32 GMT+",
> ":jcr:data": 35146,
> "jcr:uuid": "cef51ff7-f3fc-4a41-b765-ca4ceb4246ce",
> "vlt:definition": {
> "jcr:primaryType": "vlt:PackageDefinition",
> "testedWith": "",
> "lastUnpacked": "Tue May 14 2024 10:13:41 GMT+",
> "lastUnpackedBy": "sling-distribution-importer",
> "requiresRestart": false,
> "requiresRoot": false,
> "lastWrapped": "Fri Apr 26 2024 12:27:44 GMT+",
> "buildCount": "17",
> "providerLink": "",
> "providerName": "",
> "jcr:created": "Fri Apr 26 2024 12:27:44 GMT+",
> "name": "global-truststore",
> "group": "admin-tasks",
> "version": "15.0",
> "dependencies": [],
> "fixedBugs": "",
> "jcr:lastModified": "Fri Apr 26 2024 12:27:44 GMT+",
> "lastUnwrapped": "Tue May 14 2024 10:13:32 GMT+",
> "providerUrl": "",
> "screenshots": {
> "jcr:primaryType": "nt:unstructured"
> },
> "filter": {
> "jcr:primaryType": "nt:unstructured",
> "f0": {
> "jcr:primaryType": "nt:unstructured",
> "propertyRules": [],
> "mode": "replace",
> "root": "/etc/truststore",
> "rules": []
> }
> }
> }
> }
> }{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JCRVLT-753) FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception in AEM Replication
[
https://issues.apache.org/jira/browse/JCRVLT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846587#comment-17846587
]
Julian Reschke edited comment on JCRVLT-753 at 5/15/24 11:32 AM:
-
So how could this be avoided without changing any code?
- change the parent node to be mix:referencable as well
- change the jcr:content child node not to be referenceable
- avoid renaming of nodes
- manually removing the conflicting node before replication
was (Author: reschke):
So how could this be avoided without changing any code?
- change the parent node to be mix:referencable as well
- avoid renaming of nodes
- manually removing the conflicting node before replication
> FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception
> in AEM Replication
> --
>
> Key: JCRVLT-753
> URL: https://issues.apache.org/jira/browse/JCRVLT-753
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Danilo Banjac
>Assignee: Konrad Windszus
>Priority: Major
> Labels: vault
>
> {*}Issue Description{*}:
> Recent updates to the replication conflict resolution strategy in Adobe
> Experience Manager (AEM) using JCR Filevault have led to failures when
> attempting to replicate content packages. Specifically, the shift from the
> *LEGACY* to the *FORCE_REMOVE_CONFLICTING_ID* strategy causes
> *javax.jcr.nodetype.ConstraintViolationException: OakConstraint0026* due to
> the attempted deletion of mandatory child nodes during the replication
> process.
> {*}Steps to Reproduce{*}:
> 1. Create a content package with a primary node of type *nt:file* and a
> mandatory child node {*}jcr:content{*}.
> 2. Update the version of the content package, ensuring the *jcr:uuid* of the
> *jcr:content* node remains unchanged.
> 3. Replicate the updated content package.
> {*}Observed Behavior{*}:
> - The replication framework attempts to remove the conflicting *jcr:content*
> node due to the identical {*}jcr:uuid{*}.
> - The deletion operation fails because the parent *nt:file* node requires the
> *jcr:content* child node, resulting in a {*}ConstraintViolationException{*}:
> "{*}Mandatory child node jcr:content cannot be removed.{*}"
> {*}Root Cause{*}:
> The *FORCE_REMOVE_CONFLICTING_ID* conflict resolution strategy does not
> account for the constraints of mandatory child nodes in the JCR repository,
> leading to violations when trying to remove these nodes.
> {*}Impact{*}:
> This issue prevents successful replication of updated content packages in
> AEM, disrupting content management workflows and generating errors in the log.
> *Nodes Used for Testing*
> {noformat}
> {
> "jcr:primaryType": "nt:file",
> "jcr:createdBy": "sling-distribution-importer",
> "jcr:created": "Tue May 14 2024 10:13:41 GMT+",
> "jcr:content": {
> "jcr:primaryType": "nt:resource",
> "jcr:mixinTypes": [
> "vlt:Package"
> ],
> "jcr:lastModifiedBy": "admin",
> "jcr:mimeType": "application/zip",
> "jcr:lastModified": "Tue May 14 2024 10:13:32 GMT+",
> ":jcr:data": 35146,
> "jcr:uuid": "cef51ff7-f3fc-4a41-b765-ca4ceb4246ce",
> "vlt:definition": {
> "jcr:primaryType": "vlt:PackageDefinition",
> "testedWith": "",
> "lastUnpacked": "Tue May 14 2024 10:13:41 GMT+",
> "lastUnpackedBy": "sling-distribution-importer",
> "requiresRestart": false,
> "requiresRoot": false,
> "lastWrapped": "Fri Apr 26 2024 12:27:44 GMT+",
> "buildCount": "17",
> "providerLink": "",
> "providerName": "",
> "jcr:created": "Fri Apr 26 2024 12:27:44 GMT+",
> "name": "global-truststore",
> "group": "admin-tasks",
> "version": "15.0",
> "dependencies": [],
> "fixedBugs": "",
> "jcr:lastModified": "Fri Apr 26 2024 12:27:44 GMT+",
> "lastUnwrapped": "Tue May 14 2024 10:13:32 GMT+",
> "providerUrl": "",
> "screenshots": {
> "jcr:primaryType": "nt:unstructured"
> },
> "filter": {
> "jcr:primaryType": "nt:unstructured",
> "f0": {
> "jcr:primaryType": "nt:unstructured",
> "propertyRules": [],
> "mode": "replace",
> "root": "/etc/truststore",
> "rules": []
> }
> }
> }
> }
> }{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCRVLT-753) FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception in AEM Replication
[
https://issues.apache.org/jira/browse/JCRVLT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846587#comment-17846587
]
Julian Reschke commented on JCRVLT-753:
---
So how could this be avoided without changing any code?
- change the parent node to be mix:referencable as well
- avoid renaming of nodes
- manually removing the conflicting node before replication
> FORCE_REMOVE_CONFLICTING_ID Strategy Causing Constraint Violation Exception
> in AEM Replication
> --
>
> Key: JCRVLT-753
> URL: https://issues.apache.org/jira/browse/JCRVLT-753
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Danilo Banjac
>Assignee: Konrad Windszus
>Priority: Major
> Labels: vault
>
> {*}Issue Description{*}:
> Recent updates to the replication conflict resolution strategy in Adobe
> Experience Manager (AEM) using JCR Filevault have led to failures when
> attempting to replicate content packages. Specifically, the shift from the
> *LEGACY* to the *FORCE_REMOVE_CONFLICTING_ID* strategy causes
> *javax.jcr.nodetype.ConstraintViolationException: OakConstraint0026* due to
> the attempted deletion of mandatory child nodes during the replication
> process.
> {*}Steps to Reproduce{*}:
> 1. Create a content package with a primary node of type *nt:file* and a
> mandatory child node {*}jcr:content{*}.
> 2. Update the version of the content package, ensuring the *jcr:uuid* of the
> *jcr:content* node remains unchanged.
> 3. Replicate the updated content package.
> {*}Observed Behavior{*}:
> - The replication framework attempts to remove the conflicting *jcr:content*
> node due to the identical {*}jcr:uuid{*}.
> - The deletion operation fails because the parent *nt:file* node requires the
> *jcr:content* child node, resulting in a {*}ConstraintViolationException{*}:
> "{*}Mandatory child node jcr:content cannot be removed.{*}"
> {*}Root Cause{*}:
> The *FORCE_REMOVE_CONFLICTING_ID* conflict resolution strategy does not
> account for the constraints of mandatory child nodes in the JCR repository,
> leading to violations when trying to remove these nodes.
> {*}Impact{*}:
> This issue prevents successful replication of updated content packages in
> AEM, disrupting content management workflows and generating errors in the log.
> *Nodes Used for Testing*
> {noformat}
> {
> "jcr:primaryType": "nt:file",
> "jcr:createdBy": "sling-distribution-importer",
> "jcr:created": "Tue May 14 2024 10:13:41 GMT+",
> "jcr:content": {
> "jcr:primaryType": "nt:resource",
> "jcr:mixinTypes": [
> "vlt:Package"
> ],
> "jcr:lastModifiedBy": "admin",
> "jcr:mimeType": "application/zip",
> "jcr:lastModified": "Tue May 14 2024 10:13:32 GMT+",
> ":jcr:data": 35146,
> "jcr:uuid": "cef51ff7-f3fc-4a41-b765-ca4ceb4246ce",
> "vlt:definition": {
> "jcr:primaryType": "vlt:PackageDefinition",
> "testedWith": "",
> "lastUnpacked": "Tue May 14 2024 10:13:41 GMT+",
> "lastUnpackedBy": "sling-distribution-importer",
> "requiresRestart": false,
> "requiresRoot": false,
> "lastWrapped": "Fri Apr 26 2024 12:27:44 GMT+",
> "buildCount": "17",
> "providerLink": "",
> "providerName": "",
> "jcr:created": "Fri Apr 26 2024 12:27:44 GMT+",
> "name": "global-truststore",
> "group": "admin-tasks",
> "version": "15.0",
> "dependencies": [],
> "fixedBugs": "",
> "jcr:lastModified": "Fri Apr 26 2024 12:27:44 GMT+",
> "lastUnwrapped": "Tue May 14 2024 10:13:32 GMT+",
> "providerUrl": "",
> "screenshots": {
> "jcr:primaryType": "nt:unstructured"
> },
> "filter": {
> "jcr:primaryType": "nt:unstructured",
> "f0": {
> "jcr:primaryType": "nt:unstructured",
> "propertyRules": [],
> "mode": "replace",
> "root": "/etc/truststore",
> "rules": []
> }
> }
> }
> }
> }{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCRVLT-659) Warn for different prefixes used in FileVault XML and importing repo
[ https://issues.apache.org/jira/browse/JCRVLT-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-659: -- Fix Version/s: 3.7.6 (was: 3.7.4) > Warn for different prefixes used in FileVault XML and importing repo > > > Key: JCRVLT-659 > URL: https://issues.apache.org/jira/browse/JCRVLT-659 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: Packaging >Reporter: Konrad Windszus >Priority: Major > Fix For: 3.7.6 > > > Due to the reasons outlined at > https://jackrabbit.apache.org/filevault/nodetypes.html#namespace-prefixes > different namespace mappings (i.e. other prefixes for used namespace URIs) > may lead to subtle issues and should therefore always lead to a WARN during > import. > Maybe one should even fail the installation in Strict mode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-716) Prevent duplicate validation issues for subpackage validation
[ https://issues.apache.org/jira/browse/JCRVLT-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-716: -- Fix Version/s: 3.7.6 (was: 3.7.4) > Prevent duplicate validation issues for subpackage validation > - > > Key: JCRVLT-716 > URL: https://issues.apache.org/jira/browse/JCRVLT-716 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: validation >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.7.6 > > > Often a validator is called twice on the same package: > * In the context of a standalone package (triggered from a non-container > Maven module) > * In the context as subpackage inside a container module > Currently lots of validators emit duplicate reports and also settings often > needs to be copied over to the container package. > Therefore with default settings validators should prevent emitting issues > twice but preferably only in the first context. The second context should > only emit issues which cannot be detected for the standalone case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-619) Allow to define node types per validRoot and leverage it from validator: jackrabbit-nodetype
[ https://issues.apache.org/jira/browse/JCRVLT-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-619: -- Fix Version/s: 3.7.6 (was: 3.7.4) > Allow to define node types per validRoot and leverage it from validator: > jackrabbit-nodetype > > > Key: JCRVLT-619 > URL: https://issues.apache.org/jira/browse/JCRVLT-619 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Konrad Windszus >Priority: Major > Fix For: 3.7.6 > > > It would be good to allow to define it in an external Maven artifact so that > these definitions could be provided per distribution/version. Also it should > be possible to allow definitions which are derived from some other metadata > (like [Sling Repo Init > statements|https://sling.apache.org/documentation/bundles/repository-initialization.html]). > Both means should be allowed at the same time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-523) Expose subpackages from RegisteredPackage
[ https://issues.apache.org/jira/browse/JCRVLT-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-523: -- Fix Version/s: 3.7.6 (was: 3.7.4) > Expose subpackages from RegisteredPackage > - > > Key: JCRVLT-523 > URL: https://issues.apache.org/jira/browse/JCRVLT-523 > Project: Jackrabbit FileVault > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: 3.7.6 > > > There should be a method which exposes all direct subpackages of an existing > package. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-524) JcrPackageRegistry.register should always register the subpackages as well
[
https://issues.apache.org/jira/browse/JCRVLT-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCRVLT-524:
--
Fix Version/s: 3.7.6
(was: 3.7.4)
> JcrPackageRegistry.register should always register the subpackages as well
> --
>
> Key: JCRVLT-524
> URL: https://issues.apache.org/jira/browse/JCRVLT-524
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: 3.7.6
>
>
> The {{FSPackageRegistry}} already registers all contained subpackages with a
> call to {{PackageRegistry.register(...)}}
> (https://github.com/apache/jackrabbit-filevault/blob/14615ce5647252005f2271b5f5f0351eb91aa78e/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/registry/impl/FSPackageRegistry.java#L362)
> both for internal and external files, while
> {{JcrPackageRegistry.register(...)}} does not do that
> (https://github.com/apache/jackrabbit-filevault/blob/14615ce5647252005f2271b5f5f0351eb91aa78e/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/registry/impl/JcrPackageRegistry.java#L348).
> The handling should be consolidated so that all implementations always
> register also the contained subpackages and the javadoc of
> {{PackageRegistry.register(...)}} clarified accordingly.
> Registering subpackages probably requires extracting them from the container
> package and store as dedicated package which leads to increased memory
> consumption.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCRVLT-522) Authorizable and authorization nodes applied even if filter rules exclude them
[
https://issues.apache.org/jira/browse/JCRVLT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCRVLT-522:
--
Fix Version/s: 3.7.6
(was: 3.7.4)
> Authorizable and authorization nodes applied even if filter rules exclude them
> --
>
> Key: JCRVLT-522
> URL: https://issues.apache.org/jira/browse/JCRVLT-522
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
>Affects Versions: 3.4.10
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.7.6
>
>
> Currently the filter rules are not fully evaluated prior to applying ACLs (in
> rep:policy and rep:repoPolicy files). According to JCRVLT-372 this is a bug.
> The same is true for authorizable nodes (compare with JCRVLT-71).
> The exact install behaviour is as follows (given that the ACHandling is not
> IGNORE):
>
> || ||ACL Path in Filter?||Effect||Example ACL Path(s)||Example Content Node
> Path(s)||
> ||1|Contained in
> filter|Installed|/testroot/node_a/rep:policy|/testroot/node_a||
> ||2|Not contained in filter, but ancestor is
> contained|Installed|/testroot/secured/rep:policy|testroot/secured||
> ||3|Neither path nor ancestor is contained in filter|Not
> Installed|/test2/rep:policy|/test2||
> ||4|Path is not contained in filter, ancestor is not contained either, but
> node affected by ACLs is contained|Not
> Installed|/testroot/rep:policy|/testroot||
> The example columns assume the following filter.xml
> {code}
>
>
>
>
>
>
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (JCRVLT-752) Release Jackrabbit Filevault 3.7.4
Julian Reschke created JCRVLT-752: - Summary: Release Jackrabbit Filevault 3.7.4 Key: JCRVLT-752 URL: https://issues.apache.org/jira/browse/JCRVLT-752 Project: Jackrabbit FileVault Issue Type: Task Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCRVLT-745) Stashing: naming and folder location
[ https://issues.apache.org/jira/browse/JCRVLT-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCRVLT-745. --- Fix Version/s: 3.7.4 Resolution: Fixed > Stashing: naming and folder location > > > Key: JCRVLT-745 > URL: https://issues.apache.org/jira/browse/JCRVLT-745 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 3.7.4 > > > We have seen cases where node stashing failed due to RuntimeExceptions (OOM > or MongoDB issues in Oak). In these cases, the tmp folder is not cleaned up. > If the operation is retried many times, there'll be many of these. > Suggestion: > 1. Do not use the root as default location, > 2. Introduce an intermediary node that makes it clear that this is temp space > created by FileVault. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5060) Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20
[ https://issues.apache.org/jira/browse/JCR-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846004#comment-17846004 ] Julian Reschke commented on JCR-5060: - trunk: [b59edd356|https://github.com/apache/jackrabbit-oak/commit/b59edd356a36948eadcf1b956459c13d767f1b4a] > Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20 > --- > > Key: JCR-5060 > URL: https://issues.apache.org/jira/browse/JCR-5060 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5060) Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20
[ https://issues.apache.org/jira/browse/JCR-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5060. - Fix Version/s: 2.21.27 Resolution: Fixed > Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20 > --- > > Key: JCR-5060 > URL: https://issues.apache.org/jira/browse/JCR-5060 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5060) Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20
[ https://issues.apache.org/jira/browse/JCR-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5060: Labels: candidate_jackrabbit_2.20 (was: ) > Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20 > --- > > Key: JCR-5060 > URL: https://issues.apache.org/jira/browse/JCR-5060 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5060) Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20
[ https://issues.apache.org/jira/browse/JCR-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5060: Summary: Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20 (was: CLONE - Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20) > Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20 > --- > > Key: JCR-5060 > URL: https://issues.apache.org/jira/browse/JCR-5060 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5060) CLONE - Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20
Julian Reschke created JCR-5060: --- Summary: CLONE - Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20 Key: JCR-5060 URL: https://issues.apache.org/jira/browse/JCR-5060 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5060) CLONE - Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak 1.22.20
[ https://issues.apache.org/jira/browse/JCR-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5060: Fix Version/s: (was: 2.21.26) > CLONE - Update oak-jackrabbit-api.version.used in trunk and 2.20 to Oak > 1.22.20 > --- > > Key: JCR-5060 > URL: https://issues.apache.org/jira/browse/JCR-5060 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5059) set baseline comparisonVersion to latest stable (2.20.16)
[ https://issues.apache.org/jira/browse/JCR-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845782#comment-17845782 ] Julian Reschke commented on JCR-5059: - trunk: [b7a674b38|https://github.com/apache/jackrabbit-oak/commit/b7a674b3886990dab79e2afa827113311e714696] > set baseline comparisonVersion to latest stable (2.20.16) > - > > Key: JCR-5059 > URL: https://issues.apache.org/jira/browse/JCR-5059 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5059) set baseline comparisonVersion to latest stable (2.20.16)
[ https://issues.apache.org/jira/browse/JCR-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5059. - Fix Version/s: 2.21.27 Resolution: Fixed > set baseline comparisonVersion to latest stable (2.20.16) > - > > Key: JCR-5059 > URL: https://issues.apache.org/jira/browse/JCR-5059 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5059) set baseline comparisonVersion to latest stable (2.20.16)
Julian Reschke created JCR-5059: --- Summary: set baseline comparisonVersion to latest stable (2.20.16) Key: JCR-5059 URL: https://issues.apache.org/jira/browse/JCR-5059 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.26 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5059) set baseline comparisonVersion to latest stable (2.20.16)
[ https://issues.apache.org/jira/browse/JCR-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5059: Fix Version/s: (was: 2.21.26) > set baseline comparisonVersion to latest stable (2.20.16) > - > > Key: JCR-5059 > URL: https://issues.apache.org/jira/browse/JCR-5059 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-745) Stashing: naming and folder location
[ https://issues.apache.org/jira/browse/JCRVLT-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844641#comment-17844641 ] Julian Reschke commented on JCRVLT-745: --- [~joscorbe] - in theory this shouldn't be a problem if the nodes indeed were temporary. What we found is that the stashing operation was failing due to a combination of issues (Oak document store handling of ordered children, and cleanup of intermediate commits). When it fails, it indeed leaves things where they are, and I'm not sure it would be good if FV tried to handle that. That said, I'm planning to make a PR that changes the order of locations where the temp node creation is attempted (so "/" is last), and also improves naming of these nodes (for more information should they stick). > Stashing: naming and folder location > > > Key: JCRVLT-745 > URL: https://issues.apache.org/jira/browse/JCRVLT-745 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > > We have seen cases where node stashing failed due to RuntimeExceptions (OOM > or MongoDB issues in Oak). In these cases, the tmp folder is not cleaned up. > If the operation is retried many times, there'll be many of these. > Suggestion: > 1. Do not use the root as default location, > 2. Introduce an intermediary node that makes it clear that this is temp space > created by FileVault. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5058) Update spotbugs-maven-plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/JCR-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844402#comment-17844402 ] Julian Reschke commented on JCR-5058: - trunk: [3969652e4|https://github.com/apache/jackrabbit-oak/commit/3969652e414211b459b084c5331530f81754399f] > Update spotbugs-maven-plugin to 4.8.5.0 > --- > > Key: JCR-5058 > URL: https://issues.apache.org/jira/browse/JCR-5058 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5058) Update spotbugs-maven-plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/JCR-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5058: Labels: candidate_jackrabbit_2.20 (was: ) > Update spotbugs-maven-plugin to 4.8.5.0 > --- > > Key: JCR-5058 > URL: https://issues.apache.org/jira/browse/JCR-5058 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5058) Update spotbugs-maven-plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/JCR-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5058. - Fix Version/s: 2.21.27 Resolution: Fixed > Update spotbugs-maven-plugin to 4.8.5.0 > --- > > Key: JCR-5058 > URL: https://issues.apache.org/jira/browse/JCR-5058 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5058) Update spotbugs-maven-plugin to 4.8.5.0
[ https://issues.apache.org/jira/browse/JCR-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5058: Fix Version/s: (was: 2.21.26) (was: 2.20.16) > Update spotbugs-maven-plugin to 4.8.5.0 > --- > > Key: JCR-5058 > URL: https://issues.apache.org/jira/browse/JCR-5058 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5058) Update spotbugs-maven-plugin to 4.8.5.0
Julian Reschke created JCR-5058: --- Summary: Update spotbugs-maven-plugin to 4.8.5.0 Key: JCR-5058 URL: https://issues.apache.org/jira/browse/JCR-5058 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.26, 2.20.16 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5057) Update pmd-plugin dependency to 3.22.0
[ https://issues.apache.org/jira/browse/JCR-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844383#comment-17844383 ] Julian Reschke commented on JCR-5057: - trunk: [8f98b9521|https://github.com/apache/jackrabbit-oak/commit/8f98b9521b8cabb3ff5e28f59133631a30c70180] > Update pmd-plugin dependency to 3.22.0 > -- > > Key: JCR-5057 > URL: https://issues.apache.org/jira/browse/JCR-5057 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5057) Update pmd-plugin dependency to 3.22.0
[ https://issues.apache.org/jira/browse/JCR-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5057. - Fix Version/s: 2.21.27 Resolution: Fixed > Update pmd-plugin dependency to 3.22.0 > -- > > Key: JCR-5057 > URL: https://issues.apache.org/jira/browse/JCR-5057 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5057) Update pmd-plugin dependency to 3.22.0
[ https://issues.apache.org/jira/browse/JCR-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5057: Labels: candidate_jackrabbit_2.20 (was: ) > Update pmd-plugin dependency to 3.22.0 > -- > > Key: JCR-5057 > URL: https://issues.apache.org/jira/browse/JCR-5057 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5057) Update pmd-plugin dependency to 3.22.0
[ https://issues.apache.org/jira/browse/JCR-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5057: Fix Version/s: (was: 2.21.21) (was: 2.20.14) > Update pmd-plugin dependency to 3.22.0 > -- > > Key: JCR-5057 > URL: https://issues.apache.org/jira/browse/JCR-5057 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5057) Update pmd-plugin dependency to 3.22.0
Julian Reschke created JCR-5057: --- Summary: Update pmd-plugin dependency to 3.22.0 Key: JCR-5057 URL: https://issues.apache.org/jira/browse/JCR-5057 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.21, 2.20.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5056) Update maven-jar-plugin to 3.4.1
[ https://issues.apache.org/jira/browse/JCR-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844371#comment-17844371 ] Julian Reschke commented on JCR-5056: - trunk: [c6597ddd8|https://github.com/apache/jackrabbit-oak/commit/c6597ddd8fc0c1f4efabf0ee49d5918c3344763f] > Update maven-jar-plugin to 3.4.1 > > > Key: JCR-5056 > URL: https://issues.apache.org/jira/browse/JCR-5056 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5056) Update maven-jar-plugin to 3.4.1
[ https://issues.apache.org/jira/browse/JCR-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5056: Labels: candidate_jackrabbit_2.20 (was: ) > Update maven-jar-plugin to 3.4.1 > > > Key: JCR-5056 > URL: https://issues.apache.org/jira/browse/JCR-5056 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5056) Update maven-jar-plugin to 3.4.1
[ https://issues.apache.org/jira/browse/JCR-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5056. - Fix Version/s: 2.21.27 Resolution: Fixed > Update maven-jar-plugin to 3.4.1 > > > Key: JCR-5056 > URL: https://issues.apache.org/jira/browse/JCR-5056 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5056) Update maven-jar-plugin to 3.4.1
[ https://issues.apache.org/jira/browse/JCR-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5056: Fix Version/s: (was: 2.21.15) (was: 2.20.9) > Update maven-jar-plugin to 3.4.1 > > > Key: JCR-5056 > URL: https://issues.apache.org/jira/browse/JCR-5056 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5056) Update maven-jar-plugin to 3.4.1
Julian Reschke created JCR-5056: --- Summary: Update maven-jar-plugin to 3.4.1 Key: JCR-5056 URL: https://issues.apache.org/jira/browse/JCR-5056 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.15, 2.20.9 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5055) update Apache parent pom to version 32
[ https://issues.apache.org/jira/browse/JCR-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844355#comment-17844355 ] Julian Reschke commented on JCR-5055: - trunk: [e9f0eaf82|https://github.com/apache/jackrabbit-oak/commit/e9f0eaf827c9a9044d283be45ecb3014d9117a2b] > update Apache parent pom to version 32 > -- > > Key: JCR-5055 > URL: https://issues.apache.org/jira/browse/JCR-5055 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5055) update Apache parent pom to version 32
[ https://issues.apache.org/jira/browse/JCR-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5055: Labels: candidate_jackrabbit_2.20 (was: ) > update Apache parent pom to version 32 > -- > > Key: JCR-5055 > URL: https://issues.apache.org/jira/browse/JCR-5055 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5055) update Apache parent pom to version 32
[ https://issues.apache.org/jira/browse/JCR-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5055: Fix Version/s: 2.21.27 > update Apache parent pom to version 32 > -- > > Key: JCR-5055 > URL: https://issues.apache.org/jira/browse/JCR-5055 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5055) update Apache parent pom to version 32
Julian Reschke created JCR-5055: --- Summary: update Apache parent pom to version 32 Key: JCR-5055 URL: https://issues.apache.org/jira/browse/JCR-5055 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.21 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5055) update Apache parent pom to version 32
[ https://issues.apache.org/jira/browse/JCR-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5055: Fix Version/s: (was: 2.21.21) > update Apache parent pom to version 32 > -- > > Key: JCR-5055 > URL: https://issues.apache.org/jira/browse/JCR-5055 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5000) update Apache parent pom to version 31
[ https://issues.apache.org/jira/browse/JCR-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5000: Labels: candidate_jackrabbit_2.20 (was: ) > update Apache parent pom to version 31 > -- > > Key: JCR-5000 > URL: https://issues.apache.org/jira/browse/JCR-5000 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.21 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5054) vfs-ext: update hadoop-hdfs-client dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844329#comment-17844329 ] Julian Reschke commented on JCR-5054: - trunk: [9c5f6dc43|https://github.com/apache/jackrabbit-oak/commit/9c5f6dc4349a2b346bfc8e45958b3eff31fd98ac] > vfs-ext: update hadoop-hdfs-client dependency to 3.4.0 > -- > > Key: JCR-5054 > URL: https://issues.apache.org/jira/browse/JCR-5054 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-vfs-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5054) vfs-ext: update hadoop-hdfs-client dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5054. - Fix Version/s: 2.21.27 Resolution: Fixed > vfs-ext: update hadoop-hdfs-client dependency to 3.4.0 > -- > > Key: JCR-5054 > URL: https://issues.apache.org/jira/browse/JCR-5054 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-vfs-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5054) vfs-ext: update hadoop-hdfs-client dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5054: Labels: candidate_jackrabbit_2.20 (was: ) > vfs-ext: update hadoop-hdfs-client dependency to 3.4.0 > -- > > Key: JCR-5054 > URL: https://issues.apache.org/jira/browse/JCR-5054 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-vfs-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5054) vfs-ext: update hadoop-hdfs-client dependency to 3.4.0
Julian Reschke created JCR-5054: --- Summary: vfs-ext: update hadoop-hdfs-client dependency to 3.4.0 Key: JCR-5054 URL: https://issues.apache.org/jira/browse/JCR-5054 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-vfs-ext Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.20.12, 2.21.19 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5054) vfs-ext: update hadoop-hdfs-client dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5054: Fix Version/s: (was: 2.20.12) (was: 2.21.19) > vfs-ext: update hadoop-hdfs-client dependency to 3.4.0 > -- > > Key: JCR-5054 > URL: https://issues.apache.org/jira/browse/JCR-5054 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-vfs-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5053) Update commons-cli dependency to 1.7.0
[ https://issues.apache.org/jira/browse/JCR-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844318#comment-17844318 ] Julian Reschke commented on JCR-5053: - trunk: [290264af9|https://github.com/apache/jackrabbit-oak/commit/290264af9bf615a36a38cf7ff11f675c141e3ab7] > Update commons-cli dependency to 1.7.0 > -- > > Key: JCR-5053 > URL: https://issues.apache.org/jira/browse/JCR-5053 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5053) Update commons-cli dependency to 1.7.0
[ https://issues.apache.org/jira/browse/JCR-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5053. - Fix Version/s: 2.21.27 Resolution: Fixed > Update commons-cli dependency to 1.7.0 > -- > > Key: JCR-5053 > URL: https://issues.apache.org/jira/browse/JCR-5053 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5053) Update commons-cli dependency to 1.7.0
Julian Reschke created JCR-5053: --- Summary: Update commons-cli dependency to 1.7.0 Key: JCR-5053 URL: https://issues.apache.org/jira/browse/JCR-5053 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-standalone Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.21, 2.20.14 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5053) Update commons-cli dependency to 1.7.0
[ https://issues.apache.org/jira/browse/JCR-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5053: Fix Version/s: (was: 2.21.21) (was: 2.20.14) > Update commons-cli dependency to 1.7.0 > -- > > Key: JCR-5053 > URL: https://issues.apache.org/jira/browse/JCR-5053 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5053) Update commons-cli dependency to 1.7.0
[ https://issues.apache.org/jira/browse/JCR-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5053: Labels: candidate_jackrabbit_2.20 (was: ) > Update commons-cli dependency to 1.7.0 > -- > > Key: JCR-5053 > URL: https://issues.apache.org/jira/browse/JCR-5053 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5052) Update commons-io dependency to 2.16.1
[ https://issues.apache.org/jira/browse/JCR-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844293#comment-17844293 ] Julian Reschke commented on JCR-5052: - trunk: [c419176e8|https://github.com/apache/jackrabbit-oak/commit/c419176e819d5499f90a25705899641fd043ede6] > Update commons-io dependency to 2.16.1 > -- > > Key: JCR-5052 > URL: https://issues.apache.org/jira/browse/JCR-5052 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5052) Update commons-io dependency to 2.16.1
[ https://issues.apache.org/jira/browse/JCR-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5052. - Fix Version/s: 2.21.27 Resolution: Fixed > Update commons-io dependency to 2.16.1 > -- > > Key: JCR-5052 > URL: https://issues.apache.org/jira/browse/JCR-5052 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5052) Update commons-io dependency to 2.16.1
Julian Reschke created JCR-5052: --- Summary: Update commons-io dependency to 2.16.1 Key: JCR-5052 URL: https://issues.apache.org/jira/browse/JCR-5052 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5052) Update commons-io dependency to 2.16.1
[ https://issues.apache.org/jira/browse/JCR-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5052: Fix Version/s: (was: 2.21.27) > Update commons-io dependency to 2.16.1 > -- > > Key: JCR-5052 > URL: https://issues.apache.org/jira/browse/JCR-5052 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5051) ISO9075.encodePath/encode should preserve wildcard
[
https://issues.apache.org/jira/browse/JCR-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843809#comment-17843809
]
Julian Reschke commented on JCR-5051:
-
Changing the behavior sounds risky to me.
Adding a new method and improving the documentation sounds reasonable.
> ISO9075.encodePath/encode should preserve wildcard
> --
>
> Key: JCR-5051
> URL: https://issues.apache.org/jira/browse/JCR-5051
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-jcr-commons
>Reporter: Konrad Windszus
>Priority: Major
>
> Currently the wildcard {{"*"}} is escaped as well to {{"_x002a_"}}.
> This is not intended as in the context of XPath the wildcard is an allowed
> character in the grammar
> (https://www.w3.org/TR/xpath20/#prod-xpath-ElementNameOrWildcard).
> Not sure if ISO9075 is used for other purposes so it might be better to
> explicitly add another method to keep the wildcard in place.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (JCR-5050) Release Jackrabbit 2.20.16
Julian Reschke created JCR-5050: --- Summary: Release Jackrabbit 2.20.16 Key: JCR-5050 URL: https://issues.apache.org/jira/browse/JCR-5050 Project: Jackrabbit Content Repository Issue Type: Task Reporter: Julian Reschke Assignee: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5049) Remove "CopyOfAbstractLInkedList" pending resolution of COLLECTIONS-842
[ https://issues.apache.org/jira/browse/JCR-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5049: Summary: Remove "CopyOfAbstractLInkedList" pending resolution of COLLECTIONS-842 (was: Remove "CopyOfAbstractLInkedList" pendig resolution of COLLECTIONS-842) > Remove "CopyOfAbstractLInkedList" pending resolution of COLLECTIONS-842 > --- > > Key: JCR-5049 > URL: https://issues.apache.org/jira/browse/JCR-5049 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-jcr2spi >Reporter: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5049) Remove "CopyOfAbstractLInkedList" pendig resolution of COLLECTIONS-842
Julian Reschke created JCR-5049: --- Summary: Remove "CopyOfAbstractLInkedList" pendig resolution of COLLECTIONS-842 Key: JCR-5049 URL: https://issues.apache.org/jira/browse/JCR-5049 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-jcr2spi Reporter: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-751) Can't import a user with parent folder that starts with _ and includes another _
[ https://issues.apache.org/jira/browse/JCRVLT-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840153#comment-17840153 ] Julian Reschke commented on JCRVLT-751: --- OK, so then the question is: what was the package created with? > Can't import a user with parent folder that starts with _ and includes > another _ > - > > Key: JCRVLT-751 > URL: https://issues.apache.org/jira/browse/JCRVLT-751 > Project: Jackrabbit FileVault > Issue Type: Bug > Components: vlt >Affects Versions: 3.7.2 >Reporter: Timothée Maret >Priority: Major > Labels: vault > > AEM has a user synchronisation capability in the publish tier. The > synchronisation mechanism relies on FileVault to export and import content. > Users stored in the repository under a path that starts with a _ and that > contain another _ can be exported but fail to be re-imported. For instance, > the user stored under the path /home/users/test/_6k_test-user-a won't be > imported. > Debugging this issue, it seems that FileVault treats the _6k_ pattern as a > namespace and thus skip the resource upon import because the paths don't > match. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-745) Stashing: naming and folder location
[ https://issues.apache.org/jira/browse/JCRVLT-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-745: -- Description: We have seen cases where node stashing failed due to RuntimeExceptions (OOM or MongoDB issues in Oak). In these cases, the tmp folder is not cleaned up. If the operation is retried many times, there'll be many of these. Suggestion: 1. Do not use the root as default location, 2. Introduce an intermediary node that makes it clear that this is temp space created by FileVault. was: We have seen cases where node stashing failed due to RuntimeExceptions (OOM or MongoDB issues in Oak). In these cases, the tmp folder is not cleaned up. If the operation is retried many times, there'll be many of these. Suggestion: 1. Do not use the root as default location, 2. Introduce an intermediary node that makes it clear that this is temp space created by FileVault. > Stashing: naming and folder location > > > Key: JCRVLT-745 > URL: https://issues.apache.org/jira/browse/JCRVLT-745 > Project: Jackrabbit FileVault > Issue Type: Improvement > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > > We have seen cases where node stashing failed due to RuntimeExceptions (OOM > or MongoDB issues in Oak). In these cases, the tmp folder is not cleaned up. > If the operation is retried many times, there'll be many of these. > Suggestion: > 1. Do not use the root as default location, > 2. Introduce an intermediary node that makes it clear that this is temp space > created by FileVault. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5048) Jackrabbit should build and test with Java 23
[
https://issues.apache.org/jira/browse/JCR-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-5048:
Fix Version/s: 2.21.28
> Jackrabbit should build and test with Java 23
> -
>
> Key: JCR-5048
> URL: https://issues.apache.org/jira/browse/JCR-5048
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.21.28
>
>
> Right now:
> {noformat}
> Caused by: java.lang.IllegalStateException:
> Byte Buddy could not instrument all classes within the mock's type hierarchy
> This problem should never occur for javac-compiled classes. This problem has
> been observed for classes that are:
> - Compiled by older versions of scalac
> - Classes that are part of the Android distribution
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:75)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:414)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:373)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:352)
> at
> org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
> at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:99)
> at org.mockito.internal.MockitoCore.mock(MockitoCore.java:84)
> at org.mockito.Mockito.spy(Mockito.java:2224)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException: Java 23 (67) is not supported
> by the current version of Byte Buddy which officially supports Java 22 (66) -
> update Byte Buddy or set net.bytebuddy.experimental as a VM property
> at
> net.bytebuddy.utility.OpenedClassReader.of(OpenedClassReader.java:100)
> at
> net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ForInlining.create(TypeWriter.java:4011)
> at
> net.bytebuddy.dynamic.scaffold.TypeWriter$Default.make(TypeWriter.java:2224)
> at
> net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase$UsingTypeWriter.make(DynamicType.java:4055)
> at
> net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase.make(DynamicType.java:3739)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.transform(InlineBytecodeGenerator.java:402)
> at
> java.instrument/java.lang.instrument.ClassFileTransformer.transform(ClassFileTransformer.java:242)
> at
> java.instrument/sun.instrument.TransformerManager.transform(TransformerManager.java:188)
> at
> java.instrument/sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:610)
> at
> java.instrument/sun.instrument.InstrumentationImpl.retransformClasses0(Native
> Method)
> at
> java.instrument/sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:225)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:281)
> ... 34 more
> {noformat}
> Probably requires mockito/bytebuddy updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCR-5048) Jackrabbit should build and test with Java 23
[
https://issues.apache.org/jira/browse/JCR-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-5048:
Issue Type: Task (was: Bug)
> Jackrabbit should build and test with Java 23
> -
>
> Key: JCR-5048
> URL: https://issues.apache.org/jira/browse/JCR-5048
> Project: Jackrabbit Content Repository
> Issue Type: Task
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 2.21.28
>
>
> Right now:
> {noformat}
> Caused by: java.lang.IllegalStateException:
> Byte Buddy could not instrument all classes within the mock's type hierarchy
> This problem should never occur for javac-compiled classes. This problem has
> been observed for classes that are:
> - Compiled by older versions of scalac
> - Classes that are part of the Android distribution
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:75)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:414)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:373)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:352)
> at
> org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
> at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:99)
> at org.mockito.internal.MockitoCore.mock(MockitoCore.java:84)
> at org.mockito.Mockito.spy(Mockito.java:2224)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException: Java 23 (67) is not supported
> by the current version of Byte Buddy which officially supports Java 22 (66) -
> update Byte Buddy or set net.bytebuddy.experimental as a VM property
> at
> net.bytebuddy.utility.OpenedClassReader.of(OpenedClassReader.java:100)
> at
> net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ForInlining.create(TypeWriter.java:4011)
> at
> net.bytebuddy.dynamic.scaffold.TypeWriter$Default.make(TypeWriter.java:2224)
> at
> net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase$UsingTypeWriter.make(DynamicType.java:4055)
> at
> net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase.make(DynamicType.java:3739)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.transform(InlineBytecodeGenerator.java:402)
> at
> java.instrument/java.lang.instrument.ClassFileTransformer.transform(ClassFileTransformer.java:242)
> at
> java.instrument/sun.instrument.TransformerManager.transform(TransformerManager.java:188)
> at
> java.instrument/sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:610)
> at
> java.instrument/sun.instrument.InstrumentationImpl.retransformClasses0(Native
> Method)
> at
> java.instrument/sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:225)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:281)
> ... 34 more
> {noformat}
> Probably requires mockito/bytebuddy updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCR-5048) Jackrabbit should build and test with Java 23
[
https://issues.apache.org/jira/browse/JCR-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-5048:
Description:
Right now:
{noformat}
Caused by: java.lang.IllegalStateException:
Byte Buddy could not instrument all classes within the mock's type hierarchy
This problem should never occur for javac-compiled classes. This problem has
been observed for classes that are:
- Compiled by older versions of scalac
- Classes that are part of the Android distribution
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:75)
at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:414)
at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:373)
at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:352)
at
org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:99)
at org.mockito.internal.MockitoCore.mock(MockitoCore.java:84)
at org.mockito.Mockito.spy(Mockito.java:2224)
... 20 more
Caused by: java.lang.IllegalArgumentException: Java 23 (67) is not supported by
the current version of Byte Buddy which officially supports Java 22 (66) -
update Byte Buddy or set net.bytebuddy.experimental as a VM property
at
net.bytebuddy.utility.OpenedClassReader.of(OpenedClassReader.java:100)
at
net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ForInlining.create(TypeWriter.java:4011)
at
net.bytebuddy.dynamic.scaffold.TypeWriter$Default.make(TypeWriter.java:2224)
at
net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase$UsingTypeWriter.make(DynamicType.java:4055)
at
net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase.make(DynamicType.java:3739)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.transform(InlineBytecodeGenerator.java:402)
at
java.instrument/java.lang.instrument.ClassFileTransformer.transform(ClassFileTransformer.java:242)
at
java.instrument/sun.instrument.TransformerManager.transform(TransformerManager.java:188)
at
java.instrument/sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:610)
at
java.instrument/sun.instrument.InstrumentationImpl.retransformClasses0(Native
Method)
at
java.instrument/sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:225)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:281)
... 34 more
{noformat}
Probably requires mockito/bytebuddy updates.
was:
Right now:
{noformat}
Caused by: java.lang.IllegalStateException:
Byte Buddy could not instrument all classes within the mock's type hierarchy
This problem should never occur for javac-compiled classes. This problem has
been observed for classes that are:
- Compiled by older versions of scalac
- Classes that are part of the Android distribution
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:75)
at
[jira] [Assigned] (JCR-5048) Jackrabbit should build and test with Java 23
[
https://issues.apache.org/jira/browse/JCR-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned JCR-5048:
---
Assignee: Julian Reschke
> Jackrabbit should build and test with Java 23
> -
>
> Key: JCR-5048
> URL: https://issues.apache.org/jira/browse/JCR-5048
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> Right now:
> {noformat}
> Caused by: java.lang.IllegalStateException:
> Byte Buddy could not instrument all classes within the mock's type hierarchy
> This problem should never occur for javac-compiled classes. This problem has
> been observed for classes that are:
> - Compiled by older versions of scalac
> - Classes that are part of the Android distribution
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:75)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:414)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:373)
> at
> org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:352)
> at
> org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
> at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:99)
> at org.mockito.internal.MockitoCore.mock(MockitoCore.java:84)
> at org.mockito.Mockito.spy(Mockito.java:2224)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException: Java 23 (67) is not supported
> by the current version of Byte Buddy which officially supports Java 22 (66) -
> update Byte Buddy or set net.bytebuddy.experimental as a VM property
> at
> net.bytebuddy.utility.OpenedClassReader.of(OpenedClassReader.java:100)
> at
> net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ForInlining.create(TypeWriter.java:4011)
> at
> net.bytebuddy.dynamic.scaffold.TypeWriter$Default.make(TypeWriter.java:2224)
> at
> net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase$UsingTypeWriter.make(DynamicType.java:4055)
> at
> net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase.make(DynamicType.java:3739)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.transform(InlineBytecodeGenerator.java:402)
> at
> java.instrument/java.lang.instrument.ClassFileTransformer.transform(ClassFileTransformer.java:242)
> at
> java.instrument/sun.instrument.TransformerManager.transform(TransformerManager.java:188)
> at
> java.instrument/sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:610)
> at
> java.instrument/sun.instrument.InstrumentationImpl.retransformClasses0(Native
> Method)
> at
> java.instrument/sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:225)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:281)
> ... 34 more
> {noformat}
> Probably requires mockito/bytebuddy updates.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCR-5048) Jackrabbit should build and test with Java 23
[
https://issues.apache.org/jira/browse/JCR-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-5048:
Description:
Right now:
{noformat}
Caused by: java.lang.IllegalStateException:
Byte Buddy could not instrument all classes within the mock's type hierarchy
This problem should never occur for javac-compiled classes. This problem has
been observed for classes that are:
- Compiled by older versions of scalac
- Classes that are part of the Android distribution
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
at
net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
at
org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:75)
at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:414)
at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:373)
at
org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:352)
at
org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:99)
at org.mockito.internal.MockitoCore.mock(MockitoCore.java:84)
at org.mockito.Mockito.spy(Mockito.java:2224)
... 20 more
Caused by: java.lang.IllegalArgumentException: Java 23 (67) is not supported by
the current version of Byte Buddy which officially supports Java 22 (66) -
update Byte Buddy or set net.bytebuddy.experimental as a VM property
at
net.bytebuddy.utility.OpenedClassReader.of(OpenedClassReader.java:100)
at
net.bytebuddy.dynamic.scaffold.TypeWriter$Default$ForInlining.create(TypeWriter.java:4011)
at
net.bytebuddy.dynamic.scaffold.TypeWriter$Default.make(TypeWriter.java:2224)
at
net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase$UsingTypeWriter.make(DynamicType.java:4055)
at
net.bytebuddy.dynamic.DynamicType$Builder$AbstractBase.make(DynamicType.java:3739)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.transform(InlineBytecodeGenerator.java:402)
at
java.instrument/java.lang.instrument.ClassFileTransformer.transform(ClassFileTransformer.java:242)
at
java.instrument/sun.instrument.TransformerManager.transform(TransformerManager.java:188)
at
java.instrument/sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:610)
at
java.instrument/sun.instrument.InstrumentationImpl.retransformClasses0(Native
Method)
at
java.instrument/sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:225)
at
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:281)
... 34 more
{noformat}
> Jackrabbit should build and test with Java 23
> -
>
> Key: JCR-5048
> URL: https://issues.apache.org/jira/browse/JCR-5048
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>Reporter: Julian Reschke
>Priority: Major
>
> Right now:
> {noformat}
> Caused by: java.lang.IllegalStateException:
> Byte Buddy could not instrument all classes within the mock's type hierarchy
> This problem should never occur for javac-compiled classes. This problem has
> been observed for classes that are:
> - Compiled by older versions of scalac
> - Classes that are part of the Android distribution
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:285)
> at
> org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:218)
> at
> org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:78)
> at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
> at
> net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
> at
[jira] [Created] (JCR-5048) Jackrabbit should build and test with Java 23
Julian Reschke created JCR-5048: --- Summary: Jackrabbit should build and test with Java 23 Key: JCR-5048 URL: https://issues.apache.org/jira/browse/JCR-5048 Project: Jackrabbit Content Repository Issue Type: Bug Reporter: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5047) Update to jacoco version 0.8.12
[ https://issues.apache.org/jira/browse/JCR-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838973#comment-17838973 ] Julian Reschke commented on JCR-5047: - trunk: [fd93acf7f|https://github.com/apache/jackrabbit-oak/commit/fd93acf7fe0e9727c8eaf5f0e7df358452fd480d] > Update to jacoco version 0.8.12 > --- > > Key: JCR-5047 > URL: https://issues.apache.org/jira/browse/JCR-5047 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5047) Update to jacoco version 0.8.12
[ https://issues.apache.org/jira/browse/JCR-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5047. - Fix Version/s: 2.21.27 Resolution: Fixed > Update to jacoco version 0.8.12 > --- > > Key: JCR-5047 > URL: https://issues.apache.org/jira/browse/JCR-5047 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5047) Update to jacoco version 0.8.12
[ https://issues.apache.org/jira/browse/JCR-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5047: Labels: candidate_jackrabbit_2.20 (was: ) > Update to jacoco version 0.8.12 > --- > > Key: JCR-5047 > URL: https://issues.apache.org/jira/browse/JCR-5047 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JCR-5047) Update to jacoco version 0.8.12
[ https://issues.apache.org/jira/browse/JCR-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCR-5047: --- Assignee: Julian Reschke (was: Manfred Baedke) > Update to jacoco version 0.8.12 > --- > > Key: JCR-5047 > URL: https://issues.apache.org/jira/browse/JCR-5047 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.20.14, 2.21.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5047) Update to jacoco version 0.8.12
[ https://issues.apache.org/jira/browse/JCR-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5047: Fix Version/s: (was: 2.20.14) (was: 2.21.22) > Update to jacoco version 0.8.12 > --- > > Key: JCR-5047 > URL: https://issues.apache.org/jira/browse/JCR-5047 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5047) Update to jacoco version 0.8.12
Julian Reschke created JCR-5047: --- Summary: Update to jacoco version 0.8.12 Key: JCR-5047 URL: https://issues.apache.org/jira/browse/JCR-5047 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Manfred Baedke Fix For: 2.22, 2.20.14, 2.21.22 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5046) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0
[ https://issues.apache.org/jira/browse/JCR-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17835288#comment-17835288 ] Julian Reschke commented on JCR-5046: - trunk: [3cfbb898c|https://github.com/apache/jackrabbit-oak/commit/3cfbb898cc8024b10746cfbe8de16da1a00baeef] > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0 > > > Key: JCR-5046 > URL: https://issues.apache.org/jira/browse/JCR-5046 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5046) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0
[ https://issues.apache.org/jira/browse/JCR-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5046. - Fix Version/s: 2.21.27 Resolution: Fixed > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0 > > > Key: JCR-5046 > URL: https://issues.apache.org/jira/browse/JCR-5046 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5046) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0
Julian Reschke created JCR-5046: --- Summary: Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0 Key: JCR-5046 URL: https://issues.apache.org/jira/browse/JCR-5046 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.23 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5046) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0
[ https://issues.apache.org/jira/browse/JCR-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5046: Fix Version/s: (was: 2.21.23) > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.62.0 > > > Key: JCR-5046 > URL: https://issues.apache.org/jira/browse/JCR-5046 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-750) startup error around unclosed archives
[
https://issues.apache.org/jira/browse/JCRVLT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834342#comment-17834342
]
Julian Reschke commented on JCRVLT-750:
---
{noformat}
diff --git
a/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/JcrPackageImpl.java
b/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/JcrPackageImpl.java
index b41f0ca9..d9198385 100644
---
a/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/JcrPackageImpl.java
+++
b/vault-core/src/main/java/org/apache/jackrabbit/vault/packaging/impl/JcrPackageImpl.java
@@ -541,6 +541,10 @@ public class JcrPackageImpl implements JcrPackage {
def.setSubPackages(subIds);
}
s.save();
+} else if (!subPacks.isEmpty()) {
+for(JcrPackageImpl p: subPacks) {
+p.close();
+}
}
if (createSnapshot) {
{noformat}
> startup error around unclosed archives
> --
>
> Key: JCRVLT-750
> URL: https://issues.apache.org/jira/browse/JCRVLT-750
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Affects Versions: 3.7.2
>Reporter: Ankita Agarwal
>Priority: Major
>
> {code:java}
> 11.03.2024 13:33:10.690 *ERROR* [OsgiInstallerImpl]
> org.apache.jackrabbit.vault.fs.io.AbstractArchive Detected unclosed archive.
> To figure out where it has been opened set the Java System property
> 'vault.enableStackTraces' to 'true'11.03.2024 13:33:10.690 *ERROR*
> [OsgiInstallerImpl] org.apache.jackrabbit.vault.fs.io.AbstractArchive
> Detected unclosed archive. To figure out where it has been opened set the
> Java System property 'vault.enableStackTraces' to 'true'11.03.2024
> 13:33:10.690 *ERROR* [OsgiInstallerImpl]
> org.apache.jackrabbit.vault.fs.io.AbstractArchive Detected unclosed archive.
> To figure out where it has been opened set the Java System property
> 'vault.enableStackTraces' to 'true'
> Full stacktrace of above unclosed archive is (it can be seen in logs using
> the switch {{{}-Dvault.enableStackTraces=true{}}}):
> {code}
> {code:xml}
> java.lang.Exception: Open Stack Trace
> at org.h2.util.CloseWatcher.register(CloseWatcher.java:85)
> at
> org.apache.jackrabbit.vault.fs.io.ZipArchive.open(ZipArchive.java:156)
> at
> org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.getArchive(ZipVaultPackage.java:107)
> at
> org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.getMetaInf(ZipVaultPackage.java:145)
> at
> org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.getPropertiesMap(ZipVaultPackage.java:323)
> at
> org.apache.jackrabbit.vault.packaging.impl.PackagePropertiesImpl.getProperty(PackagePropertiesImpl.java:265)
> at
> org.apache.jackrabbit.vault.packaging.impl.PackagePropertiesImpl.getId(PackagePropertiesImpl.java:62)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageDefinitionImpl.unwrap(JcrPackageDefinitionImpl.java:219)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.tryUnwrap(JcrPackageImpl.java:258)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:414)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:356)
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.install(JcrPackageImpl.java:350)
> at
> com.adobe.granite.installer.factory.packages.impl.PackageTransformer$InstallPackageTask.execute(PackageTransformer.java:348)
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:918)
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(OsgiInstallerImpl.java:755)
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstallerImpl.java:304)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
> It seems that, in case of sub packages, filevault opens the archive but only
> processes (and close) them in case of non-recursive import option is set to
> false [0]. Packages are deployed non-recursively in this case and filevault
> is not closing the archives when subpacks are not empty.
> This seems to be happening for the we-retail packages, as in case of
> we-retail the created archive is of type ZipArchive [1] (and we are adding a
> close watcher for it [3]), for other cases in which subpacks are there,
> archive is of type MemoryArchive [2]
> I believe this
> [filevault.patch{^}!https://jira.corp.adobe.com/images/icons/link_attachment_7.gif|width=7,height=7!{^}|https://jira.corp.adobe.com/secure/attachment/11792561/11792561_filevault.patch]
> should fix the problem,
> [0]:
>
