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 2009/04/27 17:02:37 UTC

[jira] Moved: (OCM-18) include OCM nodetypes config file in JAR

     [ https://issues.apache.org/jira/browse/OCM-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting moved JCR-1260 to OCM-18:
---------------------------------------

          Component/s:     (was: jackrabbit-ocm)
           Issue Type: Bug  (was: Improvement)
    Affects Version/s:     (was: 1.4)
             Workflow: no-reopen-closed, patch-avail  (was: jira)
                  Key: OCM-18  (was: JCR-1260)
              Project: Jackrabbit OCM  (was: Jackrabbit Content Repository)

> include OCM nodetypes config file in JAR
> ----------------------------------------
>
>                 Key: OCM-18
>                 URL: https://issues.apache.org/jira/browse/OCM-18
>             Project: Jackrabbit OCM
>          Issue Type: Bug
>            Reporter: Paul Mietz Egli
>
> It would be useful to include the custom_nodetypes.xml file in the packaged jcm-mapping JAR so client projects don't have to copy the nodetype configuration file around.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.