0.6.5

No new functionality here. Just clean up around the build system.

0.6.4

Small bug fix to exclude signature files from bundle (i.e. Uber) JARs

0.6.3

Expanding the number of annotations available in the spals-appbuilder-annotations bundle. Also shading the org.slf4j package such that this can be independently upgraded in applications.

0.6.2

More work to provide fully self-contained bundles. Specifically:

1. Relocate common java packages using the prefix net.spals.shaded. This will allow application depending on AppBuilder to choose their own versions of common packages.
2. Put more annotations in the spals-appbuilder-annotations bundle. This allows applications to use this as an independent bundle for service development instead of having to rely on the larger spals-appbuilder-app-core bundle, for example.

0.6.1

Releasing production modules as fully self-contained bundles (i.e. uber JARs). This should help with using AppBuilder in build systems such as Bazel which require explicit dependencies lists.

To use bundles in Maven:

<dependency>
  <groupId>net.spals.appbuilder</groupId>
  <artifactId>spals-appbuilder-app-core</artifactId>
  <version>${appbuilder.version}</version>
  <classifier>bundle</classifier>
</dependency>

To use bundles in Bazel:

load("@bazel_tools//tools/build_defs/repo:maven_rules.bzl", "maven_jar")

maven_jar(
  name = "appbuilder_core_bundle",
  artifact = "net.spals.appbuilder:spals-appbuilder-app-core:{appbuilder.version}:jar:bundle",
)

0.6.0

Several new features are now available in this release:

1. A new build option is available for WebAppBuilder: enableCors. This will create a globally permissive CORS filter for the web application. Note that this is not a recommended security practice and is available only for convenience.
2. All example applications used in testing have been consolidated to the app-examples module
3. A new application type is now supported: gRPC (available in the app-grpc plugin module). This integration allows one to seamlessly create micro-services within a gRPC server.

0.5.0

Adding two features in this release:

1. A new MapStoreIndex service. This service allows creation of, deletion of, and reads from a secondary index on a MapStore. Note that this is a separate service from MapStore because not all MapStore implementations will have a matching MapStoreIndex implementation (for example, Cassandra, for which secondary indexes are not recommended). MapStoreIndex implementations do exist for MapDB (the embedded default), DynamoDB, and MongoDB.

2. Automatically add a Swagger endpoint to all web applications. This allows Swagger annotations to be used right away on an API resource classes.

0.4.1

Small tweak to the password KeyStore which removes its dependence on Java Cryptography Extension. This means that the default KeyStore service can be used out of the box without any additional set up.

0.4.0

New features:

1. Added MongoDB implementation for the MapStore service
2. Added new KeyStore service which stores keys for bi-directional encryption of Strings and byte arrays
3. Added default KeyStore implementation which uses a master password (i.e. Password Based Encryption)
4. Integration KeyStore service with configuration provider. In other words, this allows configuration provider to handle encrypted configuration.

Bug fixes:

1. In DefaultExecutorServiceFactory, prevent leaked ExecutorService with duplicated tags.

0.3.0

Upgrades the ExecutorServiceFactory API. In particular:

1. Simplifying API to only build executor services with ExecutorServiceFactory.Key instances.
2. Allows individual executor service instances to be stopped
3. Adds support for scheduled executor services

Also, better error reporting around service initialization errors. These used to be swallowed by Guice, but now will be reported to the console.