-lines. Does that help?
BR,
Jukka Zitting
Hi,
On Wed, Jan 23, 2013 at 1:35 PM, Michael Dürig wrote:
> [INFO] Step 1. Check release cheksum
> [ERROR] Release checksum does not match provided checksum!
Hmm, what do you have in
target/jackrabbit-staging-*/2.3.5/jackrabbit-2.5.3-src.zip.sha after
getting the above error?
BR,
ouldn't be backported to
the 2.6 branch.
BR,
Jukka Zitting
because...
My vote is +1.
PS. Note the new dist.apache.org location for the release candidate
and the updated check-release.sh script (remember to svn update before
running the above command).
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3455:
---
Component/s: jackrabbit-core
Fix Version/s: 2.5.3
Looks like this was fixed in revision 1405792
[
https://issues.apache.org/jira/browse/JCR-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3305:
---
Fix Version/s: 2.5.3
> spi2davex.RepositoryServiceImpl -> idUriCache raises until heap ov
[
https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559690#comment-13559690
]
Jukka Zitting commented on JCR-3402:
Nice! Looks good to me.
Marcel, Alex, others;
[
https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559671#comment-13559671
]
Jukka Zitting commented on JCR-3402:
The problem is the "+ invalid" part.
[
https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3440.
Resolution: Fixed
Re-resolving this as the patch already got applied.
Please see the backwards
[
https://issues.apache.org/jira/browse/JCR-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3489:
---
Fix Version/s: (was: 2.5.3)
Let's postpone this to see if some of the feedback could be addr
[
https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3402:
---
Fix Version/s: (was: 2.5.3)
I'm hesitant to apply the patch as is for the following two re
[
https://issues.apache.org/jira/browse/JCR-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3485:
---
Resolution: Fixed
Assignee: Jukka Zitting
Status: Resolved (was: Patch Available)
Patch
[
https://issues.apache.org/jira/browse/JCR-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3443:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Looks useful, thanks! Patch
[
https://issues.apache.org/jira/browse/JCR-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3443:
---
Assignee: Jukka Zitting
Issue Type: New Feature (was: Improvement)
> Normalize Str
[
https://issues.apache.org/jira/browse/JCR-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3435:
---
Resolution: Fixed
Fix Version/s: (was: 2.4.4)
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/JCR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3439:
---
Fix Version/s: (was: 2.6)
2.5.3
> PrincipalManagerImpl.CheckedGroup sho
[
https://issues.apache.org/jira/browse/JCR-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3435:
---
Fix Version/s: (was: 2.6)
2.5.3
> NPE on parsing XPath query with ch
[
https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3469:
---
Fix Version/s: (was: 2.6)
2.5.3
> Thread interrupt may result in clo
[
https://issues.apache.org/jira/browse/JCR-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3478:
---
Fix Version/s: (was: 2.6)
2.5.3
> Partial search terms matching fails w
[
https://issues.apache.org/jira/browse/JCR-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3476:
---
Fix Version/s: (was: 2.6)
2.5.3
> NodeIndexer attempts to extract bin
[
https://issues.apache.org/jira/browse/JCR-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3483:
---
Fix Version/s: (was: 2.6)
2.5.3
> Result set iterator causes infinite l
[
https://issues.apache.org/jira/browse/JCR-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3486:
---
Fix Version/s: (was: 2.6)
2.5.3
> Potential null pointer exception
Jukka Zitting created JCR-3494:
--
Summary: Make Jackrabbit performance benchmark easier to use from
Oak
Key: JCR-3494
URL: https://issues.apache.org/jira/browse/JCR-3494
Project: Jackrabbit Content
Hi,
On Thu, Jan 17, 2013 at 1:00 PM, Jukka Zitting wrote:
> On Tue, Oct 23, 2012 at 5:03 PM, Jukka Zitting
> wrote:
>> * Jackrabbit 2.6: We target at releasing a stable Jackrabbit 2.6.0
>> version sometime around the end of this year. As usual, we'll have a
>&g
Hi,
On Tue, Oct 23, 2012 at 5:03 PM, Jukka Zitting wrote:
> Here's an early draft of how this could work out in terms of the
> Jackrabbit roadmap:
Seems like we have fairly good consensus on the big picture, so let's
start laying some more concrete plans!
> * Jackrabbi
[
https://issues.apache.org/jira/browse/JCR-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552557#comment-13552557
]
Jukka Zitting commented on JCR-3491:
This might have broken the CI build, see
h
[
https://issues.apache.org/jira/browse/JCR-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537211#comment-13537211
]
Jukka Zitting commented on JCR-3489:
There's little downside to adding somet
Hi,
On Mon, Dec 17, 2012 at 12:09 PM, Jukka Zitting wrote:
> As documented in [1], we should migrate our release publishing
> mechanism from people.apache.org to the new svnpubsub-based
> dist.apache.org mechanism [2]. Since we currently have no releases
> being prepared or voted o
d=12895234&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12895234
BR,
Jukka Zitting
Hi,
On Mon, Dec 10, 2012 at 12:43 PM, Alexander Klimetschek
wrote:
> is anything planned for this already? Or did we already move, and
> jackrabbit.apache.org is incorrectly listed below?
It's still on the TODO, see latest board report.
BR,
Jukka Zitting
it it beginning of next week.
Looks good to me.
It's quite a while since our last releases. I think we should target
at cutting 2.5.3 and Oak 0.6 sometime around the end of the year. It
would probably be a good idea to also create the Jackrabbit 2.6 branch
around that time, and go for 2
bling the auto-versioning CommitHook.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508601#comment-13508601
]
Jukka Zitting commented on JCR-3474:
I replaced the isJackrabbitImpl flag wit
below for the full InterruptedQueryTest failure. The test case was
added in revision 1415093 for JCR-3469, and has failed in all Jenkins
builds since then.
BR,
Jukka Zitting
junit.framework.AssertionFailedError: javax.jcr.RepositoryException:
java.io.IOException: null:
SimpleFSIndexInput(
[
https://issues.apache.org/jira/browse/JCR-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3474.
Resolution: Fixed
Fix Version/s: 2.5.3
Done in revision 1415968.
>
Jukka Zitting created JCR-3474:
--
Summary: Add JackrabbitQueryResult.getTotalSize()
Key: JCR-3474
URL: https://issues.apache.org/jira/browse/JCR-3474
Project: Jackrabbit Content Repository
Issue
[
https://issues.apache.org/jira/browse/JCR-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3474:
---
Issue Type: Improvement (was: Bug)
> Add JackrabbitQueryResult.getTotalS
lly mess
up with transitive dependencies of downstream projects. A downstream
project that embeds Jackrabbit but still wants the Tika update can
still do so locally by explicitly upgrading the version of the Tika
dependency.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505811#comment-13505811
]
Jukka Zitting commented on JCR-3465:
The current implementation works jus
or the Apache CMS as support for the current
Confluence export + svn checkout mechanism is going to be discontinued
at the end of the year. The good part about migrating is that site
changes will then be reflected on the public web site in just a few
seconds instead of the hours of delay we now have.
BR,
Jukka Zitting
ature.
I intentionally set the update limit high enough so that the
functionality is only triggered in custom test cases and in normal use
the much lower purge limit in RootImpl takes care of branch handling.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492467#comment-13492467
]
Jukka Zitting commented on JCR-3440:
For 2.4 and 2.2 it would be nice to fi
[
https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492431#comment-13492431
]
Jukka Zitting commented on JCR-3440:
IMO it's better to update downstream
[
https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491266#comment-13491266
]
Jukka Zitting commented on JCR-3258:
We need autocommit since Jackrabbit is using
[
https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3258.
Resolution: Not A Problem
Jackrabbit is designed to work directly as an XA resource, which means
Hi,
On Tue, Oct 23, 2012 at 4:52 PM, Jukka Zitting wrote:
> Done. The next build seems to have passed.
Oh, I was looking at the console output from a wrong build. Looks like
there's something more wrong with Jenkins that's causing these builds
to fail.
BR,
Jukka Zitting
Hi,
On Tue, Oct 23, 2012 at 4:31 PM, Bart van der Schans
wrote:
> Looks like a Jenkins related failure. Can somebody restart the build?
Done. The next build seems to have passed.
BR,
Jukka Zitting
lients, and new features for future Jackrabbit
3.x releases. And since Jackrabbit 3.0 will be based on a fresh new
underlying architecture from Oak, it's likely that we'll encounter a
number of smaller issues to be fixed or improved.
WDYT?
[1] http://markmail.org/message/ga4mn2x2xqsvzwg6
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3447:
---
Fix Version/s: 2.2.14
Makes sense. Merged also to the 2.2 branch in revision 1399667
[
https://issues.apache.org/jira/browse/JCR-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3447:
---
Fix Version/s: 2.4.4
Merged to the 2.4 branch in revision 1399587
[
https://issues.apache.org/jira/browse/JCR-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3447.
Resolution: Fixed
Fix Version/s: 2.5.3
Fixed in revision 1399576
Jukka Zitting created JCR-3447:
--
Summary: InternalValueFactory should use the DataStore whenever
available
Key: JCR-3447
URL: https://issues.apache.org/jira/browse/JCR-3447
Project: Jackrabbit Content
sues.
BR,
Jukka Zitting
open already closed (i.e. released) issues, but
you can add edit the issue (add new fix version, etc.) and add
comments.
BR,
Jukka Zitting
the issue
to add the 2.2.13 fix version in addition to the existing fix
versions. For completeness I often also add a comment like "Backported
to the x.y branch in revision n" when adding the new fix version.
BR,
Jukka Zitting
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.5.2. The release is available for download at:
http://jackrabbit.apache.org/downloads.html
See the full release notes below for details about this release.
Release Notes -- Apache Jackrabbit -- Version
Hi,
On Tue, Sep 18, 2012 at 6:08 PM, Jukka Zitting wrote:
> Please vote on releasing this package as Apache Jackrabbit 2.5.2.
The vote passes as follows:
+1 Alex Parvulescu
+1 Bart van der Schans
+1 Claus Köll
+1 Jukka Zitting
+1 Julian Reschke
+1 Marcel Reuteg
for Oak
and the re-activated OCM. That would also be useful for Oak where Alex
P. has already been working on generalizing some of the query tests we
have in jackrabbit-core.
BR,
Jukka Zitting
y work :-) that certainly won't scale to larger indexes. We'll
need to extend the binary value mechanism a bit to match features
(mostly random access) that Lucene needs.
BR,
Jukka Zitting
some Jenkins/Nexus connection issue. Let's wait for the next build.
BR,
Jukka Zitting
because...
My vote is +1.
BR,
Jukka Zitting
when it knows the main path constraint used in the
query, it can walk down that path to detect which indexes are
available and useful for resolving the query.
At commit time, it can walk down the affected subtrees to detect which
indexes need to be updated.
BR,
Jukka Zitting
e, please share your critiques, improvements and/or alternatives.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3401:
---
Fix Version/s: (was: 2.6)
2.5.2
> Wrong results when querying wit
[
https://issues.apache.org/jira/browse/JCR-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3428:
---
Fix Version/s: (was: 2.6)
2.5.2
> Partial search terms are no lon
inModule implementation should be able to encapsulate all the
proposed extra logic.
BR,
Jukka Zitting
ou missed Michael's earlier reply to you:
http://markmail.org/message/jon6kpi3vwgwxrbb
BR,
Jukka Zitting
g in
particular that's blocking you from upgrading? The upgrade should be
fairly straightforward.
That said, if you're willing to do the work of backporting all fixes
and submitting the changes as patches, then obviously we'd be happy to
commit the changes and cut a release.
BR,
Jukka Zitting
you could cut the
> release ...
I'm available for most of today and tomorrow on Skype, so you ping me
anytime if you want to take a shot at cutting 2.4.3. Otherwise I'll
take care of cutting the release now and we can do a bigger release
walkthrough at adaptTo().
BR,
Jukka Zitting
Hi,
On Thu, Aug 30, 2012 at 11:48 AM, Bart van der Schans
wrote:
> If you are going to do a walk through on skype I might want to join
> also.
That would be great, welcome!
BR,
Jukka Zitting
If you have time later today and are available on Skype (I'm
jukka_zitting) or Google talk, I can also walk you through the steps
and help with the details.
The more people we have who are familiar with the release process, the
better! :-)
BR,
Jukka Zitting
Hi,
On Wed, Aug 29, 2012 at 3:46 PM, KÖLL Claus wrote:
> Once again .. can we start with the 2.4.3 release ...
Yes!
> Alex or Jukka do you have time to prepare the release ?
I can look into it tomorrow. Or, Claus, if you like I could walk you
through the steps to cut a release.
BR,
[
https://issues.apache.org/jira/browse/JCR-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3418.
Resolution: Fixed
Fix Version/s: 2.5.2
Fixed in revision 1377690
Jukka Zitting created JCR-3418:
--
Summary: CompactNodeTypeDefReader throws away exception information
Key: JCR-3418
URL: https://issues.apache.org/jira/browse/JCR-3418
Project: Jackrabbit Content
Hi,
On Fri, Aug 3, 2012 at 12:40 PM, Alex Parvulescu
wrote:
> Please vote on releasing this package as Apache Jackrabbit 2.5.1.
[x] +1 Release this package as Apache Jackrabbit 2.5.1
BR,
Jukka Zitting
ime we'll encounter cases where existing clients
that assume only standard JCR functionality fail on Oak because of
some problems in our code. Capturing such cases as TCK tests would be
quite useful.
[1] http://jcp.org/en/procedures/jcp2#5
[2]
http://www.day.com/content/day/en/products/jcr/jsr-283/_jcr_content/par/download_1/file.res/jsr-283-tck-appeal.pdf
BR,
Jukka Zitting
/jira/browse/JCR-3383
> https://issues.apache.org/jira/browse/JCR-3379
> https://issues.apache.org/jira/browse/JCR-3354
> https://issues.apache.org/jira/browse/JCR-3377
> https://issues.apache.org/jira/browse/JCR-3318
> https://issues.apache.org/jira/browse/JCR-3349
I backported all of these to 2.4.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427961#comment-13427961
]
Jukka Zitting commented on JCR-3349:
Merged to the 2.4 branch in revision 136
[
https://issues.apache.org/jira/browse/JCR-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427959#comment-13427959
]
Jukka Zitting commented on JCR-3354:
Merged to the 2.4 branch in revision 136
[
https://issues.apache.org/jira/browse/OAK-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427954#comment-13427954
]
Jukka Zitting commented on OAK-224:
---
+1 Looks like a good step forward.
FWIW I d
[
https://issues.apache.org/jira/browse/JCR-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427942#comment-13427942
]
Jukka Zitting commented on JCR-3318:
Merged to the 2.4 branch in revision 136
[
https://issues.apache.org/jira/browse/JCR-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427943#comment-13427943
]
Jukka Zitting commented on JCR-3377:
Merged to the 2.4 branch in revision 136
[
https://issues.apache.org/jira/browse/JCR-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427939#comment-13427939
]
Jukka Zitting commented on JCR-3379:
Merged to the 2.4 branch in revision 136
[
https://issues.apache.org/jira/browse/JCR-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427934#comment-13427934
]
Jukka Zitting commented on JCR-3383:
Merged to the 2.4 branch in revision 136
[
https://issues.apache.org/jira/browse/JCR-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3378:
---
Fix Version/s: (was: 2.4.3)
I'm getting some merge conflicts here too with 2.4. Removing the
[
https://issues.apache.org/jira/browse/JCR-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3387:
---
Fix Version/s: (was: 2.4.3)
2.5.1
I tried merging this to the 2.4 branch but
[
https://issues.apache.org/jira/browse/JCR-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3399:
---
Fix Version/s: 2.5.1
Merged to the 2.4 branch in revision 1368836.
> Shared ISM d
to split
it back off the main Jackrabbit trunk to a separate component with its
own release cycle. That would make it easier to cut releases of the
code whenever needed.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3265:
---
Fix Version/s: (was: 2.6)
2.5.1
> Consistency checker should double ch
[
https://issues.apache.org/jira/browse/JCR-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3267:
---
Fix Version/s: (was: 2.6)
2.5.1
> Consistency checker needs to run multi
[
https://issues.apache.org/jira/browse/JCR-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3334:
---
Affects Version/s: (was: 2.6)
2.5
Fix Version/s: (was: 2.6
[
https://issues.apache.org/jira/browse/JCR-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3269:
---
Fix Version/s: (was: 2.6)
2.5.1
> Consistency checker should
[
https://issues.apache.org/jira/browse/JCR-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3352:
---
Affects Version/s: (was: 2.6)
2.5
Fix Version/s: (was: 2.6
[
https://issues.apache.org/jira/browse/JCR-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3367:
---
Fix Version/s: (was: 2.6)
2.5.1
> InMemBundlePersistenceMana
[
https://issues.apache.org/jira/browse/JCR-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3329:
---
Affects Version/s: (was: 2.6)
2.5
Fix Version/s: (was: 2.6
[
https://issues.apache.org/jira/browse/JCR-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3382:
---
Fix Version/s: (was: 2.5.1)
(was: 2.2.13)
Removed fix version. It's be
[
https://issues.apache.org/jira/browse/JCR-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3393:
---
Affects Version/s: (was: 2.4.3)
(was: 2.2.13
[
https://issues.apache.org/jira/browse/JCR-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3382:
---
Fix Version/s: (was: 2.6)
2.5.1
> ItemManager.getNode does not d
ready tomorrow.
There's also some demand for a new 2.4.x release with some of the
recent bug fixes, so I think we should target at cutting the 2.4.3
release candidate sometime in the next week or two. If you have any
particular fixes you'd like to see included, please note so in Jira.
BR,
Jukka Zitting
Hi,
On Wed, Jul 25, 2012 at 3:39 PM, Jukka Zitting wrote:
> Then it's probably some other bug in the MicroKernel. For some reason
> it's no longer finding a revision that was there before.
A few more examples in the CI build failures today:
http://ci.apache.org/builders/oak-
301 - 400 of 6330 matches
Mail list logo
