A2A Java SDK for Jakarta 0.3.0.Final is released!
I am pleased to announce the 0.3.0.Final release of the A2A Java SDK for Jakarta. You can find the release here, and it supports version 0.3.0 of the A2A Protocol Specification.
Since the 0.3.0.Beta1 release, there haven’t been big changes on our side, but we are now aligned with version 0.3.2.Final of the A2A Java SDK. A lot of work has taken place there since the previous version of the A2A Java SDK we aligned with which was 0.3.0.Beta1.
You can find the changes between versions 0.3.0.Beta2 and 0.3.2.Final of the A2A Java SDK here.
Please see the A2A Java SDK for Jakarta 0.3.0.Beta1 release announcement for how to get started with the SDK.
Future Plans
We will continue to align with the A2A SDK for Java, which is currently working towards supporting 0.4.0 of the A2A Protocol Specification. Note that the work on version 0.4.0 of the specification is still in progress.
Also, it is worth pointing out that for WildFly users, the A2A Java SDK for Jakarta currently relies on bundling the jars from the two SDKs, as well as their dependencies, into your application deployment archive. We would like to create a WildFly feature pack for this, which would follow the normal WildFly pattern of enabling a subsystem which would make all the A2A libraries available automatically to deployments, thus removing the need to bundle them in your application.
However, we have decided that the wildfly-extras/a2a-java-sdk-server-jakarta repository is not the correct place for such a feature pack, since it is meant to be used by people wanting to integrate in other Jakarta runtimes. Instead, we are considering adding it to the WildFly AI Feature Pack. This will be announced separately when it happens.
Get involved
-
If you have any issues with the SDK, please open an issue. Also, pull requests are welcome!
