Re: FileVault: Require Java 8
Hi, ok. So from the jackrabbit / oak side we have: - Jackrabbit 2.18 - recommended version for Java 8 and newer - Jackrabbit 2.16 - Java 8 and newer - Jackrabbit 2.14 - recommended version for Java 7 - “end of life” planned for Spring 2022 - Apache Jackrabbit Oak 1.16.0 (Java 8 and later) - Apache Jackrabbit Oak 1.10.x (Java 8 and later) - Apache Jackrabbit Oak 1.8.x (Java 8 and later) - Apache Jackrabbit Oak 1.6.x (Java 7 and later) The relevant part for the vault-core osgi bundle is the dependency on the jackrabbit APIs. It has no direct bundle dependency to Oak. Also, it doesn't embed any other bundles, so as long as the APIs stay Java version independent, it should all work. As for the CLI, we ignore the java7 compatibility and just include the respective jackrabbit components that are needed (but again, no oak needed). So the only things I'm concerned with are actuall API changes in the Jackrabbit API that are relevant for FileVault. For example fixes in Filevault that use new features in org.apache.jackrabbit.api.security.* that would force a AEM 6.3/Java7 customer to use Jackrabbit 2.18. So far we were lucky and didn't use any new Jackrabbit API for a long time I guess :-) Anyways I would keep 3.2.8 as the current 3.2.x release, create a 3.2 branch and hope for the best :-) And then start with 3.4 (Java 8, Jackrabbit 2.18, Oak 1.16) WDYT? Regards, Toby > On 3 Sep 2019, at 23:27, Konrad Windszus wrote: > > I am a bit confused, > Jackrabbit 2.16 requires Java 8 already and was already required with > filevault 3.2.8 > (https://github.com/apache/jackrabbit-filevault/blob/5104a49b4b0fcd25bfbcc202734cca490e55765d/parent/pom.xml#L43) > Oak 1.6 on the other hand still supports Java 7 (it depends on Jackrabbit > 2.14 -> > https://github.com/apache/jackrabbit-oak/blob/024278e1e33935bb30729a36252a1c93cc0e0d18/oak-parent/pom.xml#L45) > > So why is the combination of Oak 1.6 / Jackrabbit 2.16 necessary? I would > understand Oak 1.6 / Jackrabbit 2.14 (AEM 6.3, still supports Java 7). > What should we now target for the next 3.x release? > > Thanks, > Konrad > >> On 26. Aug 2019, at 19:54, Tobias Bocanegra wrote: >> >> Hi, >> >> The problem is, that we need oak 1.6 / jackrabbit 2.16 compatible version of >> filevault. I think that >> https://issues.apache.org/jira/browse/JCRVLT-340 might already changed that. >> If so, we need to update >> The major version and jump to 4.0.0, if filevault no longer works with oak >> 1.16. >> And then we also need to start a dedicated 3.x branch for back ports. >> >> Regards, Toby >> >> >>> On 26 Aug 2019, at 05:00, Konrad Windszus wrote: >>> >>> Hi, currently FileVault is still supporting Java 7. >>> But with https://issues.apache.org/jira/browse/JCRVLT-344 we implicitly >>> require Java 8 (due to the dependency towards Oak 1.16 and Jackrabbit 2.18). >>> Is it fine if with the next release version (3.2.10) we require Java 8? Or >>> should we rather increase the second digit, i.e. release 3.4.0? >>> >>> Is Filevault using the same Odd/Even release policy as Jackrabbit/Oak? >>> >>> In any case I would strongly recommend to upgrade then also the FileVault >>> Maven Plugin to Java 8. >>> WDYT? >>> Konrad >>> >>> >> >
[jira] [Resolved] (JCRVLT-359) Provide separate option to control handling of rep:cugPolicy nodes.
[ https://issues.apache.org/jira/browse/JCRVLT-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra resolved JCRVLT-359. - Fix Version/s: 3.2.10 Resolution: Fixed fixed in r1866426 > Provide separate option to control handling of rep:cugPolicy nodes. > --- > > Key: JCRVLT-359 > URL: https://issues.apache.org/jira/browse/JCRVLT-359 > Project: Jackrabbit FileVault > Issue Type: Bug > Components: vlt >Affects Versions: 3.2.8 >Reporter: Alexei Krainiouk >Priority: Major > Fix For: 3.2.10 > > > Currently handling of rep:cugPolicy nodes is controlled by aclHandling > configuration option that equally affects ACLs and CUGs. We need to control > them separately as for replication that is based on sling-distribution we > need to ignore ACLs while overwriting CUGs -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCRVLT-341) https doesn't work anymore
[
https://issues.apache.org/jira/browse/JCRVLT-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922947#comment-16922947
]
Tobias Bocanegra commented on JCRVLT-341:
-
you are correct. the Java 8 dependency is IMO only really relevant for the
vault-core osgi bundle. the jackrabbit spi dependency is only directly used in
the CLI and the RCP service. but the RCP service expects the jackrabbit-spi to
be present in the system already. so, we might be actually good :-) in this
case.
but if we add changes that require a new jackrabbit-api, that only come with a
jackrabbit/oak version that requires java 8, a customer might not be able to
upgrade, if he's stuck with java 7 (e.g. using IBM JDK).
> https doesn't work anymore
> --
>
> Key: JCRVLT-341
> URL: https://issues.apache.org/jira/browse/JCRVLT-341
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: RCP, vlt
>Affects Versions: 3.1.44, 3.2.6, 3.2.8
> Environment: source instance is suse linux sles 12
> target instance is suse linux sles 12 and windows 10
> java 1.8
> AEM 6.4.4
>Reporter: WalterSteiner
>Assignee: Tobias Bocanegra
>Priority: Major
> Fix For: 3.2.10
>
>
> org.apache.jackrabbit.vault.rcp-3.1.24 introduced support of https. I now
> upgraded to the version 3.2.8. I want to transfer with the following path
> "/content/etc/robots.txt" from one aem-author instance to another. I get the
> following log entry
> 16.07.2019 10:52:52.827 *ERROR* [Vault RCP Task - copy-contentetcrobots.txt]
> org.apache.jackrabbit.vault.util.RepositoryCopier Error while retrieving src
> node /content/etc/robots.txt: javax.jcr.PathNotFoundException:
> /content/etc/robots.txt
> In the source, this path exists. If I do the same with http. The path is
> found and the content transfered.
> I use the following json to create the tast in aem
> {code}
> {
> "cmd":"create",
> "id":"copy-contentetcrobots.txt",
>
> "src":"https://user:password@host:port/crx/server/crx.default/jcr:root/content/etc/robots.txt;,
> "dst":"/content/etc/robots.txt",
> "batchsize": 2048,
> "update": true,
> "onlyNewer": true,
> "recursive": true,
> "throttle": 1,
> "excludes": []
> }
> {code}
> Please fix this issue, because we are no longer allowed to use http in our
> company.
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
Re: Lucene Index Extraction
Sounds like a bug to me. Can you please open an issue? --Vikas (sent from mobile) On Thu, 5 Sep, 2019, 01:23 jorgeeflorez ., wrote: > Hello, > > I am trying to extract a Lucene index from a Repository stored in MongoDB. > I tried to use oak-run (1.12.0) as depicted in > https://jackrabbit.apache.org/oak/docs/query/lucene.html#luke (I > downloaded > the jar) but no luck so far. > > This is what I get when I try to get index info: > > C:\Users\Jorge Eduardo\Desktop>java -jar oak-run-1.12.0.jar console > --read-write mongodb://localhost:37017/rRepo4 > Apache Jackrabbit Oak 1.12.0 > Jackrabbit Oak Shell (Apache Jackrabbit Oak 1.12.0, JVM: 1.8.0_191) > Type ':help' or ':h' for help. > > --- > /> lc info /oak:index/LuceneFullText > ERROR groovy.lang.GroovyRuntimeException: > Could not find matching constructor for: > > org.apache.jackrabbit.oak.plugins.index.lucene.directory.OakDirectory(org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder, > org.apache.jackrabbit.oak.plugins.index.search.IndexDefinition, > java.lang.Boolean) > at > org.apache.jackrabbit.oak.console.commands.LuceneCommand.getDirectory > (LuceneCommand.groovy:132) > at > org.apache.jackrabbit.oak.console.commands.LuceneCommand$_closure1.doCall > (LuceneCommand.groovy:54) > at java_lang_Runnable$run.call (Unknown Source) > at org.apache.jackrabbit.oak.console.GroovyConsole$OakSh.run > (GroovyConsole.groovy:265) > at org.apache.jackrabbit.oak.console.GroovyConsole.run > (GroovyConsole.groovy:74) > at org.apache.jackrabbit.oak.console.Console.main (Console.java:74) > at org.apache.jackrabbit.oak.run.ConsoleCommand.execute > (ConsoleCommand.java:27) > at org.apache.jackrabbit.oak.run.Main.main (Main.java:49) > /> > > Similiar error if I try to dump the index: > C:\Users\Jorge Eduardo\Desktop>java -jar oak-run-1.12.0.jar console > mongodb://localhost:37017/rRepo4 > Apache Jackrabbit Oak 1.12.0 > Repository connected in read-only mode. Use '--read-write' for write > operations > Jackrabbit Oak Shell (Apache Jackrabbit Oak 1.12.0, JVM: 1.8.0_191) > Type ':help' or ':h' for help. > > --- > /> lc dump "C:\Users\Jorge Eduardo\Desktop\lc" /oak:index/LuceneFullText > ERROR groovy.lang.GroovyRuntimeException: > Could not find matching constructor for: > > org.apache.jackrabbit.oak.plugins.index.lucene.directory.OakDirectory(org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder, > org.apache.jackrabbit.oak.plugins.index.search.IndexDefinition, > java.lang.Boolean) > at > org.apache.jackrabbit.oak.console.commands.LuceneCommand.getDirectory > (LuceneCommand.groovy:132) > at > org.apache.jackrabbit.oak.console.commands.LuceneCommand$_closure2.doCall > (LuceneCommand.groovy:77) > at java_lang_Runnable$run.call (Unknown Source) > at org.apache.jackrabbit.oak.console.GroovyConsole$OakSh.run > (GroovyConsole.groovy:265) > at org.apache.jackrabbit.oak.console.GroovyConsole.run > (GroovyConsole.groovy:74) > at org.apache.jackrabbit.oak.console.Console.main (Console.java:74) > at org.apache.jackrabbit.oak.run.ConsoleCommand.execute > (ConsoleCommand.java:27) > at org.apache.jackrabbit.oak.run.Main.main (Main.java:49) > > I am pretty certain that I am missing or misusing something, or just > ignoring some necessary condition that makes it work. > > Anyway, any help is greatly appreciated. > > Regards, > > Jorge Flórez >
Lucene Index Extraction
Hello, I am trying to extract a Lucene index from a Repository stored in MongoDB. I tried to use oak-run (1.12.0) as depicted in https://jackrabbit.apache.org/oak/docs/query/lucene.html#luke (I downloaded the jar) but no luck so far. This is what I get when I try to get index info: C:\Users\Jorge Eduardo\Desktop>java -jar oak-run-1.12.0.jar console --read-write mongodb://localhost:37017/rRepo4 Apache Jackrabbit Oak 1.12.0 Jackrabbit Oak Shell (Apache Jackrabbit Oak 1.12.0, JVM: 1.8.0_191) Type ':help' or ':h' for help. --- /> lc info /oak:index/LuceneFullText ERROR groovy.lang.GroovyRuntimeException: Could not find matching constructor for: org.apache.jackrabbit.oak.plugins.index.lucene.directory.OakDirectory(org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder, org.apache.jackrabbit.oak.plugins.index.search.IndexDefinition, java.lang.Boolean) at org.apache.jackrabbit.oak.console.commands.LuceneCommand.getDirectory (LuceneCommand.groovy:132) at org.apache.jackrabbit.oak.console.commands.LuceneCommand$_closure1.doCall (LuceneCommand.groovy:54) at java_lang_Runnable$run.call (Unknown Source) at org.apache.jackrabbit.oak.console.GroovyConsole$OakSh.run (GroovyConsole.groovy:265) at org.apache.jackrabbit.oak.console.GroovyConsole.run (GroovyConsole.groovy:74) at org.apache.jackrabbit.oak.console.Console.main (Console.java:74) at org.apache.jackrabbit.oak.run.ConsoleCommand.execute (ConsoleCommand.java:27) at org.apache.jackrabbit.oak.run.Main.main (Main.java:49) /> Similiar error if I try to dump the index: C:\Users\Jorge Eduardo\Desktop>java -jar oak-run-1.12.0.jar console mongodb://localhost:37017/rRepo4 Apache Jackrabbit Oak 1.12.0 Repository connected in read-only mode. Use '--read-write' for write operations Jackrabbit Oak Shell (Apache Jackrabbit Oak 1.12.0, JVM: 1.8.0_191) Type ':help' or ':h' for help. --- /> lc dump "C:\Users\Jorge Eduardo\Desktop\lc" /oak:index/LuceneFullText ERROR groovy.lang.GroovyRuntimeException: Could not find matching constructor for: org.apache.jackrabbit.oak.plugins.index.lucene.directory.OakDirectory(org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder, org.apache.jackrabbit.oak.plugins.index.search.IndexDefinition, java.lang.Boolean) at org.apache.jackrabbit.oak.console.commands.LuceneCommand.getDirectory (LuceneCommand.groovy:132) at org.apache.jackrabbit.oak.console.commands.LuceneCommand$_closure2.doCall (LuceneCommand.groovy:77) at java_lang_Runnable$run.call (Unknown Source) at org.apache.jackrabbit.oak.console.GroovyConsole$OakSh.run (GroovyConsole.groovy:265) at org.apache.jackrabbit.oak.console.GroovyConsole.run (GroovyConsole.groovy:74) at org.apache.jackrabbit.oak.console.Console.main (Console.java:74) at org.apache.jackrabbit.oak.run.ConsoleCommand.execute (ConsoleCommand.java:27) at org.apache.jackrabbit.oak.run.Main.main (Main.java:49) I am pretty certain that I am missing or misusing something, or just ignoring some necessary condition that makes it work. Anyway, any help is greatly appreciated. Regards, Jorge Flórez
adaptTo() 2019 - slides online
the slides of the adaptTo() 2019 conference in berlin are online - 25 talks plus lightning talks. you find the slides and code samples here: https://adapt.to/2019/schedule the talk videos and images are expected in 2-3 weeks - we will announce them when available. stefan
[jira] [Comment Edited] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919177#comment-16919177
]
Julian Reschke edited comment on JCR-4460 at 9/4/19 5:29 PM:
-
trunk: (2.19.4) [r1863384|http://svn.apache.org/r1863384]
[r1863222|http://svn.apache.org/r1863222]
2.18: (2.18.3) [r1863388|http://svn.apache.org/r1863388]
[r1863271|http://svn.apache.org/r1863271]
2.16: (2.16.5) [r1866114|http://svn.apache.org/r1866114]
2.14: [r1866411|http://svn.apache.org/r1866411]
was (Author: reschke):
trunk: (2.19.4) [r1863384|http://svn.apache.org/r1863384]
[r1863222|http://svn.apache.org/r1863222]
2.18: (2.18.3) [r1863388|http://svn.apache.org/r1863388]
[r1863271|http://svn.apache.org/r1863271]
2.16: [r1866114|http://svn.apache.org/r1866114]
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4460:
Labels: (was: candidate_jcr_2_14)
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4460) allow to run remoted conformance tests with a custom servlet context path
[
https://issues.apache.org/jira/browse/JCR-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4460:
Fix Version/s: 2.14.8
> allow to run remoted conformance tests with a custom servlet context path
> -
>
> Key: JCR-4460
> URL: https://issues.apache.org/jira/browse/JCR-4460
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr2dav
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8
>
> Attachments: servlet_path_prefix.patch, use-context-path.diff
>
>
> Add a system property that selects a servlet context path for testing.
> To run tests with non-root path:
> {noformat}
> mvn clean install -PintegrationTesting -DWebDAVServletContext="/foobar/"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4459: Labels: (was: candidate_jcr_2_14) > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922680#comment-16922680 ] Julian Reschke commented on JCR-4459: - trunk: (2.19.4) [r1863196|http://svn.apache.org/r1863196] 2.18: (2.18.3) [r1863249|http://svn.apache.org/r1863249] 2.16: (2.16.5) [r1866111|http://svn.apache.org/r1866111] 2.14: [r1866400|http://svn.apache.org/r1866400] > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4459: Fix Version/s: 2.14.8 > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (JCR-4459) Basic Authentication for HTTPS URIs does not work
[ https://issues.apache.org/jira/browse/JCR-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4459: Comment: was deleted (was: trunk: (2.19.4) [r1863196|http://svn.apache.org/r1863196] 2.18: (2.18.3) [r1863249|http://svn.apache.org/r1863249] 2.16: [r1866111|http://svn.apache.org/r1866111] ) > Basic Authentication for HTTPS URIs does not work > - > > Key: JCR-4459 > URL: https://issues.apache.org/jira/browse/JCR-4459 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-spi2dav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...because the auth cache is keyed by httpHost, and in the constructor, we > leave out the URI scheme. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4457) Update httpclient/mime dependencies to 4.5.9
[ https://issues.apache.org/jira/browse/JCR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874914#comment-16874914 ] Julian Reschke edited comment on JCR-4457 at 9/4/19 4:18 PM: - trunk: (2.19.4) [r1862283|http://svn.apache.org/r1862283] 2.18: (2.18.3) [r1863270|http://svn.apache.org/r1863270] 2.16: (2.16.5) [r1866104|http://svn.apache.org/r1866104] 2.14: [r1866399|http://svn.apache.org/r1866399] was (Author: reschke): trunk: (2.19.4) [r1862283|http://svn.apache.org/r1862283] 2.18: (2.18.3) [r1863270|http://svn.apache.org/r1863270] 2.16: [r1866104|http://svn.apache.org/r1866104] > Update httpclient/mime dependencies to 4.5.9 > > > Key: JCR-4457 > URL: https://issues.apache.org/jira/browse/JCR-4457 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-spi2dav, jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4457) Update httpclient/mime dependencies to 4.5.9
[ https://issues.apache.org/jira/browse/JCR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4457: Labels: (was: candidate_jcr_2_14) > Update httpclient/mime dependencies to 4.5.9 > > > Key: JCR-4457 > URL: https://issues.apache.org/jira/browse/JCR-4457 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-spi2dav, jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4457) Update httpclient/mime dependencies to 4.5.9
[ https://issues.apache.org/jira/browse/JCR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4457: Fix Version/s: 2.14.8 > Update httpclient/mime dependencies to 4.5.9 > > > Key: JCR-4457 > URL: https://issues.apache.org/jira/browse/JCR-4457 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-spi2dav, jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4455) condition index-rule handling more broken after JCR-4339
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915551#comment-16915551
]
Julian Reschke edited comment on JCR-4455 at 9/4/19 3:54 PM:
-
trunk: (2.19.4) [r1862805|http://svn.apache.org/r1862805]
[r1862783|http://svn.apache.org/r1862783]
2.18: (2.18.3) [r1865913|http://svn.apache.org/r1865913]
2.16: (2.16.5) [r1866101|http://svn.apache.org/r1866101]
2.14: [r1866397|http://svn.apache.org/r1866397
was (Author: reschke):
trunk: (2.19.4) [r1862805|http://svn.apache.org/r1862805]
[r1862783|http://svn.apache.org/r1862783]
2.18: (2.18.3) [r1865913|http://svn.apache.org/r1865913]
2.16: [r1866101|http://svn.apache.org/r1866101]
> condition index-rule handling more broken after JCR-4339
>
>
> Key: JCR-4455
> URL: https://issues.apache.org/jira/browse/JCR-4455
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: core
>Affects Versions: 2.18.2
>Reporter: Ate Douma
>Assignee: Claus Köll
>Priority: Major
> Labels: candidate_jcr_2_12
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8
>
> Attachments: JCR-4455.patch, exposing-JCR-4455.patch
>
>
> [~c_koell]
> When reviewing the fix applied for JCR-4339 before going through an upgrade
> to 2.18.2, I noticed that, while it fixes the reported problem, it does so
> only in simple ('happy path') scenarios. Now it is broken when trying to use
> multiple index-rule definitions for one node type.
> The logic for finding the applicable indexing rule for a specific property no
> longer considers (checks) if the there is a condition for that property.
> Instead, that check is postponed/moved to the method *calling*
> #getApplicableIndexingRule.
> But this is incorrect because now the #getApplicableIndexingRule method
> returns the first *type* matching rule, regardless of the *property* it
> should be applicable for.
> For example, it is perfectly feasible, and sometimes even needed, to have
> multiple index-rules for the same node type, like the following enhanced
> version of test resource indexing_config6.xml, which can be used to verify
> the logic now is broken:
> {code:xml}
>
> other
>
>
> foo
> {code}
> The important points to expose the new bug is:
> * the index-rule for property other is defined *before* the index-rule for
> property foo
> * (for this example) the index-rule for property other doesn't have a
> condition
> With the above, the property foo will *not* be indexed, regardless its value,
> because the first 'matching' rule returned from #getApplicableIndexingRule
> for a node of type nt:unstructured will be the rule for property other. But
> will always return false on the (now postponed/delegated) call to
> rule.isIndexed(propertyName: foo), because *that* rule doesn't has a
> propertyConfig for foo (only for other).
> I'll attach a patch (based on trunk) to demonstrate the above failing using
> the new IndexingConfigurationImplTest#testMatchCondition test.
> Note that the current #testMatchCondition() test itself also is broken: it
> actually *does not* test the intended condition, but tests for it to *not*
> match using assertFalse instead of assertTrue.
> Which indeed is needed to pass the test because the indexing_config6.xml
> configuration file itself contains an invalid (incomplete) index-rule.
> Instead of the current content:
> {code:xml}
>
> {code}
> it actually should be:
> {code:xml}
>
> foo
> {code}
> to pass the test with assertTrue.
> I'll also fix that test method in my patch, which then however will fail,
> because of the above reported problem.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4455) condition index-rule handling more broken after JCR-4339
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4455:
Labels: candidate_jcr_2_12 (was: candidate_jcr_2_14)
> condition index-rule handling more broken after JCR-4339
>
>
> Key: JCR-4455
> URL: https://issues.apache.org/jira/browse/JCR-4455
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: core
>Affects Versions: 2.18.2
>Reporter: Ate Douma
>Assignee: Claus Köll
>Priority: Major
> Labels: candidate_jcr_2_12
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8
>
> Attachments: JCR-4455.patch, exposing-JCR-4455.patch
>
>
> [~c_koell]
> When reviewing the fix applied for JCR-4339 before going through an upgrade
> to 2.18.2, I noticed that, while it fixes the reported problem, it does so
> only in simple ('happy path') scenarios. Now it is broken when trying to use
> multiple index-rule definitions for one node type.
> The logic for finding the applicable indexing rule for a specific property no
> longer considers (checks) if the there is a condition for that property.
> Instead, that check is postponed/moved to the method *calling*
> #getApplicableIndexingRule.
> But this is incorrect because now the #getApplicableIndexingRule method
> returns the first *type* matching rule, regardless of the *property* it
> should be applicable for.
> For example, it is perfectly feasible, and sometimes even needed, to have
> multiple index-rules for the same node type, like the following enhanced
> version of test resource indexing_config6.xml, which can be used to verify
> the logic now is broken:
> {code:xml}
>
> other
>
>
> foo
> {code}
> The important points to expose the new bug is:
> * the index-rule for property other is defined *before* the index-rule for
> property foo
> * (for this example) the index-rule for property other doesn't have a
> condition
> With the above, the property foo will *not* be indexed, regardless its value,
> because the first 'matching' rule returned from #getApplicableIndexingRule
> for a node of type nt:unstructured will be the rule for property other. But
> will always return false on the (now postponed/delegated) call to
> rule.isIndexed(propertyName: foo), because *that* rule doesn't has a
> propertyConfig for foo (only for other).
> I'll attach a patch (based on trunk) to demonstrate the above failing using
> the new IndexingConfigurationImplTest#testMatchCondition test.
> Note that the current #testMatchCondition() test itself also is broken: it
> actually *does not* test the intended condition, but tests for it to *not*
> match using assertFalse instead of assertTrue.
> Which indeed is needed to pass the test because the indexing_config6.xml
> configuration file itself contains an invalid (incomplete) index-rule.
> Instead of the current content:
> {code:xml}
>
> {code}
> it actually should be:
> {code:xml}
>
> foo
> {code}
> to pass the test with assertTrue.
> I'll also fix that test method in my patch, which then however will fail,
> because of the above reported problem.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4455) condition index-rule handling more broken after JCR-4339
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4455:
Fix Version/s: 2.14.8
> condition index-rule handling more broken after JCR-4339
>
>
> Key: JCR-4455
> URL: https://issues.apache.org/jira/browse/JCR-4455
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: core
>Affects Versions: 2.18.2
>Reporter: Ate Douma
>Assignee: Claus Köll
>Priority: Major
> Labels: candidate_jcr_2_14
> Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8
>
> Attachments: JCR-4455.patch, exposing-JCR-4455.patch
>
>
> [~c_koell]
> When reviewing the fix applied for JCR-4339 before going through an upgrade
> to 2.18.2, I noticed that, while it fixes the reported problem, it does so
> only in simple ('happy path') scenarios. Now it is broken when trying to use
> multiple index-rule definitions for one node type.
> The logic for finding the applicable indexing rule for a specific property no
> longer considers (checks) if the there is a condition for that property.
> Instead, that check is postponed/moved to the method *calling*
> #getApplicableIndexingRule.
> But this is incorrect because now the #getApplicableIndexingRule method
> returns the first *type* matching rule, regardless of the *property* it
> should be applicable for.
> For example, it is perfectly feasible, and sometimes even needed, to have
> multiple index-rules for the same node type, like the following enhanced
> version of test resource indexing_config6.xml, which can be used to verify
> the logic now is broken:
> {code:xml}
>
> other
>
>
> foo
> {code}
> The important points to expose the new bug is:
> * the index-rule for property other is defined *before* the index-rule for
> property foo
> * (for this example) the index-rule for property other doesn't have a
> condition
> With the above, the property foo will *not* be indexed, regardless its value,
> because the first 'matching' rule returned from #getApplicableIndexingRule
> for a node of type nt:unstructured will be the rule for property other. But
> will always return false on the (now postponed/delegated) call to
> rule.isIndexed(propertyName: foo), because *that* rule doesn't has a
> propertyConfig for foo (only for other).
> I'll attach a patch (based on trunk) to demonstrate the above failing using
> the new IndexingConfigurationImplTest#testMatchCondition test.
> Note that the current #testMatchCondition() test itself also is broken: it
> actually *does not* test the intended condition, but tests for it to *not*
> match using assertFalse instead of assertTrue.
> Which indeed is needed to pass the test because the indexing_config6.xml
> configuration file itself contains an invalid (incomplete) index-rule.
> Instead of the current content:
> {code:xml}
>
> {code}
> it actually should be:
> {code:xml}
>
> foo
> {code}
> to pass the test with assertTrue.
> I'll also fix that test method in my patch, which then however will fail,
> because of the above reported problem.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4454) update surefire-report-plugin dependency to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4454: Fix Version/s: 2.14.8 > update surefire-report-plugin dependency to 2.22.2 > -- > > Key: JCR-4454 > URL: https://issues.apache.org/jira/browse/JCR-4454 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4454) update surefire-report-plugin dependency to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4454: Labels: (was: candidate_jcr_2_14) > update surefire-report-plugin dependency to 2.22.2 > -- > > Key: JCR-4454 > URL: https://issues.apache.org/jira/browse/JCR-4454 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4454) update surefire-report-plugin dependency to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869455#comment-16869455 ] Julian Reschke edited comment on JCR-4454 at 9/4/19 3:35 PM: - trunk: (2.19.4) [r1861786|http://svn.apache.org/r1861786] 2.18: (2.18.3) [r1863269|http://svn.apache.org/r1863269] 2.16: (2.16.5) [r1866100|http://svn.apache.org/r1866100] 2.14: [r1866396|http://svn.apache.org/r1866396] was (Author: reschke): trunk: (2.19.4) [r1861786|http://svn.apache.org/r1861786] 2.18: (2.18.3) [r1863269|http://svn.apache.org/r1863269] 2.16: [r1866100|http://svn.apache.org/r1866100] > update surefire-report-plugin dependency to 2.22.2 > -- > > Key: JCR-4454 > URL: https://issues.apache.org/jira/browse/JCR-4454 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4453) update pmd-plugin dependency to 3.12.0
[ https://issues.apache.org/jira/browse/JCR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869440#comment-16869440 ] Julian Reschke edited comment on JCR-4453 at 9/4/19 2:24 PM: - trunk: (2.19.4) [r1861781|http://svn.apache.org/r1861781] 2.18: (2.18.3) [r1863264|http://svn.apache.org/r1863264] 2.16: (2.16.5) [r1866099|http://svn.apache.org/r1866099] 2.14: [r1866392|http://svn.apache.org/r1866392] was (Author: reschke): trunk: (2.19.4) [r1861781|http://svn.apache.org/r1861781] 2.18: (2.18.3) [r1863264|http://svn.apache.org/r1863264] 2.16: [r1866099|http://svn.apache.org/r1866099] > update pmd-plugin dependency to 3.12.0 > -- > > Key: JCR-4453 > URL: https://issues.apache.org/jira/browse/JCR-4453 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4453) update pmd-plugin dependency to 3.12.0
[ https://issues.apache.org/jira/browse/JCR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4453: Labels: (was: candidate_jcr_2_14) > update pmd-plugin dependency to 3.12.0 > -- > > Key: JCR-4453 > URL: https://issues.apache.org/jira/browse/JCR-4453 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4453) update pmd-plugin dependency to 3.12.0
[ https://issues.apache.org/jira/browse/JCR-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4453: Fix Version/s: 2.14.8 > update pmd-plugin dependency to 3.12.0 > -- > > Key: JCR-4453 > URL: https://issues.apache.org/jira/browse/JCR-4453 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4452) update war-plugin dependency to 3.2.3
[ https://issues.apache.org/jira/browse/JCR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869418#comment-16869418 ] Julian Reschke edited comment on JCR-4452 at 9/4/19 2:05 PM: - trunk: (2.19.4) [r1861778|http://svn.apache.org/r1861778] 2.18: (2.18.3) [r1863263|http://svn.apache.org/r1863263] 2.16: (2.16.5) [r1866093|http://svn.apache.org/r1866093] 2.14: [r1866391|http://svn.apache.org/r1866391] was (Author: reschke): trunk: (2.19.4) [r1861778|http://svn.apache.org/r1861778] 2.18: (2.18.3) [r1863263|http://svn.apache.org/r1863263] 2.16: [r1866093|http://svn.apache.org/r1866093] > update war-plugin dependency to 3.2.3 > - > > Key: JCR-4452 > URL: https://issues.apache.org/jira/browse/JCR-4452 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4452) update war-plugin dependency to 3.2.3
[ https://issues.apache.org/jira/browse/JCR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4452: Fix Version/s: 2.14.8 > update war-plugin dependency to 3.2.3 > - > > Key: JCR-4452 > URL: https://issues.apache.org/jira/browse/JCR-4452 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4452) update war-plugin dependency to 3.2.3
[ https://issues.apache.org/jira/browse/JCR-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4452: Labels: (was: candidate_jcr_2_14) > update war-plugin dependency to 3.2.3 > - > > Key: JCR-4452 > URL: https://issues.apache.org/jira/browse/JCR-4452 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4451) update jar-plugin dependency to 3.1.2
[ https://issues.apache.org/jira/browse/JCR-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869405#comment-16869405 ] Julian Reschke edited comment on JCR-4451 at 9/4/19 1:31 PM: - trunk: (2.19.4) [r1861777|http://svn.apache.org/r1861777] 2.18: (2.18.3) [r1863258|http://svn.apache.org/r1863258] 2.16: (2.16.5) [r1866091|http://svn.apache.org/r1866091] 2.14: [r1866388|http://svn.apache.org/r1866388] was (Author: reschke): trunk: (2.19.4) [r1861777|http://svn.apache.org/r1861777] 2.18: (2.18.3) [r1863258|http://svn.apache.org/r1863258] 2.16: [r1866091|http://svn.apache.org/r1866091] > update jar-plugin dependency to 3.1.2 > - > > Key: JCR-4451 > URL: https://issues.apache.org/jira/browse/JCR-4451 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4451) update jar-plugin dependency to 3.1.2
[ https://issues.apache.org/jira/browse/JCR-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4451: Fix Version/s: 2.14.8 > update jar-plugin dependency to 3.1.2 > - > > Key: JCR-4451 > URL: https://issues.apache.org/jira/browse/JCR-4451 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4451) update jar-plugin dependency to 3.1.2
[ https://issues.apache.org/jira/browse/JCR-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4451: Labels: (was: candidate_jcr_2_14) > update jar-plugin dependency to 3.1.2 > - > > Key: JCR-4451 > URL: https://issues.apache.org/jira/browse/JCR-4451 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: [jira] [Created] (JCR-4464) Update Tika dependency to 1.22
UNSUBSCRIBE for god!!! Em ter, 20 de ago de 2019 às 07:53, Julian Reschke (Jira) escreveu: > Julian Reschke created JCR-4464: > --- > > Summary: Update Tika dependency to 1.22 > Key: JCR-4464 > URL: https://issues.apache.org/jira/browse/JCR-4464 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent > Affects Versions: 2.20 > Reporter: Julian Reschke > Assignee: Julian Reschke > > > > > > > -- > This message was sent by Atlassian Jira > (v8.3.2#803003) > -- att. Marcelo Taborda Vicente Cel: 55 (41) 9545-5084
[jira] [Updated] (JCR-4464) Update Tika dependency to 1.22
[ https://issues.apache.org/jira/browse/JCR-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4464: Labels: requires-java8 (was: candidate_jcr_2_14) > Update Tika dependency to 1.22 > -- > > Key: JCR-4464 > URL: https://issues.apache.org/jira/browse/JCR-4464 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: requires-java8 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4450) update checkstyle-plugin dependency to 3.1.0
[ https://issues.apache.org/jira/browse/JCR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4450: Labels: (was: candidate_jcr_2_14) > update checkstyle-plugin dependency to 3.1.0 > > > Key: JCR-4450 > URL: https://issues.apache.org/jira/browse/JCR-4450 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4450) update checkstyle-plugin dependency to 3.1.0
[ https://issues.apache.org/jira/browse/JCR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869397#comment-16869397 ] Julian Reschke edited comment on JCR-4450 at 9/4/19 1:11 PM: - trunk: (2.19.4) [r1861773|http://svn.apache.org/r1861773] 2.18: (2.18.3) [r1863255|http://svn.apache.org/r1863255] 2.16: (2.16.5) [r1866090|http://svn.apache.org/r1866090] 2.14: [r1866386|http://svn.apache.org/r1866386] was (Author: reschke): trunk: (2.19.4) [r1861773|http://svn.apache.org/r1861773] 2.18: (2.18.3) [r1863255|http://svn.apache.org/r1863255] 2.16: [r1866090|http://svn.apache.org/r1866090] > update checkstyle-plugin dependency to 3.1.0 > > > Key: JCR-4450 > URL: https://issues.apache.org/jira/browse/JCR-4450 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4450) update checkstyle-plugin dependency to 3.1.0
[ https://issues.apache.org/jira/browse/JCR-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4450: Fix Version/s: 2.14.8 > update checkstyle-plugin dependency to 3.1.0 > > > Key: JCR-4450 > URL: https://issues.apache.org/jira/browse/JCR-4450 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCRVLT-355) False error in case embedded file/subpackage is overwritten by jcrRootSourceDirectory
[
https://issues.apache.org/jira/browse/JCRVLT-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-355:
---
Fix Version/s: package-maven-plugin-1.0.5
> False error in case embedded file/subpackage is overwritten by
> jcrRootSourceDirectory
> -
>
> Key: JCRVLT-355
> URL: https://issues.apache.org/jira/browse/JCRVLT-355
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.4
>Reporter: Stefan Seifert
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: package-maven-plugin-1.0.5
>
>
> i've found problem with the check introduced with JCRVLT-279 - or i do not
> understand why the check leads to a failure in my case.
> i've two projects where this happens:
> 1. conf-content:
> https://github.com/stefanseifert/filevault-package-maven-plugin-1.0.4-validation-issues/tree/master/content-packages/conf-content
> fails with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
> (default-package) on project
> mycompany.myprojectgroup.myproject1.conf-content:
> org.apache.maven.plugin.MojoFailureException: Found duplicate files in
> content package, most probably you have overlapping filter roots or you embed
> a file which is already there in 'jcrRootSourceDirectory'. For details check
> the nested exception!: Duplicate file
> jcr_root\conf\myproject1\settings\wcm\policies was found and the duplicate
> attribute is 'fail'. {noformat}
> 2. ui.apps
> https://github.com/stefanseifert/filevault-package-maven-plugin-1.0.4-validation-issues/tree/master/content-packages/ui.apps
> fails with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
> (default-package) on project mycompany.myprojectgroup.myproject1.ui.apps:
> org.apache.maven.plugin.MojoFailureException: Found duplicate files in
> content package, most probably you have overlapping filter roots or you embed
> a file which is already there in 'jcrRootSourceDirectory'. For details check
> the nested exception!: Duplicate file
> jcr_root\apps\epsilon65Project\clientlibs\.content.xml was found and the
> duplicate attribute is 'fail'.
> {noformat}
> the second project is a special case because in some files in the
> "clientlibs" folder placeholders are replaced using maven resource filtering,
> if the corresponding build-helper-maven-plugin definition is removed the
> build works.
> but the first project is really simple project.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (JCR-4447) jackrabbit-jcr-commons: update cglib dependency
[ https://issues.apache.org/jira/browse/JCR-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856416#comment-16856416 ] Julian Reschke edited comment on JCR-4447 at 9/4/19 12:48 PM: -- trunk: (2.19.4) [r1860645|http://svn.apache.org/r1860645] 2.18: (2.18.3) [r1863254|http://svn.apache.org/r1863254] 2.16: (2.16.5) [r1866079|http://svn.apache.org/r1866079] 2.14: [r1866383|http://svn.apache.org/r1866383] was (Author: reschke): trunk: (2.19.4) [r1860645|http://svn.apache.org/r1860645] 2.18: (2.18.3) [r1863254|http://svn.apache.org/r1863254] 2.16: [r1866079|http://svn.apache.org/r1866079] > jackrabbit-jcr-commons: update cglib dependency > --- > > Key: JCR-4447 > URL: https://issues.apache.org/jira/browse/JCR-4447 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr-commons >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...and untangle it from the parent POM. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4447) jackrabbit-jcr-commons: update cglib dependency
[ https://issues.apache.org/jira/browse/JCR-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4447: Labels: (was: candidate_jcr_2_14) > jackrabbit-jcr-commons: update cglib dependency > --- > > Key: JCR-4447 > URL: https://issues.apache.org/jira/browse/JCR-4447 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr-commons >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...and untangle it from the parent POM. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4447) jackrabbit-jcr-commons: update cglib dependency
[ https://issues.apache.org/jira/browse/JCR-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4447: Fix Version/s: 2.14.8 > jackrabbit-jcr-commons: update cglib dependency > --- > > Key: JCR-4447 > URL: https://issues.apache.org/jira/browse/JCR-4447 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-jcr-commons >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > > ...and untangle it from the parent POM. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4442) Update animal-sniffer dependency to 1.18
[ https://issues.apache.org/jira/browse/JCR-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4442: Labels: requires-java8 (was: candidate_jcr_2_14) > Update animal-sniffer dependency to 1.18 > > > Key: JCR-4442 > URL: https://issues.apache.org/jira/browse/JCR-4442 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: requires-java8 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848774#comment-16848774 ] Julian Reschke edited comment on JCR-4441 at 9/4/19 12:25 PM: -- trunk: (2.19.4) [r1860118|http://svn.apache.org/r1860118] 2.18: (2.18.3) [r1863252|http://svn.apache.org/r1863252] 2.16: (2.16.5) [r1866076|http://svn.apache.org/r1866076] 2.14: [r1866381|http://svn.apache.org/r1866381] was (Author: reschke): trunk: (2.19.4) [r1860118|http://svn.apache.org/r1860118] 2.18: (2.18.3) [r1863252|http://svn.apache.org/r1863252] 2.16: [r1866076|http://svn.apache.org/r1866076] > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4441: Fix Version/s: 2.14.8 > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4441) Update surefire/failsafe dependencies to 2.22.2
[ https://issues.apache.org/jira/browse/JCR-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4441: Labels: (was: candidate_jcr_2_14) > Update surefire/failsafe dependencies to 2.22.2 > --- > > Key: JCR-4441 > URL: https://issues.apache.org/jira/browse/JCR-4441 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCRVLT-363) .content.xml of ancestor nodes not included in package
[
https://issues.apache.org/jira/browse/JCRVLT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922437#comment-16922437
]
Jakub Gorgolewski commented on JCRVLT-363:
--
Thanks for the link. Reg options presented by [~tripod], it looks like they
don't apply very well to my use case. When using overlay mechanic you:
# want to limit the footprint to absolute minimum to avoid conflict with other
overlays - the more specific path the better;
# probably cannot really use dependencies as those would list resources under
/libs and actual ancestor node would be under /apps.
> .content.xml of ancestor nodes not included in package
> --
>
> Key: JCRVLT-363
> URL: https://issues.apache.org/jira/browse/JCRVLT-363
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.4
>Reporter: Jakub Gorgolewski
>Priority: Minor
> Fix For: package-maven-plugin-1.0.5
>
> Attachments: ancestor-bug-example.zip,
> ancestor-package-test-pkg-1.0.0-SNAPSHOT.zip
>
>
> Packaging does not include ancestor node .content.xml files, for example if
> project has following files:
> {noformat}
> jcr_root/apps/wcm/core/resources
> jcr_root/apps/wcm/core/resources/.content.xml
> jcr_root/apps/wcm/core/resources/languages
> jcr_root/apps/wcm/core/resources/languages/.content.xml
> jcr_root/apps/wcm/core/resources/languages/_rep_policy.xml{noformat}
> And filter is set to:
> {code:java}
>
> {code}
> Then .content.xml for resources directory is still excluded with following
> warning:
> {noformat}
> [WARNING] File /.../jcr_root/apps/wcm/core/resources/.content.xml not covered
> by a filter rule and therefore not contained in the resulting package
> {noformat}
> This is required especially in case of /apps overloads where specific
> ancestor folders require specific primary type for package to successfully
> install (and those folders may or may not exist on target environment).
> Potential workaround for this issue is to use filters in following form:
> {code:java}
>
>
>
> {code}
> I'm attaching example project and resulting package.
> On related note, it seemed to have veen covered by test cases but recent
> commit removed .conent.xml files from expected list:
> [https://github.com/apache/jackrabbit-filevault-package-maven-plugin/commit/2d4a4490ebd0ffad3800789e839a5b322b9bab71#diff-48d0ab4fe7c714f2424acbe6b6ad7f2b]
> FYI [~kwin]
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (JCR-4439) disable baseline check for jackrabbit-bundle
[ https://issues.apache.org/jira/browse/JCR-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844807#comment-16844807 ] Julian Reschke edited comment on JCR-4439 at 9/4/19 12:00 PM: -- trunk: (2.19.4) [r1859633|http://svn.apache.org/r1859633] 2.18: (2.18.2) [r1859642|http://svn.apache.org/r1859642] 2.16: (2.16.5) [r1860268|http://svn.apache.org/r1860268] 2.14: [r1866378|http://svn.apache.org/r1866378] was (Author: reschke): trunk: [r1859633|http://svn.apache.org/r1859633] 2.18: (2.18.2) [r1859642|http://svn.apache.org/r1859642] 2.16: [r1860268|http://svn.apache.org/r1860268] > disable baseline check for jackrabbit-bundle > > > Key: JCR-4439 > URL: https://issues.apache.org/jira/browse/JCR-4439 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-bundle >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.18.2, 2.16.5, 2.19.4, 2.14.8 > > > ...because the package version numbers assigned here are meaningless anway. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4439) disable baseline check for jackrabbit-bundle
[ https://issues.apache.org/jira/browse/JCR-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4439: Labels: (was: candidate_jcr_2_14) > disable baseline check for jackrabbit-bundle > > > Key: JCR-4439 > URL: https://issues.apache.org/jira/browse/JCR-4439 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-bundle >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.18.2, 2.16.5, 2.19.4, 2.14.8 > > > ...because the package version numbers assigned here are meaningless anway. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4439) disable baseline check for jackrabbit-bundle
[ https://issues.apache.org/jira/browse/JCR-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4439: Fix Version/s: 2.14.8 > disable baseline check for jackrabbit-bundle > > > Key: JCR-4439 > URL: https://issues.apache.org/jira/browse/JCR-4439 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-bundle >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.18.2, 2.16.5, 2.19.4, 2.14.8 > > > ...because the package version numbers assigned here are meaningless anway. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCRVLT-189) Improve lazy loading of ZipStreamArchive
[
https://issues.apache.org/jira/browse/JCRVLT-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922419#comment-16922419
]
Konrad Windszus commented on JCRVLT-189:
Partly this is supported by the {{MemoryArchive}} which only extracts the
metadata but nothing else. The problem is that one still has to consume the
whole input stream even though usually the META-INF is contained in one of the
first entries...
> Improve lazy loading of ZipStreamArchive
>
>
> Key: JCRVLT-189
> URL: https://issues.apache.org/jira/browse/JCRVLT-189
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
>Affects Versions: 3.1.40
>Reporter: Tobias Bocanegra
>Priority: Major
>
> A lazy-loading mechanism on the ZipStreamArchive which allows to extract the
> metadata without actually creating the inflated copy (in memory or on a temp
> file) would be highly appreciated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCR-4438) jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging
[ https://issues.apache.org/jira/browse/JCR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4438: Labels: (was: candidate_jcr_2_14) > jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging > -- > > Key: JCR-4438 > URL: https://issues.apache.org/jira/browse/JCR-4438 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4438) jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging
[ https://issues.apache.org/jira/browse/JCR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4438: Fix Version/s: 2.14.8 > jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging > -- > > Key: JCR-4438 > URL: https://issues.apache.org/jira/browse/JCR-4438 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4438) jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging
[ https://issues.apache.org/jira/browse/JCR-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843959#comment-16843959 ] Julian Reschke edited comment on JCR-4438 at 9/4/19 11:39 AM: -- trunk: (2.19.4) [r1859563|http://svn.apache.org/r1859563] 2.18: (2.18.3) [r1863251|http://svn.apache.org/r1863251] 2.16: (2.16.5) [r1866075|http://svn.apache.org/r1866075] 2.14: [r1866377|http://svn.apache.org/r1866377] was (Author: reschke): trunk: (2.19.4) [r1859563|http://svn.apache.org/r1859563] 2.18: (2.18.3) [r1863251|http://svn.apache.org/r1863251] 2.16: [r1866075|http://svn.apache.org/r1866075] > jcr-webdav: AbstractLocatorFactory - fix Javadoc and add trace logging > -- > > Key: JCR-4438 > URL: https://issues.apache.org/jira/browse/JCR-4438 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webdav >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Trivial > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4437) Update Tika dependency to 1.21
[ https://issues.apache.org/jira/browse/JCR-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4437: Labels: requires-java8 (was: candidate_jcr_2_14) > Update Tika dependency to 1.21 > -- > > Key: JCR-4437 > URL: https://issues.apache.org/jira/browse/JCR-4437 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: requires-java8 > Fix For: 2.20, 2.16.5, 2.19.4, 2.18.3 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4400) Update tika dependency to 1.20
[ https://issues.apache.org/jira/browse/JCR-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4400: Labels: requires-java8 (was: ) > Update tika dependency to 1.20 > -- > > Key: JCR-4400 > URL: https://issues.apache.org/jira/browse/JCR-4400 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: requires-java8 > Fix For: 2.16.4, 2.20, 2.18.1, 2.19.1 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4428) update Apache parent pom to version 21
[ https://issues.apache.org/jira/browse/JCR-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820752#comment-16820752 ] Julian Reschke edited comment on JCR-4428 at 9/4/19 11:14 AM: -- trunk: (2.19.3) [r1857721|http://svn.apache.org/r1857721] 2.18: (2.18.2) [r1859059|http://svn.apache.org/r1859059] 2.16: (2.16.5) [r1860271|http://svn.apache.org/r1860271] 2.14: [r1866374|http://svn.apache.org/r1866374] was (Author: reschke): trunk: (2.19.3) [r1857721|http://svn.apache.org/r1857721] 2.18: (2.18.2) [r1859059|http://svn.apache.org/r1859059] 2.16: [r1860271|http://svn.apache.org/r1860271] > update Apache parent pom to version 21 > -- > > Key: JCR-4428 > URL: https://issues.apache.org/jira/browse/JCR-4428 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.19.3, 2.18.2, 2.16.5, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4428) update Apache parent pom to version 21
[ https://issues.apache.org/jira/browse/JCR-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4428: Fix Version/s: 2.14.8 > update Apache parent pom to version 21 > -- > > Key: JCR-4428 > URL: https://issues.apache.org/jira/browse/JCR-4428 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.19.3, 2.18.2, 2.16.5, 2.14.8 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4127) update to latest apache parent pom (18)
[ https://issues.apache.org/jira/browse/JCR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976762#comment-15976762 ] Julian Reschke edited comment on JCR-4127 at 9/4/19 10:33 AM: -- trunk: (2.15.2) [r1792066|http://svn.apache.org/r1792066] 2.14: [r1866372|http://svn.apache.org/r1866372] was (Author: reschke): trunk: [r1792066|http://svn.apache.org/r1792066] > update to latest apache parent pom (18) > --- > > Key: JCR-4127 > URL: https://issues.apache.org/jira/browse/JCR-4127 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.16, 2.15.2, 2.14.8 > > > https://svn.apache.org/viewvc/maven/pom/tags/apache-18/pom.xml?view=markup -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4127) update to latest apache parent pom (18)
[ https://issues.apache.org/jira/browse/JCR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4127: Fix Version/s: 2.14.8 > update to latest apache parent pom (18) > --- > > Key: JCR-4127 > URL: https://issues.apache.org/jira/browse/JCR-4127 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.16, 2.15.2, 2.14.8 > > > https://svn.apache.org/viewvc/maven/pom/tags/apache-18/pom.xml?view=markup -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (JCR-4425) NodeSetPrimaryTypeTest.testSetPrimaryType() must not use nt:activity
[ https://issues.apache.org/jira/browse/JCR-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849698#comment-16849698 ] Julian Reschke edited comment on JCR-4425 at 9/4/19 9:57 AM: - trunk: (2.19.3) [r1857631|http://svn.apache.org/r1857631] 2.18: (2.18.2) [r1857632|http://svn.apache.org/r1857632] 2.16: (2.16.5) [r1860266|http://svn.apache.org/r1860266] 2.14: [r1866371|http://svn.apache.org/r1866371] was (Author: reschke): trunk: (2.19.3) [r1857631|http://svn.apache.org/r1857631] 2.18: (2.18.2) [r1857632|http://svn.apache.org/r1857632] 2.16: [r1860266|http://svn.apache.org/r1860266] > NodeSetPrimaryTypeTest.testSetPrimaryType() must not use nt:activity > > > Key: JCR-4425 > URL: https://issues.apache.org/jira/browse/JCR-4425 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-jcr-tests >Affects Versions: 2.18.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 2.20, 2.19.3, 2.18.2, 2.16.5, 2.14.8 > > > The test should not use nt:activity as a node type for Node.setPrimaryType(). > Nodes with this type are only allowed under /jcr:system/jcr:activities. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4425) NodeSetPrimaryTypeTest.testSetPrimaryType() must not use nt:activity
[ https://issues.apache.org/jira/browse/JCR-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4425: Labels: (was: candidate_jcr_2_14) > NodeSetPrimaryTypeTest.testSetPrimaryType() must not use nt:activity > > > Key: JCR-4425 > URL: https://issues.apache.org/jira/browse/JCR-4425 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-jcr-tests >Affects Versions: 2.18.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Fix For: 2.20, 2.19.3, 2.18.2, 2.16.5, 2.14.8 > > > The test should not use nt:activity as a node type for Node.setPrimaryType(). > Nodes with this type are only allowed under /jcr:system/jcr:activities. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (JCR-4425) NodeSetPrimaryTypeTest.testSetPrimaryType() must not use nt:activity
[ https://issues.apache.org/jira/browse/JCR-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4425: Fix Version/s: 2.14.8 > NodeSetPrimaryTypeTest.testSetPrimaryType() must not use nt:activity > > > Key: JCR-4425 > URL: https://issues.apache.org/jira/browse/JCR-4425 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: jackrabbit-jcr-tests >Affects Versions: 2.18.0 >Reporter: Marcel Reutegger >Assignee: Marcel Reutegger >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.20, 2.19.3, 2.18.2, 2.16.5, 2.14.8 > > > The test should not use nt:activity as a node type for Node.setPrimaryType(). > Nodes with this type are only allowed under /jcr:system/jcr:activities. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JCRVLT-341) https doesn't work anymore
[
https://issues.apache.org/jira/browse/JCRVLT-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922321#comment-16922321
]
Konrad Windszus commented on JCRVLT-341:
The point is: Java 8 was introduced with JCRVLT-247 (namely with version
3.1.44) by upgrading the Jackrabbit dependency from 2.14 to 2.16:
https://github.com/apache/jackrabbit-filevault/commit/9eb53d36adfb7695a44075c72ca7ff0cedafabcc.
So all release since then already require Java 8. This were 5 releases with a
dependency to Jackrabbit 2.16 (already requiring Java 8)
> https doesn't work anymore
> --
>
> Key: JCRVLT-341
> URL: https://issues.apache.org/jira/browse/JCRVLT-341
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: RCP, vlt
>Affects Versions: 3.1.44, 3.2.6, 3.2.8
> Environment: source instance is suse linux sles 12
> target instance is suse linux sles 12 and windows 10
> java 1.8
> AEM 6.4.4
>Reporter: WalterSteiner
>Assignee: Tobias Bocanegra
>Priority: Major
> Fix For: 3.2.10
>
>
> org.apache.jackrabbit.vault.rcp-3.1.24 introduced support of https. I now
> upgraded to the version 3.2.8. I want to transfer with the following path
> "/content/etc/robots.txt" from one aem-author instance to another. I get the
> following log entry
> 16.07.2019 10:52:52.827 *ERROR* [Vault RCP Task - copy-contentetcrobots.txt]
> org.apache.jackrabbit.vault.util.RepositoryCopier Error while retrieving src
> node /content/etc/robots.txt: javax.jcr.PathNotFoundException:
> /content/etc/robots.txt
> In the source, this path exists. If I do the same with http. The path is
> found and the content transfered.
> I use the following json to create the tast in aem
> {code}
> {
> "cmd":"create",
> "id":"copy-contentetcrobots.txt",
>
> "src":"https://user:password@host:port/crx/server/crx.default/jcr:root/content/etc/robots.txt;,
> "dst":"/content/etc/robots.txt",
> "batchsize": 2048,
> "update": true,
> "onlyNewer": true,
> "recursive": true,
> "throttle": 1,
> "excludes": []
> }
> {code}
> Please fix this issue, because we are no longer allowed to use http in our
> company.
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JCRVLT-363) .content.xml of ancestor nodes not included in package
[
https://issues.apache.org/jira/browse/JCRVLT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922303#comment-16922303
]
Konrad Windszus commented on JCRVLT-363:
Please look at the comment in
https://issues.apache.org/jira/browse/JCRVLT-279?focusedCommentId=16684536=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16684536.
This was a deliberate change, but I am not convinced myself that this was a
wise decision. Maybe we should rethink it and rather restore the behaviour to
imitate the exporter functionality within the Maven plugin.
> .content.xml of ancestor nodes not included in package
> --
>
> Key: JCRVLT-363
> URL: https://issues.apache.org/jira/browse/JCRVLT-363
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.4
>Reporter: Jakub Gorgolewski
>Priority: Minor
> Fix For: package-maven-plugin-1.0.5
>
> Attachments: ancestor-bug-example.zip,
> ancestor-package-test-pkg-1.0.0-SNAPSHOT.zip
>
>
> Packaging does not include ancestor node .content.xml files, for example if
> project has following files:
> {noformat}
> jcr_root/apps/wcm/core/resources
> jcr_root/apps/wcm/core/resources/.content.xml
> jcr_root/apps/wcm/core/resources/languages
> jcr_root/apps/wcm/core/resources/languages/.content.xml
> jcr_root/apps/wcm/core/resources/languages/_rep_policy.xml{noformat}
> And filter is set to:
> {code:java}
>
> {code}
> Then .content.xml for resources directory is still excluded with following
> warning:
> {noformat}
> [WARNING] File /.../jcr_root/apps/wcm/core/resources/.content.xml not covered
> by a filter rule and therefore not contained in the resulting package
> {noformat}
> This is required especially in case of /apps overloads where specific
> ancestor folders require specific primary type for package to successfully
> install (and those folders may or may not exist on target environment).
> Potential workaround for this issue is to use filters in following form:
> {code:java}
>
>
>
> {code}
> I'm attaching example project and resulting package.
> On related note, it seemed to have veen covered by test cases but recent
> commit removed .conent.xml files from expected list:
> [https://github.com/apache/jackrabbit-filevault-package-maven-plugin/commit/2d4a4490ebd0ffad3800789e839a5b322b9bab71#diff-48d0ab4fe7c714f2424acbe6b6ad7f2b]
> FYI [~kwin]
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JCRVLT-341) https doesn't work anymore
[
https://issues.apache.org/jira/browse/JCRVLT-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922301#comment-16922301
]
Tobias Bocanegra commented on JCRVLT-341:
-
I would branch off 3.2.x and start with 4.0.0 only supporting java 8.
and then only include jackrabbit 2.18 there.
> https doesn't work anymore
> --
>
> Key: JCRVLT-341
> URL: https://issues.apache.org/jira/browse/JCRVLT-341
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: RCP, vlt
>Affects Versions: 3.1.44, 3.2.6, 3.2.8
> Environment: source instance is suse linux sles 12
> target instance is suse linux sles 12 and windows 10
> java 1.8
> AEM 6.4.4
>Reporter: WalterSteiner
>Assignee: Tobias Bocanegra
>Priority: Major
> Fix For: 3.2.10
>
>
> org.apache.jackrabbit.vault.rcp-3.1.24 introduced support of https. I now
> upgraded to the version 3.2.8. I want to transfer with the following path
> "/content/etc/robots.txt" from one aem-author instance to another. I get the
> following log entry
> 16.07.2019 10:52:52.827 *ERROR* [Vault RCP Task - copy-contentetcrobots.txt]
> org.apache.jackrabbit.vault.util.RepositoryCopier Error while retrieving src
> node /content/etc/robots.txt: javax.jcr.PathNotFoundException:
> /content/etc/robots.txt
> In the source, this path exists. If I do the same with http. The path is
> found and the content transfered.
> I use the following json to create the tast in aem
> {code}
> {
> "cmd":"create",
> "id":"copy-contentetcrobots.txt",
>
> "src":"https://user:password@host:port/crx/server/crx.default/jcr:root/content/etc/robots.txt;,
> "dst":"/content/etc/robots.txt",
> "batchsize": 2048,
> "update": true,
> "onlyNewer": true,
> "recursive": true,
> "throttle": 1,
> "excludes": []
> }
> {code}
> Please fix this issue, because we are no longer allowed to use http in our
> company.
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCRVLT-363) .content.xml of ancestor nodes not included in package
[
https://issues.apache.org/jira/browse/JCRVLT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-363:
---
Fix Version/s: package-maven-plugin-1.0.5
> .content.xml of ancestor nodes not included in package
> --
>
> Key: JCRVLT-363
> URL: https://issues.apache.org/jira/browse/JCRVLT-363
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
>Affects Versions: package-maven-plugin-1.0.4
>Reporter: Jakub Gorgolewski
>Priority: Minor
> Fix For: package-maven-plugin-1.0.5
>
> Attachments: ancestor-bug-example.zip,
> ancestor-package-test-pkg-1.0.0-SNAPSHOT.zip
>
>
> Packaging does not include ancestor node .content.xml files, for example if
> project has following files:
> {noformat}
> jcr_root/apps/wcm/core/resources
> jcr_root/apps/wcm/core/resources/.content.xml
> jcr_root/apps/wcm/core/resources/languages
> jcr_root/apps/wcm/core/resources/languages/.content.xml
> jcr_root/apps/wcm/core/resources/languages/_rep_policy.xml{noformat}
> And filter is set to:
> {code:java}
>
> {code}
> Then .content.xml for resources directory is still excluded with following
> warning:
> {noformat}
> [WARNING] File /.../jcr_root/apps/wcm/core/resources/.content.xml not covered
> by a filter rule and therefore not contained in the resulting package
> {noformat}
> This is required especially in case of /apps overloads where specific
> ancestor folders require specific primary type for package to successfully
> install (and those folders may or may not exist on target environment).
> Potential workaround for this issue is to use filters in following form:
> {code:java}
>
>
>
> {code}
> I'm attaching example project and resulting package.
> On related note, it seemed to have veen covered by test cases but recent
> commit removed .conent.xml files from expected list:
> [https://github.com/apache/jackrabbit-filevault-package-maven-plugin/commit/2d4a4490ebd0ffad3800789e839a5b322b9bab71#diff-48d0ab4fe7c714f2424acbe6b6ad7f2b]
> FYI [~kwin]
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (JCRVLT-363) .content.xml of ancestor nodes not included in package
Jakub Gorgolewski created JCRVLT-363:
Summary: .content.xml of ancestor nodes not included in package
Key: JCRVLT-363
URL: https://issues.apache.org/jira/browse/JCRVLT-363
Project: Jackrabbit FileVault
Issue Type: Bug
Components: package maven plugin
Affects Versions: package-maven-plugin-1.0.4
Reporter: Jakub Gorgolewski
Attachments: ancestor-bug-example.zip,
ancestor-package-test-pkg-1.0.0-SNAPSHOT.zip
Packaging does not include ancestor node .content.xml files, for example if
project has following files:
{noformat}
jcr_root/apps/wcm/core/resources
jcr_root/apps/wcm/core/resources/.content.xml
jcr_root/apps/wcm/core/resources/languages
jcr_root/apps/wcm/core/resources/languages/.content.xml
jcr_root/apps/wcm/core/resources/languages/_rep_policy.xml{noformat}
And filter is set to:
{code:java}
{code}
Then .content.xml for resources directory is still excluded with following
warning:
{noformat}
[WARNING] File /.../jcr_root/apps/wcm/core/resources/.content.xml not covered
by a filter rule and therefore not contained in the resulting package
{noformat}
This is required especially in case of /apps overloads where specific ancestor
folders require specific primary type for package to successfully install (and
those folders may or may not exist on target environment).
Potential workaround for this issue is to use filters in following form:
{code:java}
{code}
I'm attaching example project and resulting package.
On related note, it seemed to have veen covered by test cases but recent commit
removed .conent.xml files from expected list:
[https://github.com/apache/jackrabbit-filevault-package-maven-plugin/commit/2d4a4490ebd0ffad3800789e839a5b322b9bab71#diff-48d0ab4fe7c714f2424acbe6b6ad7f2b]
FYI [~kwin]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JCRVLT-341) https doesn't work anymore
[
https://issues.apache.org/jira/browse/JCRVLT-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922206#comment-16922206
]
Konrad Windszus commented on JCRVLT-341:
[~tripod] Is 2.18.3 acceptable (because it requires Java 8) or do we have to
wait for the 2.14.x release containing the fix?
> https doesn't work anymore
> --
>
> Key: JCRVLT-341
> URL: https://issues.apache.org/jira/browse/JCRVLT-341
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: RCP, vlt
>Affects Versions: 3.1.44, 3.2.6, 3.2.8
> Environment: source instance is suse linux sles 12
> target instance is suse linux sles 12 and windows 10
> java 1.8
> AEM 6.4.4
>Reporter: WalterSteiner
>Assignee: Tobias Bocanegra
>Priority: Major
> Fix For: 3.2.10
>
>
> org.apache.jackrabbit.vault.rcp-3.1.24 introduced support of https. I now
> upgraded to the version 3.2.8. I want to transfer with the following path
> "/content/etc/robots.txt" from one aem-author instance to another. I get the
> following log entry
> 16.07.2019 10:52:52.827 *ERROR* [Vault RCP Task - copy-contentetcrobots.txt]
> org.apache.jackrabbit.vault.util.RepositoryCopier Error while retrieving src
> node /content/etc/robots.txt: javax.jcr.PathNotFoundException:
> /content/etc/robots.txt
> In the source, this path exists. If I do the same with http. The path is
> found and the content transfered.
> I use the following json to create the tast in aem
> {code}
> {
> "cmd":"create",
> "id":"copy-contentetcrobots.txt",
>
> "src":"https://user:password@host:port/crx/server/crx.default/jcr:root/content/etc/robots.txt;,
> "dst":"/content/etc/robots.txt",
> "batchsize": 2048,
> "update": true,
> "onlyNewer": true,
> "recursive": true,
> "throttle": 1,
> "excludes": []
> }
> {code}
> Please fix this issue, because we are no longer allowed to use http in our
> company.
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JCRVLT-362) ZipStreamArchive does not expose correct input source to the META-INF resources
[
https://issues.apache.org/jira/browse/JCRVLT-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-362:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Fixed in http://svn.apache.org/r1866356.
> ZipStreamArchive does not expose correct input source to the META-INF
> resources
> ---
>
> Key: JCRVLT-362
> URL: https://issues.apache.org/jira/browse/JCRVLT-362
> Project: Jackrabbit FileVault
> Issue Type: Bug
>Affects Versions: 3.2.8
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: 3.2.10
>
>
> After calling {{open}} on a given {{ZipStreamArchive}} the {{getInputSource}}
> does not correctly expose access to the input stream of the entries below
> {{META-INF}}. This is due to the fact that the input stream of those entries
> are already consumed once
> https://github.com/apache/jackrabbit-filevault/blob/202e86a98226d1e3fda4a3f9278f174fc4c6094d/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/ZipStreamArchive.java#L158
> is reached. The solution would be to first copy to buffer/file and then read
> the meta inf from there.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
