Relocation Release

After the original publication home of dinistiq was discontinued, development was stalled for quite some years.

Now we finally relocated the canonical publication target to Maven Central. Besides that, the canonical place for the source code also was relocated, as were some Maven packages' group and artifact IDs.

As a result, nothing changed very much besides the more recent dependency versions and underlying packages. Updating the referred libraries and Java baseline will also be on the roadmap for the coming time.

Bugfix Release

To stick to the idea, that the 0.8 track is the last release to support Java 8, a small bugfix is necessary, which avoids the annoying error log entries, when using dinistiq without the web part.

Servlet API Update

Besides the necessary version updates in dependencies and tests without any code changes inside the project, this release updates the Servlet API version to 4.0 optional dependency. This way, dinistiq can be used with recent web-based applications.

This will be the last release to support Java 8, and the few code changes aim in the Java 11 (LTS) direction.

Dependency Reduction Release

Since having a small footprint not only means having less code and memory consumption but also that a library only depends on that many other components as is really worth the extra dependency and weight, this release eliminates one external library dependency.

As a result, dinistiq now only depends on

• the at inject JAR for JSR330 annotation
• Simple Logging Facade for Java (slf4j) for logging

The Servlet API needed when using the web integration part is now an optional dependency, which a web project using dinistiq has to declare separately - and will already have in place if it's a web project anyway.

The other referenced components are only used for testing.

Besides this, all dependencies are brought to current versions and have been tested to work together with this release.

Qualifier Release

Despite the fact that dinistiq passes the TCK for JSR330 it lacked handling of qualifiers following the standard. This has been fixed with this release at the account of performance of the container.

None of my projects uses this feature, so the implementation fully relies on the dinistiq tests and the TCK run integrated in these tests.

Except for this, the dependency set has been updated, and the tests again have increased their coverage of the code.

Leaner Servlet Container Integration

With dinistiq 0.5 the web integration is mostly rewritten now depending on the Servlet API version 3.1. This removes the indirection through a central dispatching servlet but sadly also removes its URL pattern matching capabilities. Apart from Servlet API 3.1 other dependencies were updated as well, test coverage once again was extended and two bugs relating to class discovery were fixed.

RegisterableServlet instances from the dinistiq scope are now registered with the servlet container directly. They now present a number servlet specification compatible URL patterns (no regular expressions any more) and the same ordering indicator as with previous releases.

Like other projects I'm working on this project was migrated to TestNG. In this case mostly to harmonize licensing of the used dependencies.

Availability Release

Starting with Release 0.4 the dinistiq artifacts are not only published to a custom maven repository but also to the jcentral repository. This renders integration of dinistiq easier since you will most likely not need to add another external repository to - say - your local mirror. Also, the test suite was enhanced while the core functionality did only get minor extensions since it right now does everything the depending projects needs.

This is the last dinistiq release to be used with the Google App Engine Java PaaS.

Compliance Release

While using JSR330 annotations, dinistiq was not fully equivalent in the interpretation of these with other CDI implementations - but only with spring. This release changes this behaviour. Release 0.3 also introduces are more concise test suite to ensure the intended behaviour and extends the API with a few minor additions.

Stabilization Release

This release deals with code clean-ups and bug reduction. Some of the problems showed up shortly after the first 0.1 release when dinistiq started to be used in more personal projects.

Introduction Release

Dinistiq started as a development support tool in summer 2013 for tangram. This is the first release as a module to be used independently. It is meant to be feature-complete just for the elements needed with tangram and what I'd like to see supported in a Dependency Injection framework.