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 (JIRA)" <ji...@apache.org> on 2007/07/02 12:00:04 UTC
[jira] Created: (JCR-995) Release the OCM component
Release the OCM component
-------------------------
Key: JCR-995
URL: https://issues.apache.org/jira/browse/JCR-995
Project: Jackrabbit
Issue Type: New Feature
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Fix For: 1.4
The contrib/jackrabbit-jcr-mapping/jcr-mapping should be promoted from contrib into a jackrabbit-jcr-ocm component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-995) Release the OCM component
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553614 ]
Jukka Zitting commented on JCR-995:
-----------------------------------
Christophe, what's the status in jcr-mapping? Ready for an upgrade to trunk and going out in Jackrabbit 1.4?
> Release the OCM component
> -------------------------
>
> Key: JCR-995
> URL: https://issues.apache.org/jira/browse/JCR-995
> Project: Jackrabbit
> Issue Type: New Feature
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Blocker
> Fix For: 1.4
>
>
> The contrib/jackrabbit-jcr-mapping/jcr-mapping should be promoted from contrib into a jackrabbit-jcr-ocm component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-995) Release the OCM component
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-995.
-------------------------------
Resolution: Fixed
Upgraded the jackrabbit-ocm and jackrabbit-ocm-nodemanagement components from sandbox to Jackrabbit trunk in revisions 607620 and 607621. To switch existing checkouts to the new locations, use the following commands:
cd /path/to/checkout/of/jackrabbit-jcr-mapping/jcr-mapping
svn switch https://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-ocm
cd /path/to/checkout/of/jackrabbit-jcr-mapping/jcr-nodemanagement
svn switch https://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-ocm-nodemanagement
Or just scrap the previous checkouts and do a fresh checkout (or update an existing one) of https://svn.apache.org/repos/asf/jackrabbit/trunk.
> Release the OCM component
> -------------------------
>
> Key: JCR-995
> URL: https://issues.apache.org/jira/browse/JCR-995
> Project: Jackrabbit
> Issue Type: New Feature
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Blocker
> Fix For: 1.4
>
>
> The contrib/jackrabbit-jcr-mapping/jcr-mapping should be promoted from contrib into a jackrabbit-jcr-ocm component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-995) Release the OCM component
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553820 ]
Christophe Lombart commented on JCR-995:
----------------------------------------
Yes I think so. I just made a small fix in the nodemanagement (pck change).
I'm working with Sébastien Deleuze on the Spring integration. We will send the patch the Spring module team.
So, it is not necessary to move the Spring subproject to the trunk.
> Release the OCM component
> -------------------------
>
> Key: JCR-995
> URL: https://issues.apache.org/jira/browse/JCR-995
> Project: Jackrabbit
> Issue Type: New Feature
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Blocker
> Fix For: 1.4
>
>
> The contrib/jackrabbit-jcr-mapping/jcr-mapping should be promoted from contrib into a jackrabbit-jcr-ocm component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-995) Release the OCM component
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-995:
------------------------------
Priority: Blocker (was: Major)
> Release the OCM component
> -------------------------
>
> Key: JCR-995
> URL: https://issues.apache.org/jira/browse/JCR-995
> Project: Jackrabbit
> Issue Type: New Feature
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Blocker
> Fix For: 1.4
>
>
> The contrib/jackrabbit-jcr-mapping/jcr-mapping should be promoted from contrib into a jackrabbit-jcr-ocm component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-995) Release the OCM component
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536972 ]
Christophe Lombart commented on JCR-995:
----------------------------------------
Can we also contriburte the jcr-nodemanagement ?
Maybe with the following structure :
jackrabbit-jcr-ocm
core
nodemanagement
> Release the OCM component
> -------------------------
>
> Key: JCR-995
> URL: https://issues.apache.org/jira/browse/JCR-995
> Project: Jackrabbit
> Issue Type: New Feature
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Blocker
> Fix For: 1.4
>
>
> The contrib/jackrabbit-jcr-mapping/jcr-mapping should be promoted from contrib into a jackrabbit-jcr-ocm component.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.