jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Created] (OAK-3842) Adjust packag export declarations
Date Wed, 06 Jan 2016 15:31:39 GMT
Michael Dürig created OAK-3842:

             Summary: Adjust packag export declarations 
                 Key: OAK-3842
                 URL: https://issues.apache.org/jira/browse/OAK-3842
             Project: Jackrabbit Oak
          Issue Type: Task
            Reporter: Michael Dürig
            Assignee: Michael Dürig
             Fix For: 1.4

We need to adjust the package export declarations such that they become manageable with our
branch / release model. 

See http://markmail.org/thread/5g3viq5pwtdryapr for discussion.

I propose to remove package export declarations from all packages that we don't consider public
API / SPI beyond Oak itself. This would allow us to evolve Oak internal stuff (e.g. things
used across Oak modules) freely without having to worry about merges to branches messing up
semantic versioning. OTOH it would force us to keep externally facing public API / SPI reasonably
stable also across the branches. Furthermore such an approach would send the right signal
to Oak API / SPI consumers regarding the stability assumptions they can make. 

An external API / SPI having a (transitive) dependency on internals might be troublesome.
In doubt I would remove the export version here until we can make reasonable guarantees (either
through decoupling the code or stabilising the dependencies). 

I would start digging through the export version and prepare an initial proposal for further

/cc [~frm], [~chetanm], [~mmarth]

This message was sent by Atlassian JIRA

View raw message