On 10/04/2020 15.50, Julian Reschke wrote:
On 10.04.2020 14:31, Ate Douma wrote:
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion
On 10/04/2020 15.50, Julian Reschke wrote:
On 10.04.2020 14:31, Ate Douma wrote:
Hmm, I now see there was some (very minimal) 'discussion' about this,
which I missed.
It might have been more helpful and effective (to trigger me) with a
more descriptive subject for that discussion
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated JCR-4552:
---
Comment: was deleted
(was: How/why should 2.18 already go EOL?
That doesn't make sense, v2.16 is indicated
) that
first a more up-to-date 2.20 is released.
And give downstream users (not on oak or from adobe) an appropriate
heads-up and time to catchup :-)
Thanks,
Ate
On 10/04/2020 14.04, Ate Douma wrote:
Huh?
How/why should 2.18 already go EOL?
That doesn't make sense.
Aren't you mistaking
) that
first a more up-to-date 2.20 is released.
And give downstream users (not on oak or from adobe) an appropriate
heads-up and time to catchup :-)
Thanks,
Ate
On 10/04/2020 14.04, Ate Douma wrote:
Huh?
How/why should 2.18 already go EOL?
That doesn't make sense.
Aren't you mistaking
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080445#comment-17080445
]
Ate Douma edited comment on JCR-4552 at 4/10/20, 12:07 PM:
---
How/why should 2.18
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080445#comment-17080445
]
Ate Douma commented on JCR-4552:
How/why should 2.18 already go EOL?
That doesn't make sense.
Aren't
Huh?
How/why should 2.18 already go EOL?
That doesn't make sense.
Aren't you mistaking this with 2.10?
Thanks,
Ate
On 09/04/2020 14.04, Julian Reschke (Jira) wrote:
[
https://issues.apache.org/jira/browse/JCR-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881240#comment-16881240
]
Ate Douma commented on JCR-4455:
Great, thanks [~c_koell]!
> condition index-rule handling more bro
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881062#comment-16881062
]
Ate Douma commented on JCR-4455:
[~c_koell] Thanks for committing the patch!
But note that, while I don't
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879942#comment-16879942
]
Ate Douma commented on JCR-4455:
Hi [~c_koell],
Yes, this now works for my use-case and with my
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874514#comment-16874514
]
Ate Douma commented on JCR-4455:
As we want to proceed with the upgrade to 2.18.2 anyhow, for the time
[
https://issues.apache.org/jira/browse/JCR-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated JCR-4455:
---
Attachment: exposing-JCR-4455.patch
> condition index-rule handling more broken after JCR-4
Ate Douma created JCR-4455:
--
Summary: condition index-rule handling more broken after JCR-4339
Key: JCR-4455
URL: https://issues.apache.org/jira/browse/JCR-4455
Project: Jackrabbit Content Repository
FYI
Forwarded Message
Subject: [jira] [Created] (INFRA-12827) Git mirror not in sync with jackrabbit
svn
Date: Tue, 25 Oct 2016 19:15:59 + (UTC)
From: Ate Douma (JIRA) <j...@apache.org>
Reply-To: us...@infra.apache.org
To: iss...@infra.apache.org
Ate Douma created
While looking through the changes for this version, I noticed recent commit
r1694984 [1] was incorrectly marked/commented with issue OAK-2231, not a
Jackrabbit JCR issue.
As result these changes are not tracked/reported in the RELEASE-NOTES.txt
either.
It might be good to at least still
[
https://issues.apache.org/jira/browse/JCRVLT-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14194820#comment-14194820
]
Ate Douma commented on JCRVLT-1:
[~tripod] Tobias, are you sure? I only see a few test
On 11/21/2013 07:18 PM, Jukka Zitting wrote:
Hi,
On Tue, Nov 19, 2013 at 9:47 AM, Ate Douma a...@douma.nu wrote:
On 11/11/2013 07:29 PM, Jukka Zitting wrote:
Of course section 12.6.2 contradicts that by essentially giving the
repository free reign to decide which (if any) events to include
On 11/11/2013 07:29 PM, Jukka Zitting wrote:
Hi,
On Mon, Nov 11, 2013 at 6:10 AM, Michael Dürig mdue...@apache.org wrote:
On 8.11.13 10:37 , Alexander Klimetschek wrote:
Regarding journaled observation: retrieving a journal with
ObservationManager#getEventJournal can allow access to events
I'm +1 (not-binding) on this release.
There are a few comments I'd like to give however:
- The RELEASE_NOTES.txt indicates JCR-3670 has already been resolved, but this
is not the case.
- There are two files for LICENSE and LICENSE.txt and for NOTICE and NOTICE.txt.
These files do not contain
-clearance-template.html
[2] http://markmail.org/message/a5ah3av2gkkytwfu
[3] http://markmail.org/message/nvyujol44wzjdimi
[4] http://markmail.org/message/xbtnxvvxf4jptnnv
[5] http://incubator.apache.org/ip-clearance/couchdb-bigcouch.html
regards, toby
On Wed, Jun 26, 2013 at 4:20 AM, Ate Douma
On 06/25/2013 12:46 PM, Felix Meschberger wrote:
Hi
Am 24.06.2013 um 23:40 schrieb Tobias Bocanegra:
I was wondering what the status for this is?
being buried in day-to-day work the last months, I just now completed
the preparation for the contribution. I need one or 2 more days to
find the
On 05/03/2013 07:19 PM, Tobias Bocanegra wrote:
Hello,
as some of you might know, we at Adobe (and at Day Software before)
developed quite some tooling around exporting, importing and syncing
content from and to a JCR repository. The checked-out structure on
the local filesystem also offers
I didn't see yet any feedback on this [1].
Its not like a very critical bug (probably) but still serious enough IMO to
consider fixing.
Anyone interested to at least take a look at it?
Regards, Ate
[1] https://issues.apache.org/jira/browse/JCR-3581
Great! Definitely interesting and useful features.
If the contribution turns out to be generically feasible and applicable enough I
expect we (Hippo) also will be interested to participate and help with further
enhancements and improvements. We will most certainly give it a proper review :)
Ate Douma created JCR-3581:
--
Summary: Incorrect bitwise arithmetic in
BitsetENTCacheImpl.BitsetKey.compareTo implementation - wrong bit mask value
used
Key: JCR-3581
URL: https://issues.apache.org/jira/browse/JCR
[
https://issues.apache.org/jira/browse/JCR-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated JCR-3581:
---
Attachment: JCR-3581.patch
The JCR-3581.patch was created against current trunk but should be applicable
On 10/01/2012 03:10 PM, Michael Dürig wrote:
On 1.10.12 12:36, Alexander Klimetschek wrote:
On 01.10.2012, at 12:26, Jukka Zitting jukka.zitt...@gmail.com wrote:
1) The Oak codebase will become Jackrabbit 3.0 sometime next year
2) We spin off the Oak effort to a new Apache project
I
for the tip, I'll have someone book there for us as well.
And if someone likes to meet for a drink Monday evening (late, probably after
21.30), we should be close by :)
See you next week,
Ate
Michael
On 18.9.12 10:08, Ate Douma wrote:
Hi everyone,
As a follow up, I can now confirm that Unico
%20Hackathon%20September%202012
On 08/22/2012 05:28 PM, Ate Douma wrote:
Thanks!
Ate
On 08/22/2012 05:17 PM, Michael Dürig wrote:
Hi,
This is great news! We are definitely looking forward to meeting all of you
there. Keep an eye on the Oakathon Wiki page as we will announce further details
and Bart Wiki
admins.
Michael
[1] [1] http://wiki.apache.org/jackrabbit/Oak%20Hackathon%20September%202012
On 22.8.12 16:33, Ate Douma wrote:
Hi OAK hackers,
As Hippo developers we are very interested to participate on the
proposed OAK Hackathon on September 25th in Berlin [1].
Although we
Congratulations Unico!
Regards, Ate
On 05/23/2012 04:26 PM, Michael Dürig wrote:
Hi,
Please welcome Unico Hommes as a new committer and PMC member of
the Apache Jackrabbit project. The Jackrabbit PMC recently decided to
offer Unico committership based on his contributions. I'm happy to
On 03/07/2012 09:25 AM, Jukka Zitting wrote:
Hi,
On Tue, Mar 6, 2012 at 1:00 PM, Jukka Zittingjukka.zitt...@gmail.com wrote:
The oak-dev@ mailing list should follow up shortly, see INFRA-4514 [1].
The list is ready now, you can subscribe by sending a message to
On 03/07/2012 10:55 PM, Jukka Zitting wrote:
Hi,
On Wed, Mar 7, 2012 at 10:47 PM, Ate Doumaa...@douma.nu wrote:
Right now discussions and replies on oak specific issues and commit messages
still end up on the main dev@ so IMO not serving the intent.
Correct. I switched the OAK notifications
Could someone add .project to the svn:ignore property for the JackRabbit root
project to support checking out with Eclipse?
Regards,
Ate
Felix Meschberger wrote:
Hi Ate,
Sounds reasonable :-)
Hehe :)
I have done it.
Thanks Felix!
Regards
Felix
On 5/11/07, Ate Douma [EMAIL PROTECTED] wrote:
Could someone add .project to the svn:ignore property for the JackRabbit
root project to support checking out with Eclipse
[
https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489403
]
Ate Douma commented on JCR-781:
---
Thanks for the quick response.
We can use the latest from the trunk again :)
Regards
[
https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489217
]
Ate Douma commented on JCR-781:
---
Jukka,
As result of this change the JCR-RMI server is no longer working for us.
We now
[
https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489242
]
Ate Douma commented on JCR-781:
---
To make a little more clear what seems to be the problem:
The new default behavior
[
https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489244
]
Ate Douma commented on JCR-781:
---
Damn, I described the differences incorrectly, it should be:
Implicit socket factories
[
https://issues.apache.org/jira/browse/JCR-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487621
]
Ate Douma commented on JCR-804:
---
Hi Marcel,
I just want to confirm Jukka's comment: that is what I encountered
[
https://issues.apache.org/jira/browse/JCR-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486667
]
Ate Douma commented on JCR-804:
---
Marcel,
Your solution breaks JDK 1.4 compatibility, jackrabbit-core now requires JDK
https://issues.apache.org/jira/browse/JCR-804
http://svn.apache.org/viewvc?view=revrevision=520841
introduced JDK 5.0 language features.
Error messages when trying to compile with JDK 1.4 (in Eclipse):
No enclosing instance of type RangeQuery is accessible. Must qualify the allocation with
43 matches
Mail list logo
