Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <688104406.1222249184251.JavaMail.jira@brutus>
Date: Wed, 24 Sep 2008 02:39:44 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1756) Include OCM in the main Jackrabbit
 build when using Java 5
In-Reply-To: <59179404.1222178744170.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jukka Zitting resolved JCR-1756.
--------------------------------

    Resolution: Fixed

Patch applied in revision 698480. Resolving as Fixed.

> 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.