You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Jukka Zitting <ju...@gmail.com> on 2008/01/30 14:55:36 UTC
jackrabbit-core 1.4.1 release plan
Hi,
I think we need to issue a patch release of jackrabbit-core with a fix
to the recently reported binary value issues. I'd also like to include
some of the other recent fixes. See below for the current list of
fixes to include:
[JCR-1046] Non-versionable children of a versionable node should not
be updated when a merge fails
[JCR-1305] JNDI data sources with BundleDbPersistenceManager:
UnsupportedOperationException
[JCR-1323] When using QueryImpl.setLimit() and
QueryImpl.setOffset(), then NodeIterator.getSize() reports wrong size
[JCR-1331] Improper deprecation of Locked class
[JCR-1332] CLONE -Aggregate include ignored if no primaryType set
[JCR-1341] Cluster Journal directory should be created automatically
[JCR-1346] InternalValue.createCopy for binary properties (jcr:data)
causes problems
Let me know if any other issues should be included. I'd like to target
already next week for this patch release.
Note that, as recently discussed, I plan to include *only* the
jackrabbit-core component in this patch release.
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.1 release plan
Posted by Marcel Reutegger <ma...@gmx.net>.
Jukka Zitting wrote:
> Let me know if any other issues should be included. I'd like to target
> already next week for this patch release.
I also noticed the error message multiple times, which is reported in JCR-1354,
but I don't know what causes it and how difficult it is to fix. might even be
mis-configuration...
WDOT?
regards
marcel
Re: jackrabbit-core 1.4.1 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Feb 5, 2008 11:44 AM, Alexander Nesterov <al...@gmail.com> wrote:
> I would like to know whether it's feasible to fix JCR-1359 in 1.4.1
> release as it's quite critical case for our project? If not, then
> could someone give at least rough estimates when JCR-1359 is planned
> to be fixed?
Yes, it's an important issue. I'll give it a look today and see what I
can do. If there's a reasonably easy fix, then it'll definitely go
into 1.4.1. Otherwise we may need to reconsider JCR-584, and it's
unfortunately quite difficult to estimate how long that'll take.
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.1 release plan
Posted by Alexander Nesterov <al...@gmail.com>.
Hello,
On Jan 30, 2008 4:55 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
> Let me know if any other issues should be included. I'd like to target
> already next week for this patch release.
>
I would like to know whether it's feasible to fix JCR-1359 in 1.4.1
release as it's quite critical case for our project? If not, then
could someone give at least rough estimates when JCR-1359 is planned
to be fixed?
--
Alexander Nesterov
Re: jackrabbit-core 1.4.1 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Jan 30, 2008 4:02 PM, Ard Schrijvers <a....@hippo.nl> wrote:
> Not sure if it is an issue we already want to address, but Jackrabbit
> 1.4 does not work with the just released lucene 2.2.3. Lucene 2.2.3 has
> quite some changing regarding refCounting and this does not work well
> ATM with the jr 1.4 refCounting / caching of readers. It is not yet a
> jira issue, but as i already said, I am not sure wether we want to
> address it in the first place...
It probably makes sense to file it at least as a known issue in Jira.
I'd be happy to include a reasonable fix in 1.4.1, but IMHO it's no
problem if such a fix is not available as our stated dependency is to
Lucene 2.2.0.
Just curious, is Lucene breaking backwards compatibility or is this
just because we're integrating with Lucene much more deeply than
people normally do?
BR,
Jukka Zitting
RE: jackrabbit-core 1.4.1 release plan
Posted by Ard Schrijvers <a....@hippo.nl>.
Hello
> Jukka Zitting wrote:
> Let me know if any other issues should be included. I'd like
> to target already next week for this patch release.
Not sure if it is an issue we already want to address, but Jackrabbit
1.4 does not work with the just released lucene 2.2.3. Lucene 2.2.3 has
quite some changing regarding refCounting and this does not work well
ATM with the jr 1.4 refCounting / caching of readers. It is not yet a
jira issue, but as i already said, I am not sure wether we want to
address it in the first place...
-Ard
>
> Note that, as recently discussed, I plan to include *only*
> the jackrabbit-core component in this patch release.
>
> BR,
>
> Jukka Zitting
>
Re: jackrabbit-core 1.4.1 release plan
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Feb 5, 2008 11:58 AM, Dominique Pfister <do...@day.com> wrote:
> I was hoping that the following would make it into 1.4.1 too:
>
> [JCR-1358] Cluster revision file not closed on repository shutdown
>
> When running a lot of tests that start up and shutdown a repository
> very often, it can become quite a nuisance.
Yes, definitely something to release in 1.4.1.
I noticed you already committed the fix to the 1.4 branch, thanks!
BR,
Jukka Zitting
Re: jackrabbit-core 1.4.1 release plan
Posted by Dominique Pfister <do...@day.com>.
Hi Jukka,
I was hoping that the following would make it into 1.4.1 too:
[JCR-1358] Cluster revision file not closed on repository shutdown
When running a lot of tests that start up and shutdown a repository
very often, it can become quite a nuisance.
WDYT?
Kind regards
Dominique
On 30/01/2008, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> I think we need to issue a patch release of jackrabbit-core with a fix
> to the recently reported binary value issues. I'd also like to include
> some of the other recent fixes. See below for the current list of
> fixes to include:
>
> [JCR-1046] Non-versionable children of a versionable node should not
> be updated when a merge fails
> [JCR-1305] JNDI data sources with BundleDbPersistenceManager:
> UnsupportedOperationException
> [JCR-1323] When using QueryImpl.setLimit() and
> QueryImpl.setOffset(), then NodeIterator.getSize() reports wrong size
> [JCR-1331] Improper deprecation of Locked class
> [JCR-1332] CLONE -Aggregate include ignored if no primaryType set
> [JCR-1341] Cluster Journal directory should be created automatically
> [JCR-1346] InternalValue.createCopy for binary properties (jcr:data)
> causes problems
>
> Let me know if any other issues should be included. I'd like to target
> already next week for this patch release.
>
> Note that, as recently discussed, I plan to include *only* the
> jackrabbit-core component in this patch release.
>
> BR,
>
> Jukka Zitting
>