Hi, On Tue, Jan 28, 2014 at 1:54 AM, Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: > On Tue, Jan 28, 2014 at 7:41 AM, <tri...@apache.org> wrote: >> + org.apache.jackrabbit.oak;version="0.15.0", >> + org.apache.jackrabbit.oak.api;version="0.15.0", >> + org.apache.jackrabbit.oak.api.jmx;version="0.15.0", > > We should version packages independent of Oak release version. definitely!
> Probably a better way would be to > > 1. Add explicit package-info.java with correct bnd version > annotations. Then we need not explicitly list down package names in > pom.xml yes. I always wanted to do this, but was too lazy/busy in the end. I created https://issues.apache.org/jira/browse/OAK-1362 to track this. > 2. Untill we have a 1.0 release we can set the package version to > 1.0.0 and not change it if even if any API changes considering that > pre 1.0 builds are to be considered as unstable wrt API right. > Post 1.0 we take care to bump the version as per OSGi Sematic Version > guidelines [1] definitely. I also think that the amount of exported packages is very large. It looks like we didn't really know how to modularize oak and just exported basically everything :-) I suggest to separate some API (and SPI) bits into separate bundles (see OAK-1238 and OAK-1239). This certainly raises awareness of the modularization also for non-osgi setups. regards, toby > > Chetan Mehrotra > [1] http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf
