GitHub user ansell opened a pull request:
https://github.com/apache/commons-rdf/pull/39
COMMONSRDF-62 : Ignore japicmp by default while version is 0.x
japicmp is activated by commons-parent profile with it set to break the
build on any incompatibilities. In order to have it still run by default, but
not break the build, an activeByDefault=true profile is added, which will be
switched off by activating any other profiles explicitly, including the release
profile, but which allows development of 0.x without interruption from japicmp.
This is either an alternative, or in addition to,
https://github.com/apache/commons-rdf/pull/38
The core reason is that japicmp is not recognising 0.3 -> 0.4 as a major
version jump, in Semantic Versioning terms. It is treating that as a minor
version jump, where the API incompatibilities still apply.
Signed-off-by: Peter Ansell <[email protected]>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ansell/commons-rdf COMMONSRDF-62-japicmp
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-rdf/pull/39.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #39
----
commit b0af14c5fe03589aea331ae254c345fcd023a79f
Author: Peter Ansell <[email protected]>
Date: 2017-09-13T00:36:52Z
COMMONSRDF-62 : Ignore japicmp by default while version is 0.x
japicmp is activated by commons-parent profile. In order to have it still
run by default, but not break the build, an activeByDefault=true profile is
added, which will be switched off by activating any other profiles explicitly,
including the release profile, but which allows development of 0.x without
interruption from japicmp.
Signed-off-by: Peter Ansell <[email protected]>
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
