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 "Julian Sedding (JIRA)" <ji...@apache.org> on 2015/10/14 15:19:05 UTC

[jira] [Commented] (OAK-3515) Document how to create diagnostic builds

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

Julian Sedding commented on OAK-3515:
-------------------------------------

A pragmatic approach taken e.g. in Sling is to use even micro version numbers for releases and uneven numbers for snapshots. By following such a convention snapshots can be deployed and no special documentation is required.

Could that be an option also for Oak?



> Document how to create diagnostic builds
> ----------------------------------------
>
>                 Key: OAK-3515
>                 URL: https://issues.apache.org/jira/browse/OAK-3515
>             Project: Jackrabbit Oak
>          Issue Type: Documentation
>          Components: doc
>            Reporter: Thomas Mueller
>            Assignee: Davide Giannella
>             Fix For: 1.3.9
>
>         Attachments: OAK-3515.patch
>
>
> We should have documentation on how to create diagnostic builds. The problem is, oak-core-...snapshot.jar should not be used in the OSGi environment, but oak-core-...r123.jar, to avoid version ordering problems.



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