-
-
Notifications
You must be signed in to change notification settings - Fork 302
Changes in 4.1.0
For Bndtools 4.0.0 changes, see https://github.com/bndtools/bndtools/wiki/Changes-in-4.1.0.
-
Macros
${removeall;list;list}
and${retainall;list;list}
are updated to work with empty args. -
Adds support for Bearer (OAuth2) authentication. If the
<server>
configuration has only a password and no username, then Bearer authentication is in effect with the password used as the token.-connection-settings: server;id="https://*.server.com";password="oauth2token"
will cause
Authorization: Bearer oauth2token
request header to be sent to servers matching the glob
https://*.server.com
.See https://github.github.com/maven-plugins/site-plugin/authentication.html for an example of a
<server>
configuration for OAuth2. -
Baselining will no longer report version mismatches when either side of the baselining has a major version of 0. See https://semver.org/#spec-item-4.
-
The pattern support for globbing things like package names has been updated to support some regular expression features. This should be backwards compatible for most normal usages.
-
The Bnd maven plugins now support Maven property references using array subscripts such as
Bundle-License: ${project.licenses\\[0\\].name}
-
bnd-baseline-maven-plugin now ignores projects with
pom
packaging type.
- Tasks of type
TestOSGi
no longer add themselves as a dependency of thecheck
task. This is to allow for multiple such tasks which should not be executed for thecheck
task. - A new task type
Bndrun
is added which can be used to run bndrun files.
- Tasks of type
TestOSGi
no longer add themselves as a dependency of thecheck
task. This is to allow for multiple such tasks which should not be executed for thecheck
task. So if you need your tasks of typeTestOSGi
to be dependencies ofcheck
, you must modify thecheck
task to add them as dependencies. - The pattern support for globbing things like package names has been updated to support some regular expression features. This should be backwards compatible for most normal usages but some characters may now require escaping. For example
[
and]
will need to be escaped as\\[
and\\]
since the[
and]
characters are now used for regular expression character classes.
- None at this time.