[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Fix Version/s: 2.20.16 > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.26, 2.20.16 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827490#comment-17827490 ] Julian Reschke edited comment on JCR-5041 at 3/28/24 5:00 PM: -- trunk: (2.21.26-beta) [62017687a|https://github.com/apache/jackrabbit/commit/62017687a8efab6d37e53c72d95daae7851e0e8f] 2.20: [81bd119ec|https://github.com/apache/jackrabbit/commit/81bd119ec35314a8137e5c2c728949fc9bc599f5] was (Author: reschke): trunk: [62017687a|https://github.com/apache/jackrabbit-oak/commit/62017687a8efab6d37e53c72d95daae7851e0e8f] > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Fix For: 2.22, 2.21.26, 2.20.16 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Labels: (was: candidate_jackrabbit_2_20) > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Fix For: 2.22, 2.21.26, 2.20.16 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Labels: candidate_jackrabbit_2_20 (was: ) > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.26 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Fix Version/s: (was: 2.20.16) > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Fix For: 2.22, 2.21.26 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Fix Version/s: 2.20.16 > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.26, 2.20.16 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Labels: (was: candidate_jackrabbit_2_20) > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Fix For: 2.22, 2.21.26, 2.20.16 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827490#comment-17827490 ] Julian Reschke commented on JCR-5041: - trunk: [62017687a|https://github.com/apache/jackrabbit-oak/commit/62017687a8efab6d37e53c72d95daae7851e0e8f] > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.26 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Labels: candidate_jackrabbit_2_20 (was: ) > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.26 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-5041. - Fix Version/s: 2.22 2.21.26 Resolution: Fixed > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > Fix For: 2.22, 2.21.26 > > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-5041) Javadoc build is broken due to JCR 2.0 API docs being unavailable
[ https://issues.apache.org/jira/browse/JCR-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-5041: Summary: Javadoc build is broken due to JCR 2.0 API docs being unavailable (was: Javadoc build is broken) > Javadoc build is broken due to JCR 2.0 API docs being unavailable > - > > Key: JCR-5041 > URL: https://issues.apache.org/jira/browse/JCR-5041 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: parent >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Blocker > > As > https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0 > now fail with a 404. Apparently, this has started to fail in the last 48 > hours. > See > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/277/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555451#comment-17555451 ] Konrad Windszus commented on JCR-4732: -- All 4 links mentioned above are back online again. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554699#comment-17554699 ] Konrad Windszus edited comment on JCR-4732 at 6/15/22 4:45 PM: --- All original targets of our short URLs, namely # https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/index.html # https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/1.0/ # https://developer.adobe.com/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-1.0/ return a 404 again, but I have not found any other location. Hopefully just a temporary glitch was (Author: kwin): Both original targets of our short URLs, namely # https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/index.html and # https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ return a 404 again, but I have not found any other location. Hopefully just a temporary glitch > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554699#comment-17554699 ] Konrad Windszus commented on JCR-4732: -- Both original targets of our short URLs, namely # https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/2.0/index.html and # https://developer.adobe.com/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ return a 404 again, but I have not found any other location. Hopefully just a temporary glitch > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Closed] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-4732. --- > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4732: Resolution: Fixed Status: Resolved (was: Patch Available) Thanks, [~kwin]. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439069#comment-17439069 ] Konrad Windszus edited comment on JCR-4732 at 11/5/21, 2:45 PM: INFRA fixed deep linking and I prepared # a PR for Oak: https://github.com/apache/jackrabbit-oak/pull/409/files # a patch for Jackrabbit: [^JCR-4732-1.0.patch] and # a PR for FileVault: https://github.com/apache/jackrabbit-filevault/pull/177 was (Author: kwin): INFRA fixed deep linking and I prepared a PR for Oak: https://github.com/apache/jackrabbit-oak/pull/409/files and a patch for Jackrabbit: [^JCR-4732-1.0.patch] > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Assignee: Konrad Windszus Status: Patch Available (was: Open) > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439069#comment-17439069 ] Konrad Windszus edited comment on JCR-4732 at 11/5/21, 8:35 AM: INFRA fixed deep linking and I prepared a PR for Oak: https://github.com/apache/jackrabbit-oak/pull/409/files and a patch for Jackrabbit: [^JCR-4732-1.0.patch] was (Author: kwin): INFRA fixed deep linking and I prepared a PR for Oak: https://github.com/apache/jackrabbit-oak/pull/409/files > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Attachment: JCR-4732-1.0.patch > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > Attachments: JCR-4732-1.0.patch > > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) # https://docs.adobe.com/docs/en/spec/jcr/2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). was: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) # https://docs.adobe.com/docs/en/spec/jcr/2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/specs/javax.jcr/javadocs/jcr-1.0/ > # http://www.day.com/maven/jsr170/javadocs/jcr-1.0/ > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439069#comment-17439069 ] Konrad Windszus commented on JCR-4732: -- INFRA fixed deep linking and I prepared a PR for Oak: https://github.com/apache/jackrabbit-oak/pull/409/files > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428258#comment-17428258 ] Konrad Windszus edited comment on JCR-4732 at 11/5/21, 7:59 AM: I assume so (will try it out later), but I was more thinking about the links used on Jackrabbit/Oak the website. I just established: # https://s.apache.org/jcr-2.0-javadoc # https://s.apache.org/jcr-1.0-javadoc # https://s.apache.org/jcr-2.0-spec # https://s.apache.org/jcr-1.0-spec Will do some more tests with those links and then propose PRs/patches for documentation/pom.xml updates. was (Author: kwin): I assume so (will try it out later), but I was more thinking about the links used on Jackrabbit/Oak the website. I just established: # https://s.apache.org/jcr-2.0-javadoc and # https://s.apache.org/jcr-2.0-spec # https://s.apache.org/jcr-1.0-spec Will do some more tests with those links and then propose PRs/patches for documentation/pom.xml updates. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428258#comment-17428258 ] Konrad Windszus edited comment on JCR-4732 at 11/5/21, 7:57 AM: I assume so (will try it out later), but I was more thinking about the links used on Jackrabbit/Oak the website. I just established: # https://s.apache.org/jcr-2.0-javadoc and # https://s.apache.org/jcr-2.0-spec # https://s.apache.org/jcr-1.0-spec Will do some more tests with those links and then propose PRs/patches for documentation/pom.xml updates. was (Author: kwin): I assume so (will try it out later), but I was more thinking about the links used on Jackrabbit/Oak the website. I just established: # https://s.apache.org/jcr-2.0-javadoc and # https://s.apache.org/jcr-2.0-spec Will do some more tests with those links and then propose PRs/patches for documentation/pom.xml updates. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) # https://docs.adobe.com/docs/en/spec/jcr/2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). was: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/ (redirected) > # https://docs.adobe.com/docs/en/spec/jcr/2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > http
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). was: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). was: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jsr170/javadocs/jcr-2.0/ > # https://docs.adobe.com/docs/en/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428263#comment-17428263 ] Konrad Windszus edited comment on JCR-4732 at 10/13/21, 2:29 PM: - Currently s.apache.org does not support deep URL paths, i.e. https://s.apache.org/jcr-2.0-javadoc/index.html returns a 404 (No such short-URL!). I asked INFRA about that in https://issues.apache.org/jira/browse/INFRA-22406. was (Author: kwin): Currently s.apache.org does not support deep URL paths, i.e. https://s.apache.org/jcr-2.0-javadoc/index.html returns a 404. I asked INFRA about that in https://issues.apache.org/jira/browse/INFRA-22406. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428263#comment-17428263 ] Konrad Windszus commented on JCR-4732: -- Currently s.apache.org does not support deep URL paths, i.e. https://s.apache.org/jcr-2.0-javadoc/index.html returns a 404. I asked INFRA about that in https://issues.apache.org/jira/browse/INFRA-22406. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428258#comment-17428258 ] Konrad Windszus commented on JCR-4732: -- I assume so (will try it out later), but I was more thinking about the links used on Jackrabbit/Oak the website. I just established: # https://s.apache.org/jcr-2.0-javadoc and # https://s.apache.org/jcr-2.0-spec Will do some more tests with those links and then propose PRs/patches for documentation/pom.xml updates. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428218#comment-17428218 ] Julian Reschke commented on JCR-4732: - Will the javadoc tool follow redirects? > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428212#comment-17428212 ] Konrad Windszus commented on JCR-4732: -- I see, the license indeed seems incompatible with ASF. What about at least using https://s.apache.org/ for all outgoing references? That way we could easily adjust them in case the URL changes again in the future? > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17428177#comment-17428177 ] Julian Reschke commented on JCR-4732: - I agree with the goal. The issue here is that the Copyright both on the API and the spec IMHO do not allow us to do this. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable online hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe (apart from JSR which only provides the spec as zipped archive). As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. The download from http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only contains a Word document and a PDF of the spec though, so one needs to somehow convert to html. Although hosting the javadoc is straightforward it might be nice to apply some fixes (e.g. unclosed code tag in https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). was: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable online hosting location of the JCR 2.0 specification and > its javadoc has been Day/Adobe (apart from JSR which only provides the spec > as zipped archive). As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. > The download from > http://jcp.org/aboutJava/communityprocess/final/jsr283/index.html only > contains a Word document and a PDF of the spec though, so one needs to > somehow convert to html. > Although hosting the javadoc is straightforward it might be nice to apply > some fixes (e.g. unclosed code tag in > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/javax/jcr/Session.html#getNodeByIdentifier(java.lang.String)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427191#comment-17427191 ] Konrad Windszus edited comment on JCR-4732 at 10/11/21, 4:05 PM: - Here is a incomplete list of references towards JCR spec/javadocs: # https://jackrabbit.apache.org/jcr/jcr.html (broken link already) # https://jackrabbit.apache.org/jcr/jcr-api.html (broken link to JCR 1.0, outdated links to docs.adobe.com) # and a lot in https://github.com/apache/jackrabbit-oak/search?q=jcr-2.0 and https://github.com/apache/jackrabbit-oak/search?q=www.day.com was (Author: kwin): Here is a incomplete list of references towards JCR spec/javadocs: # https://jackrabbit.apache.org/jcr/jcr.html (broken link already) # https://jackrabbit.apache.org/jcr/jcr-api.html (broken link to JCR 1.0, outdated links to docs.adobe.com) # and a lot in https://github.com/apache/jackrabbit-oak/search?q=jcr-2.0. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ (broken) # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. was: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0 (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0 We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ (broken) > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html (redirected) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0/ (broken) > # http://www.day.com/maven/javax.jcr/javadocs/jcr-2.0/ (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0/ > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/ > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/specs/jcr/2.0/ # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0 (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0 We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. was: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0 (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0 We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/specs/jcr/2.0/ > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0 (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 > (no longer working) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0 > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0 (broken) # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0 We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. was: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/... > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # http://www.day.com/specs/javax.jcr/javadocs/jcr-2.0 (broken) > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 > (no longer working) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0 > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html We maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should host that in our own ASF website under a stable URL. was: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html And we maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should instead host that in our own ASF website. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/... > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 > (no longer working) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html > We maintain a lot of references towards it in our documentation, instead of > adjusting the URLs each time, we should host that in our own ASF website > under a stable URL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427191#comment-17427191 ] Konrad Windszus commented on JCR-4732: -- Here is a incomplete list of references towards JCR spec/javadocs: # https://jackrabbit.apache.org/jcr/jcr.html (broken link already) # https://jackrabbit.apache.org/jcr/jcr-api.html (broken link to JCR 1.0, outdated links to docs.adobe.com) # and a lot in https://github.com/apache/jackrabbit-oak/search?q=jcr-2.0. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/... > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 > (no longer working) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html > And we maintain a lot of references towards it in our documentation, instead > of adjusting the URLs each time, we should instead host that in our own ASF > website. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
[ https://issues.apache.org/jira/browse/JCR-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCR-4732: - Description: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html (seems to be the current one for JCR 2.0 spec) and # https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 (no longer working) # https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html And we maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should instead host that in our own ASF website. was: The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html And we maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should instead host that in our own ASF website. > Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org > - > > Key: JCR-4732 > URL: https://issues.apache.org/jira/browse/JCR-4732 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: docs >Reporter: Konrad Windszus >Priority: Major > > The only reliable hosting location of the JCR 2.0 specification and its > javadoc has been Day/Adobe. As the URLs changed quite often from > # http://www.day.com/... > # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html > # > https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html > (seems to be the current one for JCR 2.0 spec) > and > # > https://www.adobe.io/experience-manager/reference-materials/spec/javax.jcr/javadocs/jcr-2.0 > (no longer working) > # > https://www.adobe.io/experience-manager/reference-materials/spec/jsr170/javadocs/jcr-2.0/index.html > And we maintain a lot of references towards it in our documentation, instead > of adjusting the URLs each time, we should instead host that in our own ASF > website. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (JCR-4732) Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org
Konrad Windszus created JCR-4732: Summary: Host JCR 2.0 spec and its javadoc below https://jackrabbit.apache.org Key: JCR-4732 URL: https://issues.apache.org/jira/browse/JCR-4732 Project: Jackrabbit Content Repository Issue Type: Improvement Components: docs Reporter: Konrad Windszus The only reliable hosting location of the JCR 2.0 specification and its javadoc has been Day/Adobe. As the URLs changed quite often from # http://www.day.com/... # https://docs.adobe.com/content/docs/en/spec/jcr/2.0/index.html # https://www.adobe.io/experience-manager/reference-materials/spec/jcr/2.0/index.html And we maintain a lot of references towards it in our documentation, instead of adjusting the URLs each time, we should instead host that in our own ASF website. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 13.02.2020 11:46, Konrad Windszus wrote:
So what you are saying is basically that the part inside the {} must contain at least
one InvalidChar
(https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2
Names>) to make Jackrabbit/Oak detect it as a expanded name?
Yes, that's how it's supposed to work.
Why was the default namespace URI then defined as the empty string? That sounds
like a mistake to me.
That dates back way before JCR 2.0 (I also happen to disagree what the
default NS name should be anything except "").
Currently I cannot even do NameParser.parse()
(https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53
<https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53>)
for name = "wrongtype".
It throws an IllegalArgumentException:
java.lang.IllegalArgumentException: No namespaceURI specified
at
org.apache.jackrabbit.spi.commons.name.NameFactoryImpl.create(NameFactoryImpl.java:49)
at
org.apache.jackrabbit.spi.commons.conversion.NameParser.parse(NameParser.java:191)
with jackrabbit-spi-commons 2.20.0.
"wrongtype" is IMHO a totally valid qualified name, therefore it shouldn't
throw!
Is this a bug?
It might, but I doubt it.
Note that jackrabbit-spi-commons is a collection of classes used by the
*internal* Jackrabbit Service Provider interface (which, FWIW, never has
been completed for JCR 2.0).
From where are you using these classes?
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
Ok, I figured out the the NamespaceResolver is assumed to return "" for the
empty prefix.
I.e. after adding
@Override
public String getURI(String prefix) throws NamespaceException {
if (prefix.isEmpty()) {
return Name.NS_DEFAULT_URI;
}
it worked fine. Worth to mention this implicit assumption though in the javadoc
https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/namespace/NamespaceResolver.java#L38
<https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/namespace/NamespaceResolver.java#L38>.
Will open a PR for that.
> On 13. Feb 2020, at 11:46, Konrad Windszus wrote:
>
> So what you are saying is basically that the part inside the {} must contain
> at least one InvalidChar
> (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names
> <https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2
> Names>) to make Jackrabbit/Oak detect it as a expanded name?
> Why was the default namespace URI then defined as the empty string? That
> sounds like a mistake to me.
>
> Currently I cannot even do NameParser.parse()
> (https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53
>
> <https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53>)
> for name = "wrongtype".
> It throws an IllegalArgumentException:
>
> java.lang.IllegalArgumentException: No namespaceURI specified
> at
> org.apache.jackrabbit.spi.commons.name.NameFactoryImpl.create(NameFactoryImpl.java:49)
> at
> org.apache.jackrabbit.spi.commons.conversion.NameParser.parse(NameParser.java:191)
>
> with jackrabbit-spi-commons 2.20.0.
>
> "wrongtype" is IMHO a totally valid qualified name, therefore it shouldn't
> throw!
> Is this a bug?
>
> Konrad
>
>
>> On 11. Feb 2020, at 15:40, Julian Reschke wrote:
>>
>> On 11.02.2020 12:17, Konrad Windszus wrote:
>>> What should be the expanded name for the qualified name "foo" (without URI
>>> prefix) then?
>>
>> One could either say that there is none (and you don't need one), or
>> that it is "foo" (and raise a bug against the spec to say that missing
>> leading "{..." in an expanded name implies the empty namespace.
>>
>>> What namespace URI should be used then?
>>
>> If "foo" is in no namespace, and you need a namespace name, it would be
>> the empty string.
>>
>>> I am now totally lost to be honest.
>>
>> Yes, it's confusing.
>>
>> It's because in JCR 2.0, expanded names were introduced as an alternate
>> name notation, and we had to find a way not to let expanded names to
>> conflict with qualified names.
>>
>> The only way to make this work was to require the namespace name not to
>> be empty and to be a valid URI (which implies there's at least one ":"
>> in the namespace name).
>>
>> Best regards, Julian
>
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
So what you are saying is basically that the part inside the {} must contain at
least one InvalidChar
(https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2
Names>) to make Jackrabbit/Oak detect it as a expanded name?
Why was the default namespace URI then defined as the empty string? That sounds
like a mistake to me.
Currently I cannot even do NameParser.parse()
(https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53
<https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53>)
for name = "wrongtype".
It throws an IllegalArgumentException:
java.lang.IllegalArgumentException: No namespaceURI specified
at
org.apache.jackrabbit.spi.commons.name.NameFactoryImpl.create(NameFactoryImpl.java:49)
at
org.apache.jackrabbit.spi.commons.conversion.NameParser.parse(NameParser.java:191)
with jackrabbit-spi-commons 2.20.0.
"wrongtype" is IMHO a totally valid qualified name, therefore it shouldn't
throw!
Is this a bug?
Konrad
> On 11. Feb 2020, at 15:40, Julian Reschke wrote:
>
> On 11.02.2020 12:17, Konrad Windszus wrote:
>> What should be the expanded name for the qualified name "foo" (without URI
>> prefix) then?
>
> One could either say that there is none (and you don't need one), or
> that it is "foo" (and raise a bug against the spec to say that missing
> leading "{..." in an expanded name implies the empty namespace.
>
>> What namespace URI should be used then?
>
> If "foo" is in no namespace, and you need a namespace name, it would be
> the empty string.
>
>> I am now totally lost to be honest.
>
> Yes, it's confusing.
>
> It's because in JCR 2.0, expanded names were introduced as an alternate
> name notation, and we had to find a way not to let expanded names to
> conflict with qualified names.
>
> The only way to make this work was to require the namespace name not to
> be empty and to be a valid URI (which implies there's at least one ":"
> in the namespace name).
>
> Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
So what you are saying is basically that the part inside the {} must contain at
least one InvalidChar
(https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2%20Names
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2
Names>) to make Jackrabbit/Oak detect it as a expanded name?
Why was the default namespace URI then defined as the empty string? That sounds
like a mistake to me.
Currently I cannot even do NameParser.parse()
(https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53
<https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi-commons/src/main/java/org/apache/jackrabbit/spi/commons/conversion/NameParser.java#L53>)
for name = "wrongtype".
It throws an IllegalArgumentException:
java.lang.IllegalArgumentException: No namespaceURI specified
at
org.apache.jackrabbit.spi.commons.name.NameFactoryImpl.create(NameFactoryImpl.java:49)
at
org.apache.jackrabbit.spi.commons.conversion.NameParser.parse(NameParser.java:191)
with jackrabbit-spi-commons 2.20.0.
"wrongtype" is IMHO a totally valid qualified name, therefore it shouldn't
throw!
Is this a bug?
Konrad
> On 11. Feb 2020, at 15:40, Julian Reschke wrote:
>
> On 11.02.2020 12:17, Konrad Windszus wrote:
>> What should be the expanded name for the qualified name "foo" (without URI
>> prefix) then?
>
> One could either say that there is none (and you don't need one), or
> that it is "foo" (and raise a bug against the spec to say that missing
> leading "{..." in an expanded name implies the empty namespace.
>
>> What namespace URI should be used then?
>
> If "foo" is in no namespace, and you need a namespace name, it would be
> the empty string.
>
>> I am now totally lost to be honest.
>
> Yes, it's confusing.
>
> It's because in JCR 2.0, expanded names were introduced as an alternate
> name notation, and we had to find a way not to let expanded names to
> conflict with qualified names.
>
> The only way to make this work was to require the namespace name not to
> be empty and to be a valid URI (which implies there's at least one ":"
> in the namespace name).
>
> Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 11.02.2020 12:17, Konrad Windszus wrote:
What should be the expanded name for the qualified name "foo" (without URI
prefix) then?
One could either say that there is none (and you don't need one), or
that it is "foo" (and raise a bug against the spec to say that missing
leading "{..." in an expanded name implies the empty namespace.
What namespace URI should be used then?
If "foo" is in no namespace, and you need a namespace name, it would be
the empty string.
I am now totally lost to be honest.
Yes, it's confusing.
It's because in JCR 2.0, expanded names were introduced as an alternate
name notation, and we had to find a way not to let expanded names to
conflict with qualified names.
The only way to make this work was to require the namespace name not to
be empty and to be a valid URI (which implies there's at least one ":"
in the namespace name).
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 11.02.2020 12:17, Konrad Windszus wrote:
What should be the expanded name for the qualified name "foo" (without URI
prefix) then?
One could either say that there is none (and you don't need one), or
that it is "foo" (and raise a bug against the spec to say that missing
leading "{..." in an expanded name implies the empty namespace.
What namespace URI should be used then?
If "foo" is in no namespace, and you need a namespace name, it would be
the empty string.
I am now totally lost to be honest.
Yes, it's confusing.
It's because in JCR 2.0, expanded names were introduced as an alternate
name notation, and we had to find a way not to let expanded names to
conflict with qualified names.
The only way to make this work was to require the namespace name not to
be empty and to be a valid URI (which implies there's at least one ":"
in the namespace name).
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
What should be the expanded name for the qualified name "foo" (without URI
prefix) then?
What namespace URI should be used then?
I am now totally lost to be honest.
Konrad
> On 11. Feb 2020, at 12:01, Julian Reschke wrote:
>
> On 11.02.2020 11:52, Konrad Windszus wrote:
>> According to
>> https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.1%20Namespaces
>> <https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.1
>> Namespaces> an empty URI part is totally valid and should be used for
>> non-namespaced names!
>> ...
>
> I would call that a bug in the spec, at least in the context of expanded
> names.
>
> At the end of the day, "{}foo" is a valid local name, so it can't by
> definition not also be an expanded name.
>
> Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 11.02.2020 11:52, Konrad Windszus wrote:
According to
https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.1%20Namespaces
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.1
Namespaces>Â an empty URI part is totally valid and should be used for
non-namespaced names!
...
I would call that a bug in the spec, at least in the context of expanded
names.
At the end of the day, "{}foo" is a valid local name, so it can't by
definition not also be an expanded name.
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
According to
https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.1%20Namespaces
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.1
Namespaces> an empty URI part is totally valid and should be used for
non-namespaced names!
> On 11. Feb 2020, at 11:50, Julian Reschke wrote:
>
> On 11.02.2020 11:45, Konrad Windszus wrote:
>> Also according to
>> https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi/src/main/java/org/apache/jackrabbit/spi/Name.java#L39
>> the default namespace URI is the empty one!
>
> But that constant does not affect the name format
>
>>> On 11. Feb 2020, at 11:43, Konrad Windszus wrote:
>>>
>>> But I am generating this expanded form via
>>> DefaultNamePathResolver.getQName("newnode")
>>>
>>> This returns a org.apache.jackrabbit.spi.Name, whose toString() returns
>>> "{}newnode".
>>> Is the Name being returned by getQName then being wrong?
>
> Yes, please open a ticket.
>
> Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 11.02.2020 11:45, Konrad Windszus wrote:
Also according to
https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi/src/main/java/org/apache/jackrabbit/spi/Name.java#L39
the default namespace URI is the empty one!
But that constant does not affect the name format
On 11. Feb 2020, at 11:43, Konrad Windszus wrote:
But I am generating this expanded form via
DefaultNamePathResolver.getQName("newnode")
This returns a org.apache.jackrabbit.spi.Name, whose toString() returns
"{}newnode".
Is the Name being returned by getQName then being wrong?
Yes, please open a ticket.
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
Also according to
https://github.com/apache/jackrabbit/blob/b23d6734381e49f236c3705820126803555608b5/jackrabbit-spi/src/main/java/org/apache/jackrabbit/spi/Name.java#L39
the default namespace URI is the empty one!
> On 11. Feb 2020, at 11:43, Konrad Windszus wrote:
>
> But I am generating this expanded form via
> DefaultNamePathResolver.getQName("newnode")
>
> This returns a org.apache.jackrabbit.spi.Name, whose toString() returns
> "{}newnode".
> Is the Name being returned by getQName then being wrong?
>
>> On 11. Feb 2020, at 10:10, Julian Reschke wrote:
>>
>> On 11.02.2020 10:01, Konrad Windszus wrote:
>>> Thanks for the quick response.
>>> Indeed there seems to be an issue in Oak:
>>> After creating a node with its expanded form with system view format import
>>> below the root node I try to call
>>> node = rootNode.getNode("{}newnode");
>>>
>>> which throws
>>> javax.jcr.PathNotFoundException: newnode
>>> at
>>> org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:558)
>>> at
>>> org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:552)
>>> at
>>> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207)
>>> at
>>> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
>>> at
>>> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getNode(NodeImpl.java:552)
>>>
>>> The same works fine in Jackrabbit 2.x
>>> ...
>>
>> That actually looks like a bug in Jackrabbit, not Oak. See
>> <https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form>:
>>
>>> ExpandedName ::= '{' Namespace '}' LocalName
>>
>> The empty string is not a valid Namespace, so this parses as qualified
>> name instead.
>>
>> Best regards, Julian
>
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
But I am generating this expanded form via
DefaultNamePathResolver.getQName("newnode")
This returns a org.apache.jackrabbit.spi.Name, whose toString() returns
"{}newnode".
Is the Name being returned by getQName then being wrong?
> On 11. Feb 2020, at 10:10, Julian Reschke wrote:
>
> On 11.02.2020 10:01, Konrad Windszus wrote:
>> Thanks for the quick response.
>> Indeed there seems to be an issue in Oak:
>> After creating a node with its expanded form with system view format import
>> below the root node I try to call
>> node = rootNode.getNode("{}newnode");
>>
>> which throws
>> javax.jcr.PathNotFoundException: newnode
>> at
>> org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:558)
>> at
>> org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:552)
>> at
>> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207)
>> at
>> org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
>> at
>> org.apache.jackrabbit.oak.jcr.session.NodeImpl.getNode(NodeImpl.java:552)
>>
>> The same works fine in Jackrabbit 2.x
>> ...
>
> That actually looks like a bug in Jackrabbit, not Oak. See
> <https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form>:
>
>> ExpandedName ::= '{' Namespace '}' LocalName
>
> The empty string is not a valid Namespace, so this parses as qualified
> name instead.
>
> Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 11.02.2020 10:01, Konrad Windszus wrote:
Thanks for the quick response.
Indeed there seems to be an issue in Oak:
After creating a node with its expanded form with system view format import
below the root node I try to call
node = rootNode.getNode("{}newnode");
which throws
javax.jcr.PathNotFoundException: newnode
at
org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:558)
at
org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:552)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207)
at
org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
at
org.apache.jackrabbit.oak.jcr.session.NodeImpl.getNode(NodeImpl.java:552)
The same works fine in Jackrabbit 2.x
...
That actually looks like a bug in Jackrabbit, not Oak. See
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form>:
ExpandedName ::= '{' Namespace '}' LocalName
The empty string is not a valid Namespace, so this parses as qualified
name instead.
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 11.02.2020 10:01, Konrad Windszus wrote:
Thanks for the quick response.
Indeed there seems to be an issue in Oak:
After creating a node with its expanded form with system view format import
below the root node I try to call
node = rootNode.getNode("{}newnode");
which throws
javax.jcr.PathNotFoundException: newnode
at
org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:558)
at
org.apache.jackrabbit.oak.jcr.session.NodeImpl$7.perform(NodeImpl.java:552)
at
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:207)
at
org.apache.jackrabbit.oak.jcr.session.ItemImpl.perform(ItemImpl.java:112)
at
org.apache.jackrabbit.oak.jcr.session.NodeImpl.getNode(NodeImpl.java:552)
The same works fine in Jackrabbit 2.x
...
That actually looks like a bug in Jackrabbit, not Oak. See
<https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form>:
ExpandedName ::= '{' Namespace '}' LocalName
The empty string is not a valid Namespace, so this parses as qualified
name instead.
Best regards, Julian
Re: JCR 2.0 System View -> sv:name: expanded or qualified form?
On 10.02.2020 16:01, Konrad Windszus wrote: Hi, in the context of https://issues.apache.org/jira/browse/JCRVLT-407 I am currently looking into details how node names can be given in the System View format (https://docs.adobe.com/docs/en/spec/jcr/2.0/7_Export.html#7.2%20System%20View) Although not explicitly stated in the JSR, it seems that the values for the "sv:name" attribute should always be the qualified form (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.2%20Qualified%20Form) rather than the expanded form (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form). That would also enforce every node namespace prefix to be registered in the XML (would be in line with 7.2.1 from the JSR). On the other hand for the qualified form it wouldn't make any sense to be forced to declare the namespace (with an unused prefix) in the SysView XML as well. Can someone shed some light on this? Thanks, Konrad Well, the requirement to declare all namespaces upfront is kind of unrealistic. It implies that between the time when serialization starts and complete node traversal no new namespace prefixes are added. The spec seems to be vague and just says "JCR name"; I believe that includes expanded names as well. We may need more tests in Oak. Best regards, Julian
JCR 2.0 System View -> sv:name: expanded or qualified form?
Hi, in the context of https://issues.apache.org/jira/browse/JCRVLT-407 I am currently looking into details how node names can be given in the System View format (https://docs.adobe.com/docs/en/spec/jcr/2.0/7_Export.html#7.2%20System%20View) Although not explicitly stated in the JSR, it seems that the values for the "sv:name" attribute should always be the qualified form (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.2%20Qualified%20Form) rather than the expanded form (https://docs.adobe.com/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.5.1%20Expanded%20Form). That would also enforce every node namespace prefix to be registered in the XML (would be in line with 7.2.1 from the JSR). On the other hand for the qualified form it wouldn't make any sense to be forced to declare the namespace (with an unused prefix) in the SysView XML as well. Can someone shed some light on this? Thanks, Konrad
[jira] [Comment Edited] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750279#comment-16750279 ] Julian Reschke edited comment on JCR-4409 at 5/9/19 12:52 PM: -- trunk: (2.19.1) [r1851953|http://svn.apache.org/r1851953] 2.18: (2.18.1) [r1853200|http://svn.apache.org/r1853200] 2.16: (2.16.4) [r1857700|http://svn.apache.org/r1857700] 2.14: [r1859000|http://svn.apache.org/r1859000] was (Author: reschke): trunk: (2.19.1) [r1851953|http://svn.apache.org/r1851953] 2.18: (2.18.1) [r1853200|http://svn.apache.org/r1853200] 2.16: [r1857700|http://svn.apache.org/r1857700] > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.16.4, 2.14.7, 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Labels: (was: candidate_jcr_2_14) > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.16.4, 2.14.7, 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Fix Version/s: 2.14.7 > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.16.4, 2.14.7, 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16) > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.16.4, 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750279#comment-16750279 ] Julian Reschke edited comment on JCR-4409 at 4/17/19 5:16 PM: -- trunk: (2.19.1) [r1851953|http://svn.apache.org/r1851953] 2.18: (2.18.1) [r1853200|http://svn.apache.org/r1853200] 2.16: [r1857700|http://svn.apache.org/r1857700] was (Author: reschke): trunk: [r1851953|http://svn.apache.org/r1851953] 2.18: [r1853200|http://svn.apache.org/r1853200] > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_14 > Fix For: 2.16.4, 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Fix Version/s: 2.16.4 > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.16.4, 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Labels: candidate_jcr_2_16 (was: candidate_jcr_2_18) > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Fix Version/s: 2.18.1 > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_18 > Fix For: 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750279#comment-16750279 ] Julian Reschke edited comment on JCR-4409 at 2/8/19 9:12 AM: - trunk: [r1851953|http://svn.apache.org/r1851953] 2.18: [r1853200|http://svn.apache.org/r1853200] was (Author: reschke): trunk: [r1851953|http://svn.apache.org/r1851953] > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_16 > Fix For: 2.20, 2.18.1, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-4409. --- > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_18 > Fix For: 2.20, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Summary: jackrabbit-webapp: embed JCR 2.0 API (was: jackkrabbit-webapp: embed JCR 2.0 API) > jackrabbit-webapp: embed JCR 2.0 API > > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_18 > Fix For: 2.20, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JCR-4409) jackkrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4409: Labels: candidate_jcr_2_18 (was: ) > jackkrabbit-webapp: embed JCR 2.0 API > - > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_18 > Fix For: 2.20, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JCR-4409) jackkrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16750279#comment-16750279 ] Julian Reschke commented on JCR-4409: - trunk: [r1851953|http://svn.apache.org/r1851953] > jackkrabbit-webapp: embed JCR 2.0 API > - > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Labels: candidate_jcr_2_18 > Fix For: 2.20, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (JCR-4409) jackkrabbit-webapp: embed JCR 2.0 API
[ https://issues.apache.org/jira/browse/JCR-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-4409. - Resolution: Fixed Fix Version/s: 2.19.1 > jackkrabbit-webapp: embed JCR 2.0 API > - > > Key: JCR-4409 > URL: https://issues.apache.org/jira/browse/JCR-4409 > Project: Jackrabbit Content Repository > Issue Type: Task > Components: jackrabbit-webapp >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Minor > Fix For: 2.20, 2.19.1 > > > Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not > embed the JCR 2.0 API jar. That might have been the right thing to do in > 2008, but as of today it just complicates deployment. We also embed in the > Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JCR-4409) jackkrabbit-webapp: embed JCR 2.0 API
Julian Reschke created JCR-4409: --- Summary: jackkrabbit-webapp: embed JCR 2.0 API Key: JCR-4409 URL: https://issues.apache.org/jira/browse/JCR-4409 Project: Jackrabbit Content Repository Issue Type: Task Components: jackrabbit-webapp Reporter: Julian Reschke Assignee: Julian Reschke Fix For: 2.20 Due to https://issues.apache.org/jira/browse/JCR-957 we currently do not embed the JCR 2.0 API jar. That might have been the right thing to do in 2008, but as of today it just complicates deployment. We also embed in the Oak webapp example. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030691#comment-16030691 ] Julian Reschke edited comment on JCR-3901 at 12/31/17 7:10 AM: --- trunk: [r1796980|http://svn.apache.org/r1796980] 2.16: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] 2.10: [r1811708|http://svn.apache.org/r1811708] 2.8: [r1818148|http://svn.apache.org/r1818148] 2.6: [r1819718|http://svn.apache.org/r1819718] was (Author: reschke): trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] 2.10: [r1811708|http://svn.apache.org/r1811708] 2.8: [r1818148|http://svn.apache.org/r1818148] > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Labels: (was: candidate_jcr_2_6) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.6.10 > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.6.10, 2.8.7 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030691#comment-16030691 ] Julian Reschke edited comment on JCR-3901 at 12/14/17 3:39 PM: --- trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] 2.10: [r1811708|http://svn.apache.org/r1811708] 2.8: [r1818148|http://svn.apache.org/r1818148] was (Author: reschke): trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] 2.10: [r1811708|http://svn.apache.org/r1811708] > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_6 > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.8.7 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Labels: candidate_jcr_2_6 (was: candidate_jcr_2_8) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_6 > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.8.7 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.8.7 > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_6 > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3, 2.8.7 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Labels: candidate_jcr_2_8 (was: candidate_jcr_2_10 candidate_jcr_2_8) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_8 > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030691#comment-16030691 ] Julian Reschke edited comment on JCR-3901 at 10/10/17 2:35 PM: --- trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] 2.10: [r1811708|http://svn.apache.org/r1811708] was (Author: reschke): trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_8 > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.10.7 > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_8 > Fix For: 2.16, 2.12.8, 2.15.3, 2.10.7, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030691#comment-16030691 ] Julian Reschke edited comment on JCR-3901 at 9/28/17 7:43 AM: -- trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] 2.12: [r1809958|http://svn.apache.org/r1809958] was (Author: reschke): trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_8 > Fix For: 2.16, 2.12.8, 2.15.3, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Labels: candidate_jcr_2_10 candidate_jcr_2_8 (was: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_8) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_8 > Fix For: 2.16, 2.12.8, 2.15.3, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.12.8 > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_8 > Fix For: 2.16, 2.12.8, 2.15.3, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030691#comment-16030691 ] Julian Reschke edited comment on JCR-3901 at 9/4/17 5:42 PM: - trunk: [r1796980|http://svn.apache.org/r1796980] 2.14: [r1807264|http://svn.apache.org/r1807264] was (Author: reschke): trunk: [r1796980|http://svn.apache.org/r1796980] > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.14.3 > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_8 (was: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 candidate_jcr_2_8) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3, 2.14.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-3901. --- > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, > candidate_jcr_2_14, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-3901. - Resolution: Fixed > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, > candidate_jcr_2_14, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030691#comment-16030691 ] Julian Reschke commented on JCR-3901: - trunk: [r1796980|http://svn.apache.org/r1796980] > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, > candidate_jcr_2_14, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.15.3 > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, > candidate_jcr_2_14, candidate_jcr_2_8 > Fix For: 2.16, 2.15.3 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 candidate_jcr_2_8 (was: ) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Labels: candidate_jcr_2_10, candidate_jcr_2_12, > candidate_jcr_2_14, candidate_jcr_2_8 > Fix For: 2.16 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Summary: TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers (was: TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers) > TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token > transfers > - > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.16 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: 2.16 > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers > --- > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.16 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3901: Fix Version/s: (was: 2.12.2) (was: 2.13.0) (was: 2.10.3) (was: 2.8.2) > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers > --- > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3901: -- Fix Version/s: (was: 2.10.2) 2.10.3 > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers > --- > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.8.2, 2.10.3, 2.13.0, 2.12.2 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3901: -- Fix Version/s: (was: 2.12.1) 2.12.2 > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers > --- > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.10.2, 2.8.2, 2.13.0, 2.12.2 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3901: -- Fix Version/s: (was: 2.11.4) 2.12.0 2.13.0 > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers > --- > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.10.2, 2.8.2, 2.13.0, 2.12.0 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3901: -- Fix Version/s: (was: 2.12.0) 2.12.1 > TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers > --- > > Key: JCR-3901 > URL: https://issues.apache.org/jira/browse/JCR-3901 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: test >Affects Versions: 2.10.1, 2.8.1, 2.11.0 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 2.10.2, 2.8.2, 2.13.0, 2.12.1 > > > testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's > always illegal to add lock tokens to multiple sessions, however > <http://www.day.com/specs/jcr/2.0/17_Locking.html#17.3%20Lock%20Owner> allows > simultaneous lock ownership for open scoped locks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
