Starting from v1.0.0, Isis has adopted semantic versioning for its versioning policy.
Version numbers are in the form
This scheme would be adopted for both core and components.
Version numbers are NOT kept in sync between core and components. Therefore components should clearly indicate the version of core that they depend upon.
For example, here is a possible flow of how versioning might evolve over a number of releases:
core 1.0.0is released
isis-objectstore-jdo 1.0.0 is released, dependent oncore 1.0.0`
isis-viewer-wicket 1.0.0is released, dependent on
core 1.0.1is released. This is NOT picked up by either of the above components.
isis-objectstore-jdo 1.0.1is released, dependent on
core 1.0.1. This also incorporates a number of its own bug fixes
core 1.1.0is released, providing a new feature
isis-viewer-wicket 1.1.0is released, using the new feature provided by
isis-viewer-wicket 1.2.0is released, offering its own new feature. It still depends on core
isis-objectstore-jdo 1.0.2is released. This has some bug fixes and depends on
core 1.1.0(even though it does not require the new feature introduced in
core 1.1.0, it tracks the latest available version of
core 2.0.0is released, making breaking changes to the objectstore API
isis-objectstore-jdo 2.0.0is released, dependent on
isis-objectstore-jdo 2.1.0is released, providing a new feature. It depends on
isis-viewer-wicket 1.2.1is released. This has some bug fixes, and also updates to run against
At the end of this sequence we have:
isis-objectstore-jdo 2.1.0, dependent upon
isis-wicket-viewer 1.2.1, dependent upon
Version ranges may not be used. If necessary, end-users can use
<dependencyManagement elements to have combine components built against different versions of core.
That said, this can introduce instability and so generally we recommend that end-users configure the
maven-enforcer-plugin and its DependencyConvergence rule. This will avoid "jar hell" (components having conflicting dependencies of core).
If there is a conflict, we would ask that end-users engage with Isis committers to have an updated version of the component(s) pushed out.
All edits are reviewed before going live, so feel free to do much more than fix typos or links. If you see a page that could benefit from an entire rewrite, we'd be thrilled to review it. Don't be surprised if we like it so much we ask you for help with other pages :)NOTICE: unless indicated otherwise on the pages in question, all editable content available from apache.org is presumed to be licensed under the Apache License (AL) version 2.0 and hence all submissions to apache.org treated as formal Contributions under the license terms.