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 2008/09/24 15:50:44 UTC

[jira] Commented: (JCR-1756) Include OCM in the main Jackrabbit build when using Java 5

    [ https://issues.apache.org/jira/browse/JCR-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634142#action_12634142 ] 

Jukka Zitting commented on JCR-1756:
------------------------------------

With the OCM components now included in the main Jackrabbit build, I have removed the separate Jackrabbit-ocm build from Hudson.

> Include OCM in the main Jackrabbit build when using Java 5
> ----------------------------------------------------------
>
>                 Key: JCR-1756
>                 URL: https://issues.apache.org/jira/browse/JCR-1756
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: maven
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 1.5
>
>         Attachments: JCR-1756.patch
>
>
> Currently the OCM component are separate from the rest of Jackrabbit build due to the fact that they need Java 5 to compile. I'd like to add a java5 profile to the main Jackrabbit build that contains the OCM components and is automatically activated when building with Java 5 or higher.
> This would simplify build instructions and allow us to remove the extra Jackrabbit-ocm Hudson build that we currently use to build the OCM component.

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