[
https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868113#action_12868113
]
Marcel Reutegger commented on JCR-2625:
---
I was wondering if it makes sense to build the
hi,
the module had a snapshot dependency to jackrabbit-core. I fixed that
and the build should now work. please note that you have to manually
deploy the hbase and hadoop-core dependencies and don't forget to
patch hbase! see also the readme file [0].
see attached repository.xml and
hi,
these are probably the read-only tests that require content.
please have a look at the class TestContentLoader in jackrabbit-core.
it adds test data to a jackrabbit repository to run the jcr tests.
preparing your repository with similar data should do the trick.
regards
marcel
On Thu, May
[
https://issues.apache.org/jira/browse/JCR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868123#action_12868123
]
Thomas Mueller commented on JCR-2396:
-
Was this patch applied to the 2.x line?
No, the
[
https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868126#action_12868126
]
Stefan Guggisberg commented on JCR-2625:
I was wondering if it makes sense to build
Hi,
As a part of my work on JCR-890, I'm planning to move most of the
session-related classes from o.a.j.core to a new o.a.j.core.session
package. This will make it easier to review and control related
dependencies and code paths, and to ultimately guard them against
access from concurrent
Hi,
I'm not sure if this will help more than it will complicate things.
Disadvantages:
- Isn't almost every class at in o.a.j.core at least somewhat session related?
- If you move classes to other packages, you will have to make many
method public.
Instead of moving session related classes to
Hi,
On Mon, May 17, 2010 at 11:00 AM, Thomas Müller thomas.muel...@day.com wrote:
- If you move classes to other packages, you will have to make many
method public.
My ultimate goal is to track down all these cases and refactor them
away so we can better control all the code paths to and from
Stefan Guggisberg wrote:
i share tomas's concerns.
so do i... in addition i have quite some changes
pending (JCR-2573, JCR-2629), which are not yet ready for commit.
UserPerWorkspaceSecurityManager
(security), DefaultSecurityManager (security),
that doesn't work without major changes.
Hi,
These unrelated classes are mostly things like RepositoryImpl,
TransientRepository, RepositoryCopier, etc. to which many external
codebases are linking, so we can't move them.
SessionImpl is used in my applications as well.
RepositoryImpl,
TransientRepository
I don't think those
On Mon, May 17, 2010 at 10:16 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
These unrelated classes are mostly things like RepositoryImpl,
TransientRepository, RepositoryCopier, etc. to which many external
codebases are linking, so we can't move them.
All class inside core has possible
Hi,
On Mon, May 17, 2010 at 11:34 AM, Thomas Müller thomas.muel...@day.com wrote:
These unrelated classes are mostly things like RepositoryImpl,
TransientRepository, RepositoryCopier, etc. to which many external
codebases are linking, so we can't move them.
SessionImpl is used in my
Hi,
As far as I understand, you want to move the classes so we can add
checkstyle / PMD constraints, and more easily ensure every method call
from an external class is synchronized. I think that's fine.
Having the 'proxy' classes sounds like a solution for the backward
compatibility concerns
Hi,
On Fri, May 14, 2010 at 9:12 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Fri, May 14, 2010 at 7:17 PM, Apache Hudson Server
hud...@hudson.zones.apache.org wrote:
Failure executing javac, but could not parse the error:
An exception has occurred in the compiler (1.5.0_14). Please
[
https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868210#action_12868210
]
Michael Dürig commented on JCR-2625:
Looks good to me. Do the davex integration tests
Hi,
On Mon, May 17, 2010 at 10:43 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Unless there's a need to wait, I'm planning to commit the changes in
the afternoon today.
This obviously needs more time than I anticipated. I'm sorry about the rush.
I'll prepare a patch and outline the steps
[
https://issues.apache.org/jira/browse/JCR-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2629.
-
Resolution: Fixed
LoginModuleConfig should allow to specify principalProvider-name in addition
to the class
See
http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1143/changes
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/1143/changes
[
https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868224#action_12868224
]
Stefan Guggisberg commented on JCR-2625:
Looks good to me. Do the davex integration
[
https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg updated JCR-2625:
---
Status: Resolved (was: Patch Available)
Fix Version/s: 2.2.0
Resolution:
[
https://issues.apache.org/jira/browse/JCR-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-890:
--
Attachment: session-class-move-norename.patch
As a first step to implementing this, I'd like to make the
[
https://issues.apache.org/jira/browse/JCR-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-890:
--
Attachment: session-class-move.patch
concurrent read-only access to a session
Hi,
On Mon, May 17, 2010 at 3:05 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
I'll prepare a patch and outline the steps by which I plan to address
the issues raised here. I'll commit the changes only when everyone is
happy with the approach.
See JCR-890 for the proposed patch and a more
[
https://issues.apache.org/jira/browse/JCR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reassigned JCR-2630:
---
Assignee: angela
UserAccessControlProvider handles users who dont have Jackrabbit managed
Principals or
[
https://issues.apache.org/jira/browse/JCR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2630:
Fix Version/s: 2.2.0
UserAccessControlProvider handles users who dont have Jackrabbit managed
Principals or User
Concurrent Session.move() operations failure
Key: JCR-2632
URL: https://issues.apache.org/jira/browse/JCR-2632
Project: Jackrabbit Content Repository
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/JCR-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg updated JCR-2632:
---
Attachment: ConcurrentMoveTest.java
test case for reproducing the issue
Concurrent
[
https://issues.apache.org/jira/browse/JCR-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-2631.
Fix Version/s: 2.2.0
Resolution: Fixed
The tests are now a part of jackrabbit-core.
Move
See
http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/org.apache.jackrabbit$jackrabbit-core/1145/changes
Changes:
[Jukka Zitting] JCR-2631: Move backwards compatibility tests to trunk
Set svn:ignore. Work in progress.
[Jukka Zitting] JCR-2631: Move backwards compatibility tests to
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk/1145/changes
Changes:
[Jukka Zitting] JCR-2631: Move backwards compatibility tests to trunk
Set svn:ignore. Work in progress.
[Jukka Zitting] JCR-2631: Move backwards compatibility tests to trunk
Streamline the old repository
hi,
I just stumbled over the method
AbstractBundlePersistenceManager.load(PropertyId), which I think might
be related to this issue.
what if the items states in the SISM indeed get cleared because the
local item states go into the change log? I guess this is more likely
the bigger the change set
Hi ,
I had an experience of pass of some tests in a package that i have not
implemented .May be those are tests which have tests dependent on other
packages that i have already implemented and tested successfully.
So I just wanna know that ,if my JCR TCK passes a test ,that means I am done
with
Hi,
On Mon, May 17, 2010 at 7:51 PM, Apache Hudson Server
hud...@hudson.zones.apache.org wrote:
[INFO] Too many unapproved licenses: 1
I fixed this in a subsequent commit.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868516#action_12868516
]
Jervis Liu commented on JCR-2400:
-
Hi, I tried JackRabbit 2.1, still same exception.
On Mon, May 17, 2010 at 9:46 PM, Marcel Reutegger mreut...@day.com wrote:
I just stumbled over the method
AbstractBundlePersistenceManager.load(PropertyId), which I think might
be related to this issue.
what if the items states in the SISM indeed get cleared because the
local item states go
36 matches
Mail list logo
