[jira] [Commented] (JCR-5092) jackrabbit-jcr2spi: switch to commons-collections4 4.5.0-M2
[ https://issues.apache.org/jira/browse/JCR-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17869368#comment-17869368 ] Julian Reschke commented on JCR-5092: - trunk: [885a0f930|https://github.com/apache/jackrabbit/commit/885a0f93071cab85839f7e2b571aa35e416faa5d] > jackrabbit-jcr2spi: switch to commons-collections4 4.5.0-M2 > --- > > Key: JCR-5092 > URL: https://issues.apache.org/jira/browse/JCR-5092 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr2spi >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.24 > > > Use new class "AbstractLinkedListForJava21"and remove copied code. > Note: this change can only be backported to a stable branch once version > 4.5.0 is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5092) jackrabbit-jcr2spi: switch to commons-collections4 4.5.0-M2
[ https://issues.apache.org/jira/browse/JCR-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5092: Fix Version/s: 2.24 > jackrabbit-jcr2spi: switch to commons-collections4 4.5.0-M2 > --- > > Key: JCR-5092 > URL: https://issues.apache.org/jira/browse/JCR-5092 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr2spi >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.24 > > > Use new class "AbstractLinkedListForJava21"and remove copied code. > Note: this change can only be backported to a stable branch once version > 4.5.0 is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5092) jackrabbit-jcr2spi: switch to commons-collections4 4.5.0-M2
Julian Reschke created JCR-5092: --- Summary: jackrabbit-jcr2spi: switch to commons-collections4 4.5.0-M2 Key: JCR-5092 URL: https://issues.apache.org/jira/browse/JCR-5092 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-jcr2spi Reporter: Julian Reschke Assignee: Julian Reschke Use new class "AbstractLinkedListForJava21"and remove copied code. Note: this change can only be backported to a stable branch once version 4.5.0 is released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5091) jcr-commons: should support java.util.function.Predicate
Julian Reschke created JCR-5091: --- Summary: jcr-commons: should support java.util.function.Predicate Key: JCR-5091 URL: https://issues.apache.org/jira/browse/JCR-5091 Project: Jackrabbit Content Repository Issue Type: New Feature Components: jackrabbit-jcr-commons Reporter: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCRVLT-763) IdConflictPolicy: improve documentation for CREATE_NEW_ID
[ https://issues.apache.org/jira/browse/JCRVLT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCRVLT-763. --- Fix Version/s: 3.8.0 Resolution: Fixed > IdConflictPolicy: improve documentation for CREATE_NEW_ID > - > > Key: JCRVLT-763 > URL: https://issues.apache.org/jira/browse/JCRVLT-763 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 3.8.0 > > > We recently were confused while looking at > IdConflictPolicy.CREATE_NEW_ID > (https://jackrabbit.apache.org/filevault/referenceablenodes.html#Id_Conflict_Policies > and > https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/api/IdConflictPolicy.html). > Trouble is, this Enum suggests that it's only relevant when there indeed is > an ID conflict. However, it is mapped to > https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html > which also affects nodes where there actually is no ID collision whatsoever. > I believe it would be hard to change the behaviour at this point, so we > should at least improve the documentation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-737) IdConflictPolicy.LEGACY: Parent node not found when installing a package - improve test coverage
[
https://issues.apache.org/jira/browse/JCRVLT-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868930#comment-17868930
]
Julian Reschke commented on JCRVLT-737:
---
tmp file leak in test case fixed:
https://github.com/apache/jackrabbit-filevault/commit/d2a47b7c889f0d1a4894364387de5520dbb392c4
> IdConflictPolicy.LEGACY: Parent node not found when installing a package -
> improve test coverage
>
>
> Key: JCRVLT-737
> URL: https://issues.apache.org/jira/browse/JCRVLT-737
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
>Affects Versions: 3.7.2
>Reporter: Timothee Maret
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 3.8.0
>
> Attachments: ReferenceableIdentifiersImportIT.java
>
>
> When importing a resource that already exists at with the same jcr:uuid but
> at a different path, the importer balks with :
>
> {code:java}
> Caused by: javax.jcr.RepositoryException: Some errors occurred while
> installing packages. Please check the logs for details. First exception is
> logged as cause.
> at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:579)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.sling.distribution.serialization.impl.vlt.FileVaultContentSerializer.importFromStream(FileVaultContentSerializer.java:151)
> [org.apache.sling.distribution.core:0.6.0.T202209271257-98a9dd5]
> ... 11 common frames omitted
> Caused by: org.apache.jackrabbit.vault.packaging.PackageException: Error
> creating/updating node
> /content/dam/cgc/tenants/apac/documents/unitholder-letter/pds-cgnpau-12012023(au).pdf/jcr:content
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1177)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:976)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:531)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> ... 12 common frames omitted
> Caused by: java.lang.IllegalStateException: Parent node not found.
> at
> org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1103)
> [org.apache.jackrabbit.vault:3.7.1.T20231005151103-335689a8]
> ... 23 common frames omitted {code}
> After removing the resource from the target repository, re-applying the
> package will succeed.
>
> Configuration of the importer:
> {code:java}
> aclHandling :"MERGE_PRESERVE"
> cugHandling :"OVERWRITE"
> importMode: "REPLACE"
> autoSaveThreshold: 1000 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (JCRVLT-762) Log/report node identifiers that cause import to switch to stashing and sysview import, also report on slow stashing progress
[ https://issues.apache.org/jira/browse/JCRVLT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCRVLT-762. --- Fix Version/s: 3.8.0 Resolution: Fixed > Log/report node identifiers that cause import to switch to stashing and > sysview import, also report on slow stashing progress > - > > Key: JCRVLT-762 > URL: https://issues.apache.org/jira/browse/JCRVLT-762 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 3.8.0 > > > It would be useful for debugging to find out what UUIDs did not match when FV > decides to use NodeStashing to overwrite a node with a new UUID. > (for instance, it would be interesting to see whether the UUID values just > flip-flop between two alternatives, or whether they are really "new" each > time) > Reporting on progress would be useful because stashing operations on large > collections can be really slow on Oak's MongoDocumentStore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JCRVLT-763) IdConflictPolicy: improve documentation for CREATE_NEW_ID
[ https://issues.apache.org/jira/browse/JCRVLT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCRVLT-763: - Assignee: Julian Reschke > IdConflictPolicy: improve documentation for CREATE_NEW_ID > - > > Key: JCRVLT-763 > URL: https://issues.apache.org/jira/browse/JCRVLT-763 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > > We recently were confused while looking at > IdConflictPolicy.CREATE_NEW_ID > (https://jackrabbit.apache.org/filevault/referenceablenodes.html#Id_Conflict_Policies > and > https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/api/IdConflictPolicy.html). > Trouble is, this Enum suggests that it's only relevant when there indeed is > an ID conflict. However, it is mapped to > https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html > which also affects nodes where there actually is no ID collision whatsoever. > I believe it would be hard to change the behaviour at this point, so we > should at least improve the documentation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-763) IdConflictPolicy: improve documentation for CREATE_NEW_ID
[ https://issues.apache.org/jira/browse/JCRVLT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-763: -- Description: We recently were confused while looking at IdConflictPolicy.CREATE_NEW_ID (https://jackrabbit.apache.org/filevault/referenceablenodes.html#Id_Conflict_Policies and https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/api/IdConflictPolicy.html). Trouble is, this Enum suggests that it's only relevant when there indeed is an ID conflict. However, it is mapped to https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html which also affects nodes where there actually is no ID collision whatsoever. I believe it would be hard to change the behaviour at this point, so we should at least improve the documentation. was: We recently were confused while looking at IdConflictPolicy.CREATE_NEW_ID. Trouble is, this Enum suggests that it's only relevant when there indeed is an ID conflict. However, it is mapped to https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html which also affects nodes where there actually is no ID collision whatsoever. I believe it would be hard to change the behaviour at this point, so we should at least improve the documentation. > IdConflictPolicy: improve documentation for CREATE_NEW_ID > - > > Key: JCRVLT-763 > URL: https://issues.apache.org/jira/browse/JCRVLT-763 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Priority: Minor > > We recently were confused while looking at > IdConflictPolicy.CREATE_NEW_ID > (https://jackrabbit.apache.org/filevault/referenceablenodes.html#Id_Conflict_Policies > and > https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/api/IdConflictPolicy.html). > Trouble is, this Enum suggests that it's only relevant when there indeed is > an ID conflict. However, it is mapped to > https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html > which also affects nodes where there actually is no ID collision whatsoever. > I believe it would be hard to change the behaviour at this point, so we > should at least improve the documentation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-762) Log/report node identifiers that cause import to switch to stashing and sysview import, also report on slow stashing progress
[ https://issues.apache.org/jira/browse/JCRVLT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-762: -- Summary: Log/report node identifiers that cause import to switch to stashing and sysview import, also report on slow stashing progress (was: Log/report UUIDs that cause import to switch to stashing and sysview import, also report on slow stashing progress) > Log/report node identifiers that cause import to switch to stashing and > sysview import, also report on slow stashing progress > - > > Key: JCRVLT-762 > URL: https://issues.apache.org/jira/browse/JCRVLT-762 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > > It would be useful for debugging to find out what UUIDs did not match when FV > decides to use NodeStashing to overwrite a node with a new UUID. > (for instance, it would be interesting to see whether the UUID values just > flip-flop between two alternatives, or whether they are really "new" each > time) > Reporting on progress would be useful because stashing operations on large > collections can be really slow on Oak's MongoDocumentStore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-762) Log/report UUIDs that cause import to switch to stashing and sysview import, also report on slow stashing progress
[ https://issues.apache.org/jira/browse/JCRVLT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-762: -- Description: It would be useful for debugging to find out what UUIDs did not match when FV decides to use NodeStashing to overwrite a node with a new UUID. (for instance, it would be interesting to see whether the UUID values just flip-flop between two alternatives, or whether they are really "new" each time) Reporting on progress would be useful because stashing operations on large collections can be really slow on Oak's MongoDocumentStore. was: If would be useful for debugging to find out what UUIDs did not match when FV decides to use NodeStashing to overwrite a node with a new UUID. (for instance, it would be interesting to see whether the UUID values just flip-flop between two alternatives, or whether they are really "new" each time) Reporting on progress would be useful because stashing operations on large collections can be really slow on Oak's MongoDocumentStore. > Log/report UUIDs that cause import to switch to stashing and sysview import, > also report on slow stashing progress > -- > > Key: JCRVLT-762 > URL: https://issues.apache.org/jira/browse/JCRVLT-762 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > > It would be useful for debugging to find out what UUIDs did not match when FV > decides to use NodeStashing to overwrite a node with a new UUID. > (for instance, it would be interesting to see whether the UUID values just > flip-flop between two alternatives, or whether they are really "new" each > time) > Reporting on progress would be useful because stashing operations on large > collections can be really slow on Oak's MongoDocumentStore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-762) Log/report UUIDs that cause import to switch to stashing and sysview import, also report on slow stashing progress
[ https://issues.apache.org/jira/browse/JCRVLT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-762: -- Description: If would be useful for debugging to find out what UUIDs did not match when FV decides to use NodeStashing to overwrite a node with a new UUID. (for instance, it would be interesting to see whether the UUID values just flip-flop between two alternatives, or whether they are really "new" each time) Reporting on progress would be useful because stashing operations on large collections can be really slow on Oak's MongoDocumentStore. was: If would be useful for debugging to find out what UUIDs did not match when FV decides to use NodeStashing to overwrite a node with a new UUID. (for instance, it would be interesting to see whether the UUID values just flip-flop between two alternatives, or whether they are really "new" each time) > Log/report UUIDs that cause import to switch to stashing and sysview import, > also report on slow stashing progress > -- > > Key: JCRVLT-762 > URL: https://issues.apache.org/jira/browse/JCRVLT-762 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > > If would be useful for debugging to find out what UUIDs did not match when FV > decides to use NodeStashing to overwrite a node with a new UUID. > (for instance, it would be interesting to see whether the UUID values just > flip-flop between two alternatives, or whether they are really "new" each > time) > Reporting on progress would be useful because stashing operations on large > collections can be really slow on Oak's MongoDocumentStore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCRVLT-762) Log/report UUIDs that cause import to switch to stashing and sysview import, also report on slow stashing progress
[ https://issues.apache.org/jira/browse/JCRVLT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCRVLT-762: -- Summary: Log/report UUIDs that cause import to switch to stashing and sysview import, also report on slow stashing progress (was: Log/report UUIDs that cause import to switch to stashing and sysview import) > Log/report UUIDs that cause import to switch to stashing and sysview import, > also report on slow stashing progress > -- > > Key: JCRVLT-762 > URL: https://issues.apache.org/jira/browse/JCRVLT-762 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > > If would be useful for debugging to find out what UUIDs did not match when FV > decides to use NodeStashing to overwrite a node with a new UUID. > (for instance, it would be interesting to see whether the UUID values just > flip-flop between two alternatives, or whether they are really "new" each > time) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JCRVLT-762) Log/report UUIDs that cause import to switch to stashing and sysview import
[ https://issues.apache.org/jira/browse/JCRVLT-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCRVLT-762: - Assignee: Julian Reschke > Log/report UUIDs that cause import to switch to stashing and sysview import > --- > > Key: JCRVLT-762 > URL: https://issues.apache.org/jira/browse/JCRVLT-762 > Project: Jackrabbit FileVault > Issue Type: Task > Components: vlt >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > > If would be useful for debugging to find out what UUIDs did not match when FV > decides to use NodeStashing to overwrite a node with a new UUID. > (for instance, it would be interesting to see whether the UUID values just > flip-flop between two alternatives, or whether they are really "new" each > time) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5087) Release Jackrabbit 2.23.0-beta
[ https://issues.apache.org/jira/browse/JCR-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5087. - Resolution: Fixed > Release Jackrabbit 2.23.0-beta > -- > > Key: JCR-5087 > URL: https://issues.apache.org/jira/browse/JCR-5087 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (JCR-5087) Release Jackrabbit 2.23.0-beta
[ https://issues.apache.org/jira/browse/JCR-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-5087. --- > Release Jackrabbit 2.23.0-beta > -- > > Key: JCR-5087 > URL: https://issues.apache.org/jira/browse/JCR-5087 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCRVLT-763) IdConflictPolicy: improve documentation for CREATE_NEW_ID
Julian Reschke created JCRVLT-763: - Summary: IdConflictPolicy: improve documentation for CREATE_NEW_ID Key: JCRVLT-763 URL: https://issues.apache.org/jira/browse/JCRVLT-763 Project: Jackrabbit FileVault Issue Type: Task Components: vlt Reporter: Julian Reschke We recently were confused while looking at IdConflictPolicy.CREATE_NEW_ID. Trouble is, this Enum suggests that it's only relevant when there indeed is an ID conflict. However, it is mapped to https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/ImportUUIDBehavior.html which also affects nodes where there actually is no ID collision whatsoever. I believe it would be hard to change the behaviour at this point, so we should at least improve the documentation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5089) avoid use of deprecated junit.framework.Assert
[ https://issues.apache.org/jira/browse/JCR-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5089. - Fix Version/s: 2.24 2.23.1 Resolution: Fixed trunk: [01cc9acd4|https://github.com/apache/jackrabbit/commit/01cc9acd4999decaa2797abe207359d41b4b0fc9] > avoid use of deprecated junit.framework.Assert > -- > > Key: JCR-5089 > URL: https://issues.apache.org/jira/browse/JCR-5089 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 2.24, 2.23.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (JCR-5089) avoid use of deprecated junit.framework.Assert
[ https://issues.apache.org/jira/browse/JCR-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCR-5089: --- Assignee: Julian Reschke > avoid use of deprecated junit.framework.Assert > -- > > Key: JCR-5089 > URL: https://issues.apache.org/jira/browse/JCR-5089 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5089) avoid use of deprecated junit.framework.Assert
Julian Reschke created JCR-5089: --- Summary: avoid use of deprecated junit.framework.Assert Key: JCR-5089 URL: https://issues.apache.org/jira/browse/JCR-5089 Project: Jackrabbit Content Repository Issue Type: Task Reporter: Julian Reschke -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5088) remove warnings about missing @deprecated annotations
[ https://issues.apache.org/jira/browse/JCR-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5088: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: ) > remove warnings about missing @deprecated annotations > - > > Key: JCR-5088 > URL: https://issues.apache.org/jira/browse/JCR-5088 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5088) remove warnings about missing @deprecated annotations
[ https://issues.apache.org/jira/browse/JCR-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5088. - Fix Version/s: 2.24 2.23.1 Resolution: Fixed trunk: [64278e0d5|https://github.com/apache/jackrabbit/commit/64278e0d593e6ee37e13d99409fab8851c9e0d83] > remove warnings about missing @deprecated annotations > - > > Key: JCR-5088 > URL: https://issues.apache.org/jira/browse/JCR-5088 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.24, 2.23.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5088) remove warnings about missing @deprecated annotations
Julian Reschke created JCR-5088: --- Summary: remove warnings about missing @deprecated annotations Key: JCR-5088 URL: https://issues.apache.org/jira/browse/JCR-5088 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] [Created] (JCR-5087) Release Jackrabbit 2.23.0-beta
Julian Reschke created JCR-5087: --- Summary: Release Jackrabbit 2.23.0-beta Key: JCR-5087 URL: https://issues.apache.org/jira/browse/JCR-5087 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] [Resolved] (JCR-5086) Update spotbugs-maven-plugin to 4.8.6.2
[ https://issues.apache.org/jira/browse/JCR-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5086. - Fix Version/s: 2.23.0 Resolution: Fixed trunk: [2da22f422|https://github.com/apache/jackrabbit/commit/2da22f422a8c1317eb56a3c8317d883c0b22dadd] > Update spotbugs-maven-plugin to 4.8.6.2 > --- > > Key: JCR-5086 > URL: https://issues.apache.org/jira/browse/JCR-5086 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5086) Update spotbugs-maven-plugin to 4.8.6.2
Julian Reschke created JCR-5086: --- Summary: Update spotbugs-maven-plugin to 4.8.6.2 Key: JCR-5086 URL: https://issues.apache.org/jira/browse/JCR-5086 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5086) Update spotbugs-maven-plugin to 4.8.6.2
[ https://issues.apache.org/jira/browse/JCR-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5086: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: candidate_jackrabbit_2.20) > Update spotbugs-maven-plugin to 4.8.6.2 > --- > > Key: JCR-5086 > URL: https://issues.apache.org/jira/browse/JCR-5086 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5086) Update spotbugs-maven-plugin to 4.8.6.2
[ https://issues.apache.org/jira/browse/JCR-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5086: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.27) (was: 2.22.0) > Update spotbugs-maven-plugin to 4.8.6.2 > --- > > Key: JCR-5086 > URL: https://issues.apache.org/jira/browse/JCR-5086 > 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.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5085) update checkstyle-plugin dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866373#comment-17866373 ] Julian Reschke commented on JCR-5085: - trunk: [804d70760|https://github.com/apache/jackrabbit/commit/804d7076062f757faf1548c2cc029ba7b9dfaab3] > update checkstyle-plugin dependency to 3.4.0 > > > Key: JCR-5085 > URL: https://issues.apache.org/jira/browse/JCR-5085 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5085) update checkstyle-plugin dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5085: Fix Version/s: (was: 2.22) (was: 2.21.21) (was: 2.20.14) > update checkstyle-plugin dependency to 3.4.0 > > > Key: JCR-5085 > URL: https://issues.apache.org/jira/browse/JCR-5085 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5085) update checkstyle-plugin dependency to 3.4.0
[ https://issues.apache.org/jira/browse/JCR-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5085: Fix Version/s: 2.24 > update checkstyle-plugin dependency to 3.4.0 > > > Key: JCR-5085 > URL: https://issues.apache.org/jira/browse/JCR-5085 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5085) update checkstyle-plugin dependency to 3.4.0
Julian Reschke created JCR-5085: --- Summary: update checkstyle-plugin dependency to 3.4.0 Key: JCR-5085 URL: https://issues.apache.org/jira/browse/JCR-5085 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-5084) Update pmd-plugin dependency to 3.24.0
[ https://issues.apache.org/jira/browse/JCR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866355#comment-17866355 ] Julian Reschke commented on JCR-5084: - trunk: [1c799ec13|https://github.com/apache/jackrabbit/commit/1c799ec13964f519dd8fd325b8bef4171c5fe246] > Update pmd-plugin dependency to 3.24.0 > -- > > Key: JCR-5084 > URL: https://issues.apache.org/jira/browse/JCR-5084 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5084) Update pmd-plugin dependency to 3.24.0
[ https://issues.apache.org/jira/browse/JCR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5084. - Fix Version/s: 2.23.0 Resolution: Fixed > Update pmd-plugin dependency to 3.24.0 > -- > > Key: JCR-5084 > URL: https://issues.apache.org/jira/browse/JCR-5084 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5084) Update pmd-plugin dependency to 3.24.0
[ https://issues.apache.org/jira/browse/JCR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5084: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: candidate_jackrabbit_2.20) > Update pmd-plugin dependency to 3.24.0 > -- > > Key: JCR-5084 > URL: https://issues.apache.org/jira/browse/JCR-5084 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5084) Update pmd-plugin dependency to 3.24.0
Julian Reschke created JCR-5084: --- Summary: Update pmd-plugin dependency to 3.24.0 Key: JCR-5084 URL: https://issues.apache.org/jira/browse/JCR-5084 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5084) Update pmd-plugin dependency to 3.24.0
[ https://issues.apache.org/jira/browse/JCR-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5084: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.27) (was: 2.22.0) > Update pmd-plugin dependency to 3.24.0 > -- > > Key: JCR-5084 > URL: https://issues.apache.org/jira/browse/JCR-5084 > 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.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5083) Update maven-jar-plugin to 3.4.2
[ https://issues.apache.org/jira/browse/JCR-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866342#comment-17866342 ] Julian Reschke commented on JCR-5083: - trunk: [96aa13504|https://github.com/apache/jackrabbit/commit/96aa13504a6cc7d419d1cb234b73800705c5d20e] > Update maven-jar-plugin to 3.4.2 > > > Key: JCR-5083 > URL: https://issues.apache.org/jira/browse/JCR-5083 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5083) Update maven-jar-plugin to 3.4.2
[ https://issues.apache.org/jira/browse/JCR-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5083. - Fix Version/s: 2.23.0 Resolution: Fixed > Update maven-jar-plugin to 3.4.2 > > > Key: JCR-5083 > URL: https://issues.apache.org/jira/browse/JCR-5083 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5083) Update maven-jar-plugin to 3.4.2
[ https://issues.apache.org/jira/browse/JCR-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5083: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: candidate_jackrabbit_2.20) > Update maven-jar-plugin to 3.4.2 > > > Key: JCR-5083 > URL: https://issues.apache.org/jira/browse/JCR-5083 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5083) Update maven-jar-plugin to 3.4.2
Julian Reschke created JCR-5083: --- Summary: Update maven-jar-plugin to 3.4.2 Key: JCR-5083 URL: https://issues.apache.org/jira/browse/JCR-5083 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5083) Update maven-jar-plugin to 3.4.2
[ https://issues.apache.org/jira/browse/JCR-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5083: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.27) (was: 2.22.0) > Update maven-jar-plugin to 3.4.2 > > > Key: JCR-5083 > URL: https://issues.apache.org/jira/browse/JCR-5083 > 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.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5082) update Jetty to 9.4.55.v20240627
[ https://issues.apache.org/jira/browse/JCR-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866339#comment-17866339 ] Julian Reschke commented on JCR-5082: - trunk: [cd862214f|https://github.com/apache/jackrabbit/commit/cd862214fb98783944dd3204a528d083e356d4ce] > update Jetty to 9.4.55.v20240627 > > > Key: JCR-5082 > URL: https://issues.apache.org/jira/browse/JCR-5082 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone, parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5082) update Jetty to 9.4.55.v20240627
[ https://issues.apache.org/jira/browse/JCR-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5082. - Fix Version/s: 2.23.0 Resolution: Fixed > update Jetty to 9.4.55.v20240627 > > > Key: JCR-5082 > URL: https://issues.apache.org/jira/browse/JCR-5082 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone, parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5082) update Jetty to 9.4.55.v20240627
Julian Reschke created JCR-5082: --- Summary: update Jetty to 9.4.55.v20240627 Key: JCR-5082 URL: https://issues.apache.org/jira/browse/JCR-5082 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-standalone, 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] [Updated] (JCR-5082) update Jetty to 9.4.55.v20240627
[ https://issues.apache.org/jira/browse/JCR-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5082: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.21) (was: 2.20.14) > update Jetty to 9.4.55.v20240627 > > > Key: JCR-5082 > URL: https://issues.apache.org/jira/browse/JCR-5082 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone, parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5082) update Jetty to 9.4.55.v20240627
[ https://issues.apache.org/jira/browse/JCR-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5082: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: ) > update Jetty to 9.4.55.v20240627 > > > Key: JCR-5082 > URL: https://issues.apache.org/jira/browse/JCR-5082 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-standalone, parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5081) update aws java sdk version to 1.12.761
[ https://issues.apache.org/jira/browse/JCR-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866306#comment-17866306 ] Julian Reschke commented on JCR-5081: - trunk: [dac8dea1e|https://github.com/apache/jackrabbit/commit/dac8dea1eec9f735a4fa472865a85914f62f889c] > update aws java sdk version to 1.12.761 > --- > > Key: JCR-5081 > URL: https://issues.apache.org/jira/browse/JCR-5081 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-aws-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5081) update aws java sdk version to 1.12.761
[ https://issues.apache.org/jira/browse/JCR-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5081. - Fix Version/s: 2.23.0 Resolution: Fixed > update aws java sdk version to 1.12.761 > --- > > Key: JCR-5081 > URL: https://issues.apache.org/jira/browse/JCR-5081 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-aws-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5081) update aws java sdk version to 1.12.761
[ https://issues.apache.org/jira/browse/JCR-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5081: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.27) (was: 2.22.0) > update aws java sdk version to 1.12.761 > --- > > Key: JCR-5081 > URL: https://issues.apache.org/jira/browse/JCR-5081 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-aws-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5081) update aws java sdk version to 1.12.761
[ https://issues.apache.org/jira/browse/JCR-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5081: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: candidate_jackrabbit_2.20) > update aws java sdk version to 1.12.761 > --- > > Key: JCR-5081 > URL: https://issues.apache.org/jira/browse/JCR-5081 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-aws-ext >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.22, 2.21.27, 2.22.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5081) update aws java sdk version to 1.12.761
Julian Reschke created JCR-5081: --- Summary: update aws java sdk version to 1.12.761 Key: JCR-5081 URL: https://issues.apache.org/jira/browse/JCR-5081 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-aws-ext Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5080) Update easymock dependency to 5.3.0
[ https://issues.apache.org/jira/browse/JCR-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866034#comment-17866034 ] Julian Reschke commented on JCR-5080: - trunk: [1305cf978|https://github.com/apache/jackrabbit/commit/1305cf9785dc922fb6b7d44a69417c79041f5bd2] > Update easymock dependency to 5.3.0 > --- > > Key: JCR-5080 > URL: https://issues.apache.org/jira/browse/JCR-5080 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5080) Update easymock dependency to 5.3.0
[ https://issues.apache.org/jira/browse/JCR-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5080. - Fix Version/s: 2.23.0 Resolution: Fixed > Update easymock dependency to 5.3.0 > --- > > Key: JCR-5080 > URL: https://issues.apache.org/jira/browse/JCR-5080 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5080) Update easymock dependency to 5.3.0
[ https://issues.apache.org/jira/browse/JCR-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5080: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: ) > Update easymock dependency to 5.3.0 > --- > > Key: JCR-5080 > URL: https://issues.apache.org/jira/browse/JCR-5080 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5080) Update easymock dependency to 5.3.0
[ https://issues.apache.org/jira/browse/JCR-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5080: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.20) (was: 2.20.13) > Update easymock dependency to 5.3.0 > --- > > Key: JCR-5080 > URL: https://issues.apache.org/jira/browse/JCR-5080 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5080) Update easymock dependency to 5.3.0
Julian Reschke created JCR-5080: --- Summary: Update easymock dependency to 5.3.0 Key: JCR-5080 URL: https://issues.apache.org/jira/browse/JCR-5080 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.20, 2.20.13 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (JCR-5079) Update tomcat dependency to 9.0.91
[ https://issues.apache.org/jira/browse/JCR-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866024#comment-17866024 ] Julian Reschke edited comment on JCR-5079 at 7/15/24 11:14 AM: --- trunk: [629446827|https://github.com/apache/jackrabbit/commit/62944682709a40e0c97b6b1be6169b9b1d3ae6ed] [df83cbab2|https://github.com/apache/jackrabbit/commit/df83cbab2f3da9b0fe76caf3c241a24eb5724ef5] was (Author: reschke): trunk: [df83cbab2|https://github.com/apache/jackrabbit/commit/df83cbab2f3da9b0fe76caf3c241a24eb5724ef5] > Update tomcat dependency to 9.0.91 > -- > > Key: JCR-5079 > URL: https://issues.apache.org/jira/browse/JCR-5079 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5079) Update tomcat dependency to 9.0.91
[ https://issues.apache.org/jira/browse/JCR-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866024#comment-17866024 ] Julian Reschke commented on JCR-5079: - trunk: [df83cbab2|https://github.com/apache/jackrabbit/commit/df83cbab2f3da9b0fe76caf3c241a24eb5724ef5] > Update tomcat dependency to 9.0.91 > -- > > Key: JCR-5079 > URL: https://issues.apache.org/jira/browse/JCR-5079 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5079) Update tomcat dependency to 9.0.91
[ https://issues.apache.org/jira/browse/JCR-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5079. - Fix Version/s: 2.24 2.23.0 Resolution: Fixed > Update tomcat dependency to 9.0.91 > -- > > Key: JCR-5079 > URL: https://issues.apache.org/jira/browse/JCR-5079 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5079) Update tomcat dependency to 9.0.91
[ https://issues.apache.org/jira/browse/JCR-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5079: Fix Version/s: (was: 2.22) (was: 2.21.27) (was: 2.22.0) > Update tomcat dependency to 9.0.91 > -- > > Key: JCR-5079 > URL: https://issues.apache.org/jira/browse/JCR-5079 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5079) Update tomcat dependency to 9.0.91
[ https://issues.apache.org/jira/browse/JCR-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5079: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: candidate_jackrabbit_2.20) > Update tomcat dependency to 9.0.91 > -- > > Key: JCR-5079 > URL: https://issues.apache.org/jira/browse/JCR-5079 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5079) Update tomcat dependency to 9.0.91
Julian Reschke created JCR-5079: --- Summary: Update tomcat dependency to 9.0.91 Key: JCR-5079 URL: https://issues.apache.org/jira/browse/JCR-5079 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-webapp Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5078) update Apache parent pom to version 33
[ https://issues.apache.org/jira/browse/JCR-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866011#comment-17866011 ] Julian Reschke commented on JCR-5078: - trunk: [e9e0ae250|https://github.com/apache/jackrabbit/commit/e9e0ae2500b3af2d7b6dc3cf6a121706839738c2] > update Apache parent pom to version 33 > -- > > Key: JCR-5078 > URL: https://issues.apache.org/jira/browse/JCR-5078 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5078) update Apache parent pom to version 33
[ https://issues.apache.org/jira/browse/JCR-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5078. - Fix Version/s: 2.24 2.23.0 Resolution: Fixed > update Apache parent pom to version 33 > -- > > Key: JCR-5078 > URL: https://issues.apache.org/jira/browse/JCR-5078 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5078) update Apache parent pom to version 33
[ https://issues.apache.org/jira/browse/JCR-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5078: Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: candidate_jackrabbit_2.20) > update Apache parent pom to version 33 > -- > > Key: JCR-5078 > URL: https://issues.apache.org/jira/browse/JCR-5078 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22 > -- 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 2.22 > 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] [Comment Edited] (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 edited comment on JCR-5055 at 7/15/24 10:08 AM: --- trunk: (2.21.27-beta) [e9f0eaf82|https://github.com/apache/jackrabbit/commit/e9f0eaf827c9a9044d283be45ecb3014d9117a2b] 2.22: (2.21.27-beta) [e9f0eaf82|https://github.com/apache/jackrabbit/commit/e9f0eaf827c9a9044d283be45ecb3014d9117a2b] was (Author: reschke): 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-5078) update Apache parent pom to version 33
[ https://issues.apache.org/jira/browse/JCR-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5078: Fix Version/s: (was: 2.22) (was: 2.21.27) (was: 2.22.0) > update Apache parent pom to version 33 > -- > > Key: JCR-5078 > URL: https://issues.apache.org/jira/browse/JCR-5078 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.20 > -- 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.22) (was: 2.21.27) (was: 2.22.0) > 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 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5078) update Apache parent pom to version 33
Julian Reschke created JCR-5078: --- Summary: update Apache parent pom to version 33 Key: JCR-5078 URL: https://issues.apache.org/jira/browse/JCR-5078 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCRVLT-762) Log/report UUIDs that cause import to switch to stashing and sysview import
Julian Reschke created JCRVLT-762: - Summary: Log/report UUIDs that cause import to switch to stashing and sysview import Key: JCRVLT-762 URL: https://issues.apache.org/jira/browse/JCRVLT-762 Project: Jackrabbit FileVault Issue Type: Task Components: vlt Reporter: Julian Reschke If would be useful for debugging to find out what UUIDs did not match when FV decides to use NodeStashing to overwrite a node with a new UUID. (for instance, it would be interesting to see whether the UUID values just flip-flop between two alternatives, or whether they are really "new" each time) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5077) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0
[ https://issues.apache.org/jira/browse/JCR-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864891#comment-17864891 ] Julian Reschke commented on JCR-5077: - trunk: [c5447c23c|https://github.com/apache/jackrabbit/commit/c5447c23c4b5dbec28b6b9edae2069610257826d] > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0 > > > Key: JCR-5077 > URL: https://issues.apache.org/jira/browse/JCR-5077 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5077) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0
[ https://issues.apache.org/jira/browse/JCR-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5077. - Fix Version/s: 2.23.0 Resolution: Fixed > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0 > > > Key: JCR-5077 > URL: https://issues.apache.org/jira/browse/JCR-5077 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.22 > Fix For: 2.24, 2.23.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5077) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0
[ https://issues.apache.org/jira/browse/JCR-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5077: Labels: candidate_jackrabbit_2.22 (was: ) > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0 > > > Key: JCR-5077 > URL: https://issues.apache.org/jira/browse/JCR-5077 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jackrabbit_2.22 > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (JCR-5071) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.64.0
[ https://issues.apache.org/jira/browse/JCR-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849822#comment-17849822 ] Julian Reschke edited comment on JCR-5071 at 7/11/24 3:58 AM: -- trunk: (2.21.27-beta) [e557bd7d0|https://github.com/apache/jackrabbit/commit/e557bd7d0fa0bb1350b3b384dac85f938040f0c5] 2.22: (2.21.27-beta) [e557bd7d0|https://github.com/apache/jackrabbit/commit/e557bd7d0fa0bb1350b3b384dac85f938040f0c5] was (Author: reschke): trunk: [e557bd7d0|https://github.com/apache/jackrabbit/commit/e557bd7d0fa0bb1350b3b384dac85f938040f0c5] > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.64.0 > > > Key: JCR-5071 > URL: https://issues.apache.org/jira/browse/JCR-5071 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.22, 2.21.27, 2.22.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5077) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0
[ https://issues.apache.org/jira/browse/JCR-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5077: Fix Version/s: 2.24 (was: 2.22) (was: 2.21.27) (was: 2.22.0) > Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0 > > > Key: JCR-5077 > URL: https://issues.apache.org/jira/browse/JCR-5077 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.24 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5077) Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0
Julian Reschke created JCR-5077: --- Summary: Update oak-jackrabbit-api.version.implemented in trunk to Oak 1.66.0 Key: JCR-5077 URL: https://issues.apache.org/jira/browse/JCR-5077 Project: Jackrabbit Content Repository Issue Type: Task Components: parent Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.22, 2.21.27, 2.22.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-755) All contents are deleted when a content package created from a folder is applied
[ https://issues.apache.org/jira/browse/JCRVLT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864136#comment-17864136 ] Julian Reschke commented on JCRVLT-755: --- I really don't know. Any chance that we can get a test case? > All contents are deleted when a content package created from a folder is > applied > > > Key: JCRVLT-755 > URL: https://issues.apache.org/jira/browse/JCRVLT-755 > Project: Jackrabbit FileVault > Issue Type: Bug > Components: vlt >Reporter: Christian Schneider >Priority: Critical > Attachments: deleted.zip, working.zip > > > We have a strange issue where replication of a folder deletes all contents of > the folder on destination system. > We create a filevault package from the folder and apply the package using > filevault on the destination system. > It seems the behaviour is different depending if the folder or parent folder > has a jcr:content sub node. > I attached two content packages: > * working.zip : Export of /content/experience-fragements/test2 when > experience-fragements has jcr:content subnode. In this case an existing > experience fragement at /content/experience-fragements/test2/test4 is not > deleted > * deleted.zip : Export of /content/experience-fragements/test2 when > experience-fragements does not have jcr:content subnode. In this case prior > existing test4 content fragment was deleted on apply > The content packages look different. In the case with jcr:content > experience-fragments and test2 are folders in the zip. > In case without jcr:content inside experience-fragments there are no folders > like above. Instead the sub nodes are inside a single content.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCRVLT-760) release check fails
[
https://issues.apache.org/jira/browse/JCRVLT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17863815#comment-17863815
]
Julian Reschke commented on JCRVLT-760:
---
So we have:
- three files only in the source ZIP: DEPENDENCIES, LICENSE, NOTICE
- more files only in Git: *.bndrun, .asf.yaml
Probably multiple reasons.
> release check fails
> ---
>
> Key: JCRVLT-760
> URL: https://issues.apache.org/jira/browse/JCRVLT-760
> Project: Jackrabbit FileVault
> Issue Type: Bug
>Reporter: Julian Reschke
>Priority: Minor
>
> As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
> {noformat}
> sh check-release.sh filevault 3.7.4
> {noformat}
> but that fails with:
> {noformat}
> [INFO]Unzipping jackrabbit-filevault-3.7.4-source-release.zip...
> Cleaning .gitignore from zip
> Cleaning .gitattributes from zip
> Cleaning .flattened-pom.xml from zip
> [INFO]Comparing sources...
> [INFO]
> Only in ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4:
> .asf.yaml
> Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
> DEPENDENCIES
> Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
> LICENSE
> Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
> NOTICE
> Only in ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4:
> target-osgi-environment
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-core:
> max-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-core:
> min-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-rcp:
> max-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-rcp:
> min-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-sync:
> min-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-validation:
> max-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-validation:
> min-target.bndrun
> [ERROR] NOT OK: Tagged sources are different from those in the archive
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCRVLT-760) release check fails
[
https://issues.apache.org/jira/browse/JCRVLT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCRVLT-760:
--
Description:
As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
{noformat}
sh check-release.sh filevault 3.7.4
{noformat}
but that fails with:
{noformat}
[INFO]Unzipping jackrabbit-filevault-3.7.4-source-release.zip...
Cleaning .gitignore from zip
Cleaning .gitattributes from zip
Cleaning .flattened-pom.xml from zip
[INFO]Comparing sources...
[INFO]
Only in ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4:
.asf.yaml
Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
DEPENDENCIES
Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
LICENSE
Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
NOTICE
Only in ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4:
target-osgi-environment
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-core:
max-target.bndrun
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-core:
min-target.bndrun
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-rcp:
max-target.bndrun
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-rcp:
min-target.bndrun
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-sync:
min-target.bndrun
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-validation:
max-target.bndrun
Only in
./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-validation:
min-target.bndrun
[ERROR] NOT OK: Tagged sources are different from those in the archive
{noformat}
was:
As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
{noformat}
mvn clean deploy -Papache-release -Dmaven.deploy.skip=true
{noformat}
but that fails with:
{noformat}
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.370 s
[INFO] Finished at: 2024-07-06T13:24:43+02:00
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:flatten-maven-plugin:1.5.0:flatten (flatten) on project
parent: 1 problem was encountered while building the effective model
[ERROR] [FATAL] Non-readable POM
/home/jre/jackrabbit-filevault/parent/.flattened-pom.xml:
/home/jre/jackrabbit-filevault/parent/.flattened-pom.xml (No such file or
directory)
{noformat}
> release check fails
> ---
>
> Key: JCRVLT-760
> URL: https://issues.apache.org/jira/browse/JCRVLT-760
> Project: Jackrabbit FileVault
> Issue Type: Bug
>Reporter: Julian Reschke
>Priority: Minor
>
> As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
> {noformat}
> sh check-release.sh filevault 3.7.4
> {noformat}
> but that fails with:
> {noformat}
> [INFO]Unzipping jackrabbit-filevault-3.7.4-source-release.zip...
> Cleaning .gitignore from zip
> Cleaning .gitattributes from zip
> Cleaning .flattened-pom.xml from zip
> [INFO]Comparing sources...
> [INFO]
> Only in ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4:
> .asf.yaml
> Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
> DEPENDENCIES
> Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
> LICENSE
> Only in ./target/jackrabbit-filevault-3.7.4/zip/jackrabbit-filevault-3.7.4:
> NOTICE
> Only in ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4:
> target-osgi-environment
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-core:
> max-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-core:
> min-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-rcp:
> max-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-rcp:
> min-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-sync:
> min-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-validation:
> max-target.bndrun
> Only in
> ./target/jackrabbit-filevault-3.7.4/scm/jackrabbit-filevault-3.7.4/vault-validation:
> min-target.bndrun
> [ERROR] NOT OK: Tagged sources are different from those in the archive
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] (JCRVLT-760) release check fails
[ https://issues.apache.org/jira/browse/JCRVLT-760 ]
Julian Reschke deleted comment on JCRVLT-760:
---
was (Author: reschke):
Seems to be broken since:
https://github.com/apache/jackrabbit-filevault/commit/f8f86c7fbd392deddf561f64c2e93126d50aa5dd
which seems weird, so I'll check once again later today.
> release check fails
> ---
>
> Key: JCRVLT-760
> URL: https://issues.apache.org/jira/browse/JCRVLT-760
> Project: Jackrabbit FileVault
> Issue Type: Bug
>Reporter: Julian Reschke
>Priority: Minor
>
> As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
> {noformat}
> mvn clean deploy -Papache-release -Dmaven.deploy.skip=true
> {noformat}
> but that fails with:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.370 s
> [INFO] Finished at: 2024-07-06T13:24:43+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:flatten-maven-plugin:1.5.0:flatten (flatten) on project
> parent: 1 problem was encountered while building the effective model
> [ERROR] [FATAL] Non-readable POM
> /home/jre/jackrabbit-filevault/parent/.flattened-pom.xml:
> /home/jre/jackrabbit-filevault/parent/.flattened-pom.xml (No such file or
> directory)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCRVLT-760) release check fails
[
https://issues.apache.org/jira/browse/JCRVLT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17863692#comment-17863692
]
Julian Reschke commented on JCRVLT-760:
---
Seems to be broken since:
https://github.com/apache/jackrabbit-filevault/commit/f8f86c7fbd392deddf561f64c2e93126d50aa5dd
which seems weird, so I'll check once again later today.
> release check fails
> ---
>
> Key: JCRVLT-760
> URL: https://issues.apache.org/jira/browse/JCRVLT-760
> Project: Jackrabbit FileVault
> Issue Type: Bug
>Reporter: Julian Reschke
>Priority: Minor
>
> As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
> {noformat}
> mvn clean deploy -Papache-release -Dmaven.deploy.skip=true
> {noformat}
> but that fails with:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.370 s
> [INFO] Finished at: 2024-07-06T13:24:43+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:flatten-maven-plugin:1.5.0:flatten (flatten) on project
> parent: 1 problem was encountered while building the effective model
> [ERROR] [FATAL] Non-readable POM
> /home/jre/jackrabbit-filevault/parent/.flattened-pom.xml:
> /home/jre/jackrabbit-filevault/parent/.flattened-pom.xml (No such file or
> directory)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (JCRVLT-760) release check fails
Julian Reschke created JCRVLT-760:
-
Summary: release check fails
Key: JCRVLT-760
URL: https://issues.apache.org/jira/browse/JCRVLT-760
Project: Jackrabbit FileVault
Issue Type: Bug
Reporter: Julian Reschke
As per https://jackrabbit.apache.org/filevault/howto_release.html I tried
{noformat}
mvn clean deploy -Papache-release -Dmaven.deploy.skip=true
{noformat}
but that fails with:
{noformat}
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 4.370 s
[INFO] Finished at: 2024-07-06T13:24:43+02:00
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:flatten-maven-plugin:1.5.0:flatten (flatten) on project
parent: 1 problem was encountered while building the effective model
[ERROR] [FATAL] Non-readable POM
/home/jre/jackrabbit-filevault/parent/.flattened-pom.xml:
/home/jre/jackrabbit-filevault/parent/.flattened-pom.xml (No such file or
directory)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JCR-5076) Use correctly test scope for dependencies of type: test-jar
[
https://issues.apache.org/jira/browse/JCR-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862734#comment-17862734
]
Julian Reschke edited comment on JCR-5076 at 7/3/24 11:18 AM:
--
Thanks, [~jkevan]. Backports will happen eventually as per our usual procedure
(cascading after releasing from the upper branch).
was (Author: reschke):
Thanks, [~jkevan]. Backports will happen eventually.
> Use correctly test scope for dependencies of type: test-jar
> ---
>
> Key: JCR-5076
> URL: https://issues.apache.org/jira/browse/JCR-5076
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-aws-ext
>Affects Versions: 2.20.16, 2.21.27, 2.22.0
>Reporter: Kevan Jahanshahi
>Assignee: Julian Reschke
>Priority: Trivial
> Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22
> Fix For: 2.24, 2.23.0
>
>
> In *jackrabbit-aws-ext* subproject there is a dependency:
> {code:java}
>
> org.apache.jackrabbit
> jackrabbit-data
> ${project.version}
> test-jar
> {code}
> I think it should be:
> {code:java}
> test {code}
> Would be great if it's possible to backport this fix to previous versions
> (2.21.x, 2.20.x) but I let you decided about it, depending on your release
> schedule and maintained versions.
> Here is a pull request with the small fix:
> [https://github.com/apache/jackrabbit/pull/194]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCR-5076) Use correctly test scope for dependencies of type: test-jar
[
https://issues.apache.org/jira/browse/JCR-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862733#comment-17862733
]
Julian Reschke commented on JCR-5076:
-
trunk:
[6313b0502|https://github.com/apache/jackrabbit/commit/6313b0502a13c623410e95dc918ba84558b3531a]
> Use correctly test scope for dependencies of type: test-jar
> ---
>
> Key: JCR-5076
> URL: https://issues.apache.org/jira/browse/JCR-5076
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-aws-ext
>Affects Versions: 2.20.16, 2.21.27, 2.22.0
>Reporter: Kevan Jahanshahi
>Assignee: Julian Reschke
>Priority: Trivial
> Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22
> Fix For: 2.24, 2.23.0
>
>
> In *jackrabbit-aws-ext* subproject there is a dependency:
> {code:java}
>
> org.apache.jackrabbit
> jackrabbit-data
> ${project.version}
> test-jar
> {code}
> I think it should be:
> {code:java}
> test {code}
> Would be great if it's possible to backport this fix to previous versions
> (2.21.x, 2.20.x) but I let you decided about it, depending on your release
> schedule and maintained versions.
> Here is a pull request with the small fix:
> [https://github.com/apache/jackrabbit/pull/194]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCR-5076) Use correctly test scope for dependencies of type: test-jar
[
https://issues.apache.org/jira/browse/JCR-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862734#comment-17862734
]
Julian Reschke commented on JCR-5076:
-
Thanks, [~jkevan]. Backports will happen eventually.
> Use correctly test scope for dependencies of type: test-jar
> ---
>
> Key: JCR-5076
> URL: https://issues.apache.org/jira/browse/JCR-5076
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-aws-ext
>Affects Versions: 2.20.16, 2.21.27, 2.22.0
>Reporter: Kevan Jahanshahi
>Assignee: Julian Reschke
>Priority: Trivial
> Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22
> Fix For: 2.24, 2.23.0
>
>
> In *jackrabbit-aws-ext* subproject there is a dependency:
> {code:java}
>
> org.apache.jackrabbit
> jackrabbit-data
> ${project.version}
> test-jar
> {code}
> I think it should be:
> {code:java}
> test {code}
> Would be great if it's possible to backport this fix to previous versions
> (2.21.x, 2.20.x) but I let you decided about it, depending on your release
> schedule and maintained versions.
> Here is a pull request with the small fix:
> [https://github.com/apache/jackrabbit/pull/194]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (JCR-5076) Use correctly test scope for dependencies of type: test-jar
[
https://issues.apache.org/jira/browse/JCR-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-5076.
-
Fix Version/s: 2.24
2.23.0
Resolution: Fixed
> Use correctly test scope for dependencies of type: test-jar
> ---
>
> Key: JCR-5076
> URL: https://issues.apache.org/jira/browse/JCR-5076
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-aws-ext
>Affects Versions: 2.20.16, 2.21.27, 2.22.0
>Reporter: Kevan Jahanshahi
>Assignee: Julian Reschke
>Priority: Trivial
> Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22
> Fix For: 2.24, 2.23.0
>
>
> In *jackrabbit-aws-ext* subproject there is a dependency:
> {code:java}
>
> org.apache.jackrabbit
> jackrabbit-data
> ${project.version}
> test-jar
> {code}
> I think it should be:
> {code:java}
> test {code}
> Would be great if it's possible to backport this fix to previous versions
> (2.21.x, 2.20.x) but I let you decided about it, depending on your release
> schedule and maintained versions.
> Here is a pull request with the small fix:
> [https://github.com/apache/jackrabbit/pull/194]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JCR-5076) Use correctly test scope for dependencies of type: test-jar
[
https://issues.apache.org/jira/browse/JCR-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-5076:
Labels: candidate_jackrabbit_2.20 candidate_jackrabbit_2.22 (was: )
> Use correctly test scope for dependencies of type: test-jar
> ---
>
> Key: JCR-5076
> URL: https://issues.apache.org/jira/browse/JCR-5076
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-aws-ext
>Affects Versions: 2.20.16, 2.21.27, 2.22.0
>Reporter: Kevan Jahanshahi
>Assignee: Julian Reschke
>Priority: Trivial
> Labels: candidate_jackrabbit_2.20, candidate_jackrabbit_2.22
>
> In *jackrabbit-aws-ext* subproject there is a dependency:
> {code:java}
>
> org.apache.jackrabbit
> jackrabbit-data
> ${project.version}
> test-jar
> {code}
> I think it should be:
> {code:java}
> test {code}
> Would be great if it's possible to backport this fix to previous versions
> (2.21.x, 2.20.x) but I let you decided about it, depending on your release
> schedule and maintained versions.
> Here is a pull request with the small fix:
> [https://github.com/apache/jackrabbit/pull/194]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (JCR-5076) Use correctly test scope for dependencies of type: test-jar
[
https://issues.apache.org/jira/browse/JCR-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned JCR-5076:
---
Assignee: Julian Reschke
> Use correctly test scope for dependencies of type: test-jar
> ---
>
> Key: JCR-5076
> URL: https://issues.apache.org/jira/browse/JCR-5076
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-aws-ext
>Affects Versions: 2.20.16, 2.21.27, 2.22.0
>Reporter: Kevan Jahanshahi
>Assignee: Julian Reschke
>Priority: Trivial
>
> In *jackrabbit-aws-ext* subproject there is a dependency:
> {code:java}
>
> org.apache.jackrabbit
> jackrabbit-data
> ${project.version}
> test-jar
> {code}
> I think it should be:
> {code:java}
> test {code}
> Would be great if it's possible to backport this fix to previous versions
> (2.21.x, 2.20.x) but I let you decided about it, depending on your release
> schedule and maintained versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JCR-4892) support the jakarta.servlet package name
[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862441#comment-17862441
]
Julian Reschke edited comment on JCR-4892 at 7/2/24 1:19 PM:
-
Did you try with "-PintegrationTesting"?
I see:
{noformat}
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 25.36 s
<<< FAILURE! -- in org.apache.jackrabbit.j2ee.TomcatIT
[ERROR] org.apache.jackrabbit.j2ee.TomcatIT.testTomcat -- Time elapsed: 25.18 s
<<< FAILURE!
junit.framework.ComparisonFailure: expected: but
was:
at junit.framework.Assert.assertEquals(Assert.java:100)
at junit.framework.Assert.assertEquals(Assert.java:107)
at junit.framework.TestCase.assertEquals(TestCase.java:260)
at org.apache.jackrabbit.j2ee.TomcatIT.testTomcat(TomcatIT.java:138)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at junit.framework.TestCase.runTest(TestCase.java:177)
at junit.framework.TestCase.runBare(TestCase.java:142)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:130)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at junit.framework.TestSuite.run(TestSuite.java:236)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
{noformat}
was (Author: reschke):
Did you try with "-PintegrationTesting"?
I see:
{noformat}
(...)
{noformat}
> support the jakarta.servlet package name
>
>
> Key: JCR-4892
> URL: https://issues.apache.org/jira/browse/JCR-4892
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 2.24
>
> Attachments: JCR-4892_v2_project_root.patch,
> JCR-4892_v2_workspace_root.patch, JCR-4892_v3.patch, JCR-4892_v4.patch, clean
> install-Output.txt, jackrabbit-webdav-jakarta.patch, patch.txt, webapp.patch,
> webapp2.patch
>
>
> ...without breaking existing uses for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (JCRVLT-747) Import of authorizable nodes appears not to process "{BinaryRef}" property values
[
https://issues.apache.org/jira/browse/JCRVLT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCRVLT-747.
---
Fix Version/s: 3.7.4
Resolution: Fixed
> Import of authorizable nodes appears not to process "{BinaryRef}" property
> values
> -
>
> Key: JCRVLT-747
> URL: https://issues.apache.org/jira/browse/JCRVLT-747
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Fix For: 3.7.4
>
>
> It appears that import of authorizable nodes will not process binary
> properties using the '\{BinaryRef}' format. Instead, their values are passed
> to the JCR's XML import handler, which then complains about the value not
> being base64-encoded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCR-4892) support the jakarta.servlet package name
[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862441#comment-17862441
]
Julian Reschke commented on JCR-4892:
-
Did you try with "-PintegrationTesting"?
I see:
{noformat}
(...)
{noformat}
> support the jakarta.servlet package name
>
>
> Key: JCR-4892
> URL: https://issues.apache.org/jira/browse/JCR-4892
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
>Reporter: Julian Reschke
>Priority: Major
> Fix For: 2.24
>
> Attachments: JCR-4892_v2_project_root.patch,
> JCR-4892_v2_workspace_root.patch, JCR-4892_v3.patch, JCR-4892_v4.patch, clean
> install-Output.txt, jackrabbit-webdav-jakarta.patch, patch.txt, webapp.patch,
> webapp2.patch
>
>
> ...without breaking existing uses for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JCRVLT-747) Import of authorizable nodes appears not to process "{BinaryRef}" property values
[
https://issues.apache.org/jira/browse/JCRVLT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17861157#comment-17861157
]
Julian Reschke edited comment on JCRVLT-747 at 7/1/24 1:34 PM:
---
PR updated and ready for review (the problem I was facing previously was that I
did not take recursion into account).
was (Author: reschke):
PR updated and ready for review (the problem I was facing previously was that I
did not take recursiion into account).
> Import of authorizable nodes appears not to process "{BinaryRef}" property
> values
> -
>
> Key: JCRVLT-747
> URL: https://issues.apache.org/jira/browse/JCRVLT-747
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> It appears that import of authorizable nodes will not process binary
> properties using the '\{BinaryRef}' format. Instead, their values are passed
> to the JCR's XML import handler, which then complains about the value not
> being base64-encoded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCRVLT-747) Import of authorizable nodes appears not to process "{BinaryRef}" property values
[
https://issues.apache.org/jira/browse/JCRVLT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17861157#comment-17861157
]
Julian Reschke commented on JCRVLT-747:
---
PR updated and ready for review (the problem I was facing previously was that I
did not take recursiion into account).
> Import of authorizable nodes appears not to process "{BinaryRef}" property
> values
> -
>
> Key: JCRVLT-747
> URL: https://issues.apache.org/jira/browse/JCRVLT-747
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> It appears that import of authorizable nodes will not process binary
> properties using the '\{BinaryRef}' format. Instead, their values are passed
> to the JCR's XML import handler, which then complains about the value not
> being base64-encoded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCRVLT-747) Import of authorizable nodes appears not to process "{BinaryRef}" property values
[
https://issues.apache.org/jira/browse/JCRVLT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856773#comment-17856773
]
Julian Reschke commented on JCRVLT-747:
---
OK; I believe I have confirmed my theory -- added an "early fail" into
JcrSysViewTransformer (see PR).
Now the question is: can we handle that, like:
a) replace reference properties by empty binaries inside "startNode" (that
seems to work)
b) collect the skipped properties for setting in a later step? (that's what I
couldn't get working yet, would we do that in "endNode"?)
> Import of authorizable nodes appears not to process "{BinaryRef}" property
> values
> -
>
> Key: JCRVLT-747
> URL: https://issues.apache.org/jira/browse/JCRVLT-747
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> It appears that import of authorizable nodes will not process binary
> properties using the '\{BinaryRef}' format. Instead, their values are passed
> to the JCR's XML import handler, which then complains about the value not
> being base64-encoded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCRVLT-747) Import of authorizable nodes appears not to process "{BinaryRef}" property values
[
https://issues.apache.org/jira/browse/JCRVLT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856516#comment-17856516
]
Julian Reschke commented on JCRVLT-747:
---
So, as far as I understand:
- JcrSysViewTransformer is used for authorizables
(https://github.com/apache/jackrabbit-filevault/blob/a6f3ccf2d2728265fb50e62ed41e39dc5649d7c8/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewImporter.java#L754)
- that transformer is used to feed data into JCR's sysview import
- but that does not support binary references (by definition)
If this is the case, it might be possible to pass in an empty binary, do the
import, and then "patch" it with the binaryref value once created.
> Import of authorizable nodes appears not to process "{BinaryRef}" property
> values
> -
>
> Key: JCRVLT-747
> URL: https://issues.apache.org/jira/browse/JCRVLT-747
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> It appears that import of authorizable nodes will not process binary
> properties using the '\{BinaryRef}' format. Instead, their values are passed
> to the JCR's XML import handler, which then complains about the value not
> being base64-encoded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (JCRVLT-747) Import of authorizable nodes appears not to process "{BinaryRef}" property values
[
https://issues.apache.org/jira/browse/JCRVLT-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825367#comment-17825367
]
Julian Reschke edited comment on JCRVLT-747 at 6/20/24 1:26 PM:
Ok, I *believe* I have a test (ugly). See
https://github.com/apache/jackrabbit-filevault/pull/333
To run:
{noformat}
mvn clean install -Dit.test=BinaryPropertiesIT
{noformat}
Result:
{noformat}
16:53:18.286 [main] ERROR o.a.j.v.p.impl.ZipVaultPackage - Error during install.
javax.jcr.RepositoryException:
org.apache.jackrabbit.vault.fs.io.DocViewParser$XmlParseException: specified
data is not base64 encoded
at
org.apache.jackrabbit.vault.fs.impl.io.AbstractArtifactHandler.importDocView(AbstractArtifactHandler.java:187)
at
org.apache.jackrabbit.vault.fs.impl.io.GenericArtifactHandler.accept(GenericArtifactHandler.java:88)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1115)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:976)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:531)
at
org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.extract(ZipVaultPackage.java:284)
at
org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.extract(ZipVaultPackage.java:168)
at
org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.extract(ZipVaultPackage.java:175)
at
org.apache.jackrabbit.vault.packaging.integration.BinaryPropertiesIT.exportBinary(BinaryPropertiesIT.java:246)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:316)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:240)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:214)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:155)
at
[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=17855540#comment-17855540 ] Julian Reschke commented on JCRVLT-754: --- Works for me (but note you have a typo: "DvEPENDENCIES"). > 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 > > Attachments: JCRVLT-754-1.patch > > > 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] [Closed] (JCR-5072) Release Jackrabbit 2.22.0
[ https://issues.apache.org/jira/browse/JCR-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-5072. --- > Release Jackrabbit 2.22.0 > - > > Key: JCR-5072 > URL: https://issues.apache.org/jira/browse/JCR-5072 > Project: Jackrabbit Content Repository > Issue Type: Task >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
