[
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 unavaila
/commit/62017687a8efab6d37e53c72d95daae7851e0e8f]
> Javadoc build is broken due to JCR 2.0 API docs being unavailable
> -
>
> Key: JCR-5041
> URL: https://issues.apache.org/jira/
[
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 be
[
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 be
[
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 be
[
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 unavaila
[
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 be
/commit/62017687a8efab6d37e53c72d95daae7851e0e8f]
> Javadoc build is broken due to JCR 2.0 API docs being unavailable
> -
>
> Key: JCR-5041
> URL: https://issues.apache.org/jira/
[
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 be
ken 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
>
[
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
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
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
://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
[
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.
[
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
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
> -
>
> K
[
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
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 jav
[
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 ht
[
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
://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/
(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
(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
[
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
[
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
[
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
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.
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 java
[
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 s
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.
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.
[
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
=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
[
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
[
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
[
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
[
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
/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 be
[
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
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
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/
ally 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 expande
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
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
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
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
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
>> no
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 f
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 20
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
.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
>
krabbit.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
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
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
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
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
: (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
>
[
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
[
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
[
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
bed 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-weba
[
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
[
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
[
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
|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
>
[
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
>
>
>
[
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
[
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
bit-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
> Compo
[
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
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
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
>
[
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 functional
[
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 to
]
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
> tra
[
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
[
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 to
oes not allow new JCR 2.0 functionality for lock token
> transfers
> -
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Projec
]
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
>
[
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 to
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
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/ji
[
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 to
|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
> tra
[
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 to
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
>
[
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
> tra
[
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 to
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
>
[
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 to
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
>
[
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
[
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 transf
)
(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/
low new JCR 2.0 for lock token transfers
> ---
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>
low new JCR 2.0 for lock token transfers
> ---
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>
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
low new JCR 2.0 for lock token transfers
> ---
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>
1 - 100 of 271 matches
Mail list logo
