[
https://issues.apache.org/jira/browse/JCR-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting reassigned JCR-845:
-
Assignee: Jukka Zitting
Links Pointing to Javadocs Are Incorrect and Return 404
[
https://issues.apache.org/jira/browse/JCR-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-845.
---
Resolution: Fixed
Fix Version/s: none
Patch applied in revision 529887. Thanks!
Links Pointing
[
https://issues.apache.org/jira/browse/JCR-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-846:
--
Fix Version/s: 1.3
Assignee: Jukka Zitting
Affects Version/s: (was: 1.3)
[
https://issues.apache.org/jira/browse/JCR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-725.
---
Resolution: Fixed
Patch applied in revision 529894. Thanks!
Configuration of CacheManager memory
Bundle persistence name index not case-sensitive
Key: JCR-849
URL: https://issues.apache.org/jira/browse/JCR-849
Project: Jackrabbit
Issue Type: Bug
Components: core
[
https://issues.apache.org/jira/browse/JCR-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-849:
--
Summary: Bundle persistence name index not case-sensitive in MySQL and MS
SQL (was: Bundle persistence
[
https://issues.apache.org/jira/browse/JCR-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-849.
---
Resolution: Fixed
Fixed in revision 529903, by explicitly declaring the NAME column collation as
case
[
https://issues.apache.org/jira/browse/JCR-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-781:
--
Fix Version/s: (was: 1.3)
I reverted the custom socket factory support in revision 529906 based on
+1
cheers
stefan
On 4/17/07, Jukka Zitting [EMAIL PROTECTED] wrote:
Hi,
As previously discussed, I'd like to formally propose to accept the
JCR Mapping codebase and related pieces of code
(http://svn.apache.org/repos/asf/incubator/graffito/trunk/jcr/) to be
moved from the incubating Gaffito
[
https://issues.apache.org/jira/browse/JCR-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-798:
--
Attachment: currentObservationSession.patch
For the record, the attached patch implements a simple check
[
https://issues.apache.org/jira/browse/JCR-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-798.
---
Resolution: Fixed
Fixed in revision 529913 by explicitly removing all registered event listeners
at
Promote the classloader component from contrib
--
Key: JCR-850
URL: https://issues.apache.org/jira/browse/JCR-850
Project: Jackrabbit
Issue Type: New Feature
Reporter: Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-850.
---
Resolution: Fixed
Promote the classloader component from contrib
[
https://issues.apache.org/jira/browse/JCR-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-838:
--
Fix Version/s: 1.3
bad assumptions/error handling in SetValueVersionExceptionTest:
[
https://issues.apache.org/jira/browse/JCR-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-842:
--
Fix Version/s: 1.3
support stores where binary properties are mandatory (such as in nt:resource)
[
https://issues.apache.org/jira/browse/JCR-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-755:
--
Affects Version/s: (was: 1.3)
Add Bundle Persistence Managers
---
[
https://issues.apache.org/jira/browse/JCR-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-786:
--
Affects Version/s: (was: 1.3)
OracleBundlePersistenceManager needs special blob handling for JDBC
Hi,
I recently tried using the jackrabbit snapshot build from
http://people.apache.org/repo/m2-snapshot-repository/org/apache/jackrabbit/. One
problem I discovered is that in the POM for jackrabbit-core for example there
are no versions for jackrabbit dependencies like jackrabbit-api defined.
Christoph Kiehl wrote:
dependency
groupIdorg.apache.jackrabbit/groupId
artifactIdjackrabbit-core/artifactId
version1.3-SNAPSHOT/version
/dependency
dependency
groupIdorg.apache.jackrabbit/groupId
artifactIdjackrabbit-api/artifactId
version1.3-SNAPSHOT/version
/dependency
dependency
Hi,
On 4/18/07, Christoph Kiehl [EMAIL PROTECTED] wrote:
I recently tried using the jackrabbit snapshot build from
http://people.apache.org/repo/m2-snapshot-repository/org/apache/jackrabbit/. One
problem I discovered is that in the POM for jackrabbit-core for example there
are no versions for
Hi,
After finishing all the issues and branching 1.3 I have now updated
the Jackrabbit trunk version to 1.4-SNAPSHOT.
I'll follow up with the 1.3 release candidate later today.
BR,
Jukka Zitting
Jukka Zitting wrote:
Hi,
On 4/18/07, Christoph Kiehl [EMAIL PROTECTED] wrote:
I recently tried using the jackrabbit snapshot build from
http://people.apache.org/repo/m2-snapshot-repository/org/apache/jackrabbit/.
One
problem I discovered is that in the POM for jackrabbit-core for
example
Hi,
On 4/18/07, Christoph Kiehl [EMAIL PROTECTED] wrote:
Jukka Zitting wrote:
The dependency versions are defined in the jackrabbit parent POM using
the Maven dependencyManagement feature. I believe Maven should
automatically download also the parent POM and take the version
numbers from
Jukka Zitting wrote:
[ ] +1 Accept JCR Mapping from Graffito
[ ] -1 Do not accept the component because ...
+1
regards
marcel
[
https://issues.apache.org/jira/browse/JCR-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-847:
---
Attachment: patch.txt
provides the method.
Provide a Method getCredentialsProvider to the SimpleWebdavServlet
[
https://issues.apache.org/jira/browse/JCR-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-847:
--
Priority: Minor (was: Major)
Affects Version/s: (was: 1.2.3)
Fix Version/s: 1.3
Jukka Zitting wrote:
The build number that replaces the SNAPSHOT part is essentially a
timestamp and a sequence number. Since the different components are
built and deployed separately, they receive different timestamps and
sequence numbers.
Actually it seems like the timestamp is the same
Jukka Zitting schrieb:
[ ] +1 Accept JCR Mapping from Graffito
[ ] -1 Do not accept the component because ...
+1
hi vikas,
On 4/16/07, Vikas Bhatia [EMAIL PROTECTED] wrote:
Jackrabbit persistence on DB2 ZOS v 8 is different than it is for most
databases. We had to make certain changes to the jackrabbit core in
order to get it working.
Changes involved 3 java and 2 ddl and 1 repository.xml file in the
[
https://issues.apache.org/jira/browse/JCR-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-615.
Resolution: Fixed
This issue was fixed as part of a major JCR2SPI rewrite in February (Angela,
Handling of binary properties (streams) in QValue interface
---
Key: JCR-851
URL: https://issues.apache.org/jira/browse/JCR-851
Project: Jackrabbit
Issue Type: Improvement
Hi Vikas,
maybe a contribution as a separate zOS DB2 Persistence Manager would
be an idea. I could certainly see something like that as a contrib.
Similar to the Oracle9BundlePersistenceManager idea from Jukka.
regards,
david
On 4/18/07, Stefan Guggisberg [EMAIL PROTECTED] wrote:
hi vikas,
[
https://issues.apache.org/jira/browse/JCR-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-852:
---
Attachment: patch.txt
Change Log-Level in DefaultIOListener
-
Change Log-Level in DefaultIOListener
-
Key: JCR-852
URL: https://issues.apache.org/jira/browse/JCR-852
Project: Jackrabbit
Issue Type: Improvement
Affects Versions: 1.2.3
Reporter: Claus
[
https://issues.apache.org/jira/browse/JCR-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reassigned JCR-852:
--
Assignee: angela
Change Log-Level in DefaultIOListener
-
[
https://issues.apache.org/jira/browse/JCR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Edwards updated JCR-853:
--
Attachment: NodeTypeDefDiff_JCR-853.diff
proposed patch.
[PATCH] Jackrabbit disallows some nodetype
[
https://issues.apache.org/jira/browse/JCR-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg reassigned JCR-853:
-
Assignee: Stefan Guggisberg
[PATCH] Jackrabbit disallows some nodetype changes which are
Hi,
On 4/18/07, Christoph Kiehl [EMAIL PROTECTED] wrote:
Jukka Zitting wrote:
The build number that replaces the SNAPSHOT part is essentially a
timestamp and a sequence number. Since the different components are
built and deployed separately, they receive different timestamps and
sequence
Jukka Zitting wrote:
Ah, perhaps Maven is using a single timestamp for the entire
multimodule build and deploy process. The sequence numbers are managed
in the maven-metadata.xml files on the snapshot repository. Each
component has it's own sequence number, which will get out of sync
from other
[
https://issues.apache.org/jira/browse/JCR-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489845
]
Jukka Zitting commented on JCR-851:
---
In most cases, especially when working with large binaries, the client will not
[
https://issues.apache.org/jira/browse/JCR-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-847.
---
Resolution: Fixed
Patch applied (with some extra javadocs) in revision 530119 and merged to the
1.3
[
https://issues.apache.org/jira/browse/JCR-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489866
]
Julian Reschke commented on JCR-851:
I'm not sure I understand.
The code implementing QValue has no way to predict
[
https://issues.apache.org/jira/browse/JCR-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489870
]
Jukka Zitting commented on JCR-851:
---
The most usual (only?) reason for a client to create QValues is when the client
[
https://issues.apache.org/jira/browse/JCR-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489872
]
Julian Reschke commented on JCR-851:
In which case we should change the contract, right? Right now, making the 99%
[
https://issues.apache.org/jira/browse/JCR-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489878
]
Jukka Zitting commented on JCR-851:
---
I'm not sure I follow you. What kind of an alternative contract do you have in
After spending some time running Jackrabbit in debug mode, I noticed some
peculiar behavior in the Lucene SearchIndex implementation.
When indexing of a Node occurs via the AbstractIndex.addDocument() method,
the Lucene Document object being indexed seems to contain all the indexed
fields,
46 matches
Mail list logo
