Version 2.5.0.0
-
Fixed a binder bug in which bind-with-deps could bind modules into different sets of services depending on traversal order. (SDKTOOLS-140)
-
The binder no longer generates or installs empty bindings descriptors for library and profile modules. (SDKTOOLS-136)
-
Fixed a bug where unbind would fail to unbind a module from a service when the module was bound into that service due to a bind-with-deps operation on a downstream module. (SDKTOOLS-135)
-
Fixed bug which caused binding to fail on some file systems such as eCryptfs due to long file names, and improve failure handling in the binder. (SDKTOOLS-134)
-
Fixed bug where mapper classes with multiple mappers were not getting renamed properly during module creation from module packs (SDKTOOLS-130)
-
Fixed provider injection warning from PromotionsCommitUsedUnits feature (STLCORE-54).
-
Fixed incorrect JNDI context being used in subsequent pojo feature execution when the initial execution cycle was initiated by an SBB feature event handler (STLCORE-46).
Version 2.4.0.3
-
Improved handling of how the top-level module is renamed when using the 'create-module' command (SDKTOOLS-92)
-
Changed behaviour of sdkadm -f and -e arguments. These will now exit sdkadm after executing the specified commands unless the new -i (force interactive) argument is specified.
-
Added -q option to sdkadm which will suppress some command processing logging.
-
Renamed default resolvers to online-resolvers.xml. Added offline-resolvers.xml.
-
Split local resolver configuration out into local-resolvers.xml.
-
Added support for property injection during <default-module-build> macrodef execution. Any properties written to ${generated}/build.properties prior to <default-module-build> will be available during annotations processing.
-
Renamed 'clean' target to 'clean-module', and renamed all non-branch publish-* targets to 'publish-*-module'. All targets named *-module now operate only on a module, whereas all targets named *-branch will operate recursively. e.g. publish-local-module will publish the current module, whereas publish-local-branch will publish the current module and all nested children. (BLDSUPP-19)
-
Certain targets (clean, publish-*) are now 'dynamic' and will behave differently based on where they are executed. e.g. executing 'publish-local' in a module which has nested modules will publish all nested modules (i.e. a publish-local-branch), whereas running 'publish-local' in a module with no children will invoke 'publish-local-module'. The non-dynamic behaviour can still be explicitly invoked via the *-module or *-branch target variants (BLDSUPP-19).
-
IDE setup targets (idea-setup, eclipse-setup, idea-clean, eclipse-clean) are now only available in the root of an SDK (STLPACK-182).
-
Relevant targets for each module build are now determined automatically based on module type and content. Old build files should be modified to remove imports of 'build/default-branch-targets.xml' and 'build/default-targets.xml' and instead import the unified 'build/targets.xml'. The old import statements will continue to work to enable backwards compatibility with 2.3.1 SDKs, but they will produce a runtime warning on each build.
-
All temporary build infrastructure artifacts are now written to the
build/targetdirectory. Repositories created by go-offline will be put into therepositoriesdirectory. Module build output remains inMODULE/target/. (BLDSUPP-34, STLPACK-35) -
Added example Python script for REST API interactions to build/bin/
Version 2.3.1.16
-
Updated the SentinelRAAToRoOcsRAA and SentinelRAAToDccaOcsRAA mappers to use application specific message factories so that RAAs sent by Sentinel will include the right Diameter Application-Id. (STLCORE-38)
-
Update the SIS dependency to 2.5.2.21
-
Support overriding of
db.typeandpostgres.jdbc.dirin the installer (OCS-338) -
Update the HTTP RA dependency from 2.2.0.6 to 2.2.0.11
Version 2.3.1.13
-
Update Rhino SDK dependency to 2.4.0.14
-
Avoid
finderror when initialising SDK -
Fix go-offline script when it is run through the installer
-
Disallow conflicting go-offline repository names
-
Enhancements to the Sentinel SDKs for Undeploying modules and redeploy commands. See General Development Cycles
-
Improvements to the user experience through the addition of a Logical Service ID for each Service
-
Support for custom CGIN and SIS versions has been added. The installer will scan for custom versions and use those if present.
-
Fix a bug in the go-offline script when the installer runs interactively (OCFE-3766)
-
Fix a NoClassDefFoundException in the Diameter Mediation layer (STLCORE-30)
-
Enable the installer to install against production Rhino (VOLTE-1385)
-
Add a SuppressOCSInteraction feature. This feature was originally added later in the Sentinel 2.1.0.x series and has now been added to the 2.3.1.x series (STLCORE-22)
-
Fix a bug when OCS finalisation is not required (STLCORE-19)
-
Upgrade to GWT 2.7.0
-
Use of REM 1.4.0.8 or later is recommended
-
Use of REM 1.4.0.7 or later is recommended
Version 2.3.1.9
-
Add ability to see which services would be affected by a
redeployoperation (SDKTOOLS-43) Usage:ant -Dredeploy.only-show-services=true redeploy-all -
Add
redeployandredeploy-alltasks (SDKTOOLS-71 and SDKTOOLS-72) -
Remove use of cascade-uninstall from the binder (SDKTOOLS-71)
-
Change
undeployandundeploy-alltasks to not use cascade-uninstall (SDKTOOLS-44) -
Make go-offline work on a Mac
-
Prompt for confirmation by default for all undeploy tasks
-
Updated the required Rhino version to be 2.4.0.14 (or later)
-
Enable terminal echo in the installer (VOLTE-1962)
-
Fix a memory leak with various tracers when using the Multi FSM SBB (STLCORE-14)
-
Minor performance improvements when using Sentinel Selection Key’s Iterator
-
Increase the available memory for a GWTC compile for user feature extensions to REM
-
Update DB Query RA dependency to 1.4.0.3 (VOLTE-1721)
Version 2.3.1.8
-
Quieten log levels by default for SDK tools (SDKTOOLS-45)
-
Quieten Ivy by default for the SDK
-
Quieten Ivy bootstrap unless specified otherwise
-
Add support for dry-run propagation through a number of commands
-
Create a verbose logfile when performing builds
-
Miscellaneous bugfixes and improvements
Version 2.3.1.5
-
Add deploy-module, bind-module and configure-module commands to
sdkadm -
Improve user control over the configurer’s and deployer’s dependency traversal order (SDKTOOLS-40). Module authors can now specify
e:configureorderto control the traversal order of a module and its dependencies. Much like the existinge:deployorder, it defines the modules as a comma separated list of module names. For bothe:configureorderande:deployorder, the module itself can now be included at any point in the given order. I.e. the module itself can be configured/deployed either before or after its dependencies. -
Adjust some memory properties for the default Rhino SDK. Set the max new size to 512MB, and set the heap minimum and maximum size to 2048MB
-
Add support for module property propagation between modules that publish properties
-
Fix go-offline local repo name rewriting
-
Run init-sdk if necessary
-
Use an SDK specific Ivy cache rather than the default
-
First 2.3.1 release for Sentinel Express
-
Handle the case where sessionState.getLatestOcsAnswer() is null (STLIN-35)
-
Fix bugs in several sentinel-core module packs
-
Rewrite the installer in Java (VOLTE-1692)
-
Initial Sentinel 2.3.1 series release, included in Sentinel VoLTE
-
For users migrating from Sentinel VoLTE 2.2.x, or Sentinel 2.1.x the SDK has been completely replaced with a brand new vastly simpler SDK.
