You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/05/26 18:14:17 UTC

[jira] [Commented] (OAK-2006) Verify the maven baseline output and fix the warnings

    [ https://issues.apache.org/jira/browse/OAK-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559307#comment-14559307 ] 

Michael Dürig commented on OAK-2006:
------------------------------------

How should we go forward on this one? 

After today's discussion re. modularisation I figure we should start failing the build once the base line feature detects a violation in package export versions so we start properly maintaining it early in the new release cycle. 

I'll do so by the end of the week unless some one objects. 

> Verify the maven baseline output and fix the warnings
> -----------------------------------------------------
>
>                 Key: OAK-2006
>                 URL: https://issues.apache.org/jira/browse/OAK-2006
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Alex Parvulescu
>            Assignee: Michael Dürig
>              Labels: build
>             Fix For: 1.3.0
>
>         Attachments: OAK-2006.patch, baseline-oak-core.patch
>
>
> Currently the maven baseline plugin only logs the package version mismatches, it doesn't fail the build. It would be beneficial to start looking at the output and possibly fix some of the warnings (increase the OSGi package versions).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)