You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Jérôme Verstrynge <jv...@gmail.com> on 2010/09/30 02:48:39 UTC

About OCM-43

  Hi,

I am new to JackRabbit. I have just registered to the mailing list. I 
was googling about OCM and its absence from 2.1.1 code. Finally found 
https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel.

I tried the jackrabbit-ocm-1.5.3-upgrade-to-2.1.1.patch from Kadir Alaca 
on trunk code and confirm it compiles and passes all JUnit tests.

It seems like the plan is to move OCM code in JackRabbit JCR Commons, 
correct? Do you want me to create a patch for this (including Kadir's)?

Cheers,

Jérôme Verstrynge
(It is 2H45 AM here, going to bed, will read answers tomorrow...)

P.S.: I have never developed code for ASF. Do I need to fill some 
agreement to join the JackRabbit project?

Re: About OCM-43 -> Patch to move OCM back into core project

Posted by Jérôme Verstrynge <jv...@gmail.com>.
  Hi,

I have created a zipped patch to move OCM code back to core project. It 
is based on trunk 1003095.

I have created a JackRabbit-OCM module next to the other modules. It 
contains all OCM code from sub-project, including Kadir's patch. I have 
attached the pom.xml to the parent. All compiles and passes JUnits tests 
successfully. However, since I am very new to the project, someone 
senior/knowledgeable should review my work.

- I get some warnings about version of dependencies. It seems like we 
could remove several and/or update many.
- I have left the LICENSE, NOTICE and README files as is.
- The OCM-module compile target and source were set at 1.6. I see 
comments containin 1.5 config. Are we happy with 1.6 only?

If everyone is happy, may be we could release new version of the OCM 
sub-project and tell the community corresponding code will be included 
in next main project's release.

Cheers,

Jérôme

Re: About OCM-43

Posted by Jérôme Verstrynge <jv...@gmail.com>.
  On 30/09/2010 15:09, Jukka Zitting wrote:
> It seems like the plan is to move OCM code in JackRabbit JCR Commons,
>> correct? Do you want me to create a patch for this (including Kadir's)?
> See http://markmail.org/message/fbx5jrzibva2r3pt for the current
> status of OCM. In hindsight it seems like the decision to move OCM and
> other similar codebases outside the main Jackrabbit trunk has just
> caused unnecessary complexity and confusion, so we may want to
> consider reverting that decision just like we already did for
> components like JCR-RMI and JCR Servlets.
OK. I will try to create a new JackRabbit OCM module for main project 
based on core code + Kadir's. Will return a contributor's agreement too.

Jérôme

Re: About OCM-43

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Thu, Sep 30, 2010 at 2:48 AM, Jérôme Verstrynge <jv...@gmail.com> wrote:
> I am new to JackRabbit. I have just registered to the mailing list. I was
> googling about OCM and its absence from 2.1.1 code. Finally found
> https://issues.apache.org/jira/browse/OCM-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel.
>
> I tried the jackrabbit-ocm-1.5.3-upgrade-to-2.1.1.patch from Kadir Alaca on
> trunk code and confirm it compiles and passes all JUnit tests.

Thanks for the confirmation! I just applied the pending patch and
marked OCM-43 as resolved.

> It seems like the plan is to move OCM code in JackRabbit JCR Commons,
> correct? Do you want me to create a patch for this (including Kadir's)?

See http://markmail.org/message/fbx5jrzibva2r3pt for the current
status of OCM. In hindsight it seems like the decision to move OCM and
other similar codebases outside the main Jackrabbit trunk has just
caused unnecessary complexity and confusion, so we may want to
consider reverting that decision just like we already did for
components like JCR-RMI and JCR Servlets.

> P.S.: I have never developed code for ASF. Do I need to fill some agreement
> to join the JackRabbit project?

No formal agreements are needed to get started. If you end up making
substantial contributions, then we'll need a contributor license
agreement [1] from you. See [2] for pointers to more information.

[1] http://www.apache.org/licenses/icla.txt
[2] http://www.apache.org/foundation/getinvolved.html

BR,

Jukka Zitting