Hi,
On 9/11/07, Christophe Lombart [EMAIL PROTECTED] wrote:
Sounds good. Would you mind doing JCR-995 (moving the core part
outside contrib) as well while you're at it?
I would like to finalise the annotation support before moving outside the
contrib. Just to be sure to have something
Hi Jukka,
On 9/12/07, Jukka Zitting [EMAIL PROTECTED] wrote:
OK. I'd like to start pushing for the 1.4 release though, and it would
be good to have the OCM included in the preliminary release builds as
soon as possible even if there still remains some work to be done.
Annotation is
Hi Jukka,
Sounds good. Would you mind doing JCR-995 (moving the core part
outside contrib) as well while you're at it?
I would like to finalise the annotation support before moving outside the
contrib. Just to be sure to have something stable in term of code and in
term of ocm project
Hi,
Am Dienstag, den 11.09.2007, 09:00 +0200 schrieb Christophe Lombart:
Concerning the annotation support, we have to use java 1.5 but maybe some
jackrabbit/ocm users are still in java 1.4.
For Sling, Felix is using another framework (Kxml if I remember). I'm not
sure that it is interesting
Hi,
On 9/5/07, Christophe Lombart [EMAIL PROTECTED] wrote:
Following the issue on the jackrabbit core dependency (
http://issues.apache.org/jira/browse/JCR-1115) and seeing other dependency
issues, I would like to reorganize the OCM contrib.
Sounds good. Would you mind doing JCR-995 (moving
Following the issue on the jackrabbit core dependency (
http://issues.apache.org/jira/browse/JCR-1115) and seeing other dependency
issues, I would like to reorganize the OCM contrib.
Indeed, the subproject jcr-mapping annotation should not depend on :
- Jackrabbit core
- Digester
- Lucene
- Derby
