[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reopened JCR-3777:
-
reopening the clear method IMO has a bug: retrieving principal for a null
name will fail. apart from that: i
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009478#comment-14009478
]
angela commented on JCR-3777:
-
and then there is a bug in the javadoc: it states that the
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reassigned JCR-3777:
---
Assignee: angela (was: Alexander Klimetschek)
Add simple allow/deny/clear convenience methods to
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-3777.
-
Resolution: Fixed
rev. 1597717
Add simple allow/deny/clear convenience methods to AccessControlUtils
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3777:
Fix Version/s: 2.9
Add simple allow/deny/clear convenience methods to AccessControlUtils
Konrad Windszus created JCRVLT-49:
-
Summary: Support case-sensitivity on case-insensitive file systems
Key: JCRVLT-49
URL: https://issues.apache.org/jira/browse/JCRVLT-49
Project: Jackrabbit FileVault
[
https://issues.apache.org/jira/browse/JCRVLT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-49:
--
Issue Type: Improvement (was: Bug)
Support case-sensitivity on case-insensitive file systems
hi
while resolving an issue that didn't make it into 2.8, i realized
that the version of the trunk is now set to 3.0-SNAPSHOT.
while i don't care too much about the number itself, it looks a bit
confusing to me, because some time ago we used to call jr3 what is now
oak. from my understanding we
hi jukka
makes sense to me... if you don't mind i would opt for keeping
3.0 reserved for that unified *rabbit and set the current
version to 2.9-SNAPSHOT to avoid confusions and not putting
too much pressure on us to complete the merge.
kind regards
angela
On 27/05/14 15:19, Jukka Zitting
angela created JCR-3782:
---
Summary: Backport OAK-1612, OAK-1615, OAK-1616
Key: JCR-3782
URL: https://issues.apache.org/jira/browse/JCR-3782
Project: Jackrabbit Content Repository
Issue Type:
[
https://issues.apache.org/jira/browse/JCR-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009750#comment-14009750
]
angela commented on JCR-3782:
-
trunk: revision 1597799
2.8 branch: revision 1597800.
Backport
[
https://issues.apache.org/jira/browse/JCR-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-3782.
-
Resolution: Fixed
Backport OAK-1612, OAK-1615, OAK-1616
-
Hi,
On Tue, May 27, 2014 at 9:54 AM, Angela Schreiber anch...@adobe.com wrote:
makes sense to me... if you don't mind i would opt for keeping
3.0 reserved for that unified *rabbit and set the current
version to 2.9-SNAPSHOT to avoid confusions and not putting
too much pressure on us to
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009801#comment-14009801
]
angela commented on JCR-3777:
-
more javadoc fixes: rev. 1597806
Add simple allow/deny/clear
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14009810#comment-14009810
]
angela commented on JCR-3777:
-
merged into 2.8 branch: rev. 1597807
Add simple
[
https://issues.apache.org/jira/browse/JCR-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3777:
Fix Version/s: 2.8
Add simple allow/deny/clear convenience methods to AccessControlUtils
On 27.05.2014, at 06:54, Angela Schreiber anch...@adobe.com wrote:
makes sense to me... if you don't mind i would opt for keeping
3.0 reserved for that unified *rabbit and set the current
version to 2.9-SNAPSHOT to avoid confusions and not putting
too much pressure on us to complete the
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/150
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
The Buildbot has detected a new failure on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/151
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
On Mon, May 26, 2014 at 9:12 AM, Michael Dürig mdue...@apache.org wrote:
Apart from that - and this is probably a separate discussion - I also think
we should split oak-run up as it is getting too heavy.
Too heavy in which way? If you refer to the size of the jar, I fail to
see how it's
On 27.5.14 3:33 , Jukka Zitting wrote:
Hi,
On Mon, May 26, 2014 at 9:12 AM, Michael Dürig mdue...@apache.org wrote:
Apart from that - and this is probably a separate discussion - I also think
we should split oak-run up as it is getting too heavy.
Too heavy in which way?
Functionality
For me more than size the problem is usage of Lucene To use full power
of Oak we need to include Lucene 4.x and thus would need to drop JR2.
So probably have two modules
1. oak-run - server, benchmarking, console, debugging, scalability, backup
2. oak-migration - upgrade, jr2 specific
On 27.5.14 4:26 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 9:47 AM, Michael Dürig mdue...@apache.org wrote:
On 27.5.14 3:33 , Jukka Zitting wrote:
Too heavy in which way?
Functionality wise. It is growing into a chief cook and bottle washer. It
already does backup, benchmarking,
Hi,
On Tue, May 27, 2014 at 10:36 AM, Michael Dürig mdue...@apache.org wrote:
This is not about different jars but about setting it up as a OSGi container
into which the respective bundles could get deployed.
We can turn the jar in to an OSGi container, but why not ship
everything everything
On 27.5.14 4:48 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 10:36 AM, Michael Dürig mdue...@apache.org wrote:
We can turn the jar in to an OSGi container, but why not ship
everything everything we can by default?
Because
increase flexibility, test and showcase OSGi readiness of
Hi,
On Tue, May 27, 2014 at 10:53 AM, Michael Dürig mdue...@apache.org wrote:
Because
increase flexibility, test and showcase OSGi readiness of Oak,
resolve version conflicts (e.g. Lucene), let others easily plug in
their own stuff (e.g scripting language through JSR-223).
Fair enough, but
fwiw I would (for a change :) ) would like to avoid OSGi here and keep
things as they are for following reasons
1. JR2 is not OSGi friendly and we use some of the internal classes
for upgrade which would be problematic in OSGI
2. For debug and console we rely on some non exported packages. Using
On 27.5.14 5:13 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 10:53 AM, Michael Dürig mdue...@apache.org wrote:
Because
increase flexibility, test and showcase OSGi readiness of Oak,
resolve version conflicts (e.g. Lucene), let others easily plug in
their own stuff (e.g scripting
The Buildbot has detected a build exception on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/157
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
Hi,
On Tue, May 27, 2014 at 11:24 AM, Michael Dürig mdue...@apache.org wrote:
Users needn't be aware of the OSGi container inside if they just want to
quickly try something out. Running with e.g. the benchmark option would
still run the benchmark suite. The difference would be that in the
On 27.5.14 5:33 , Jukka Zitting wrote:
Hi,
On Tue, May 27, 2014 at 11:24 AM, Michael Dürig mdue...@apache.org wrote:
Users needn't be aware of the OSGi container inside if they just want to
quickly try something out. Running with e.g. the benchmark option would
still run the benchmark suite.
31 matches
Mail list logo
