Skip to content

Releases: Intersmash/intersmash

Intersmash 0.0.2 (Rollercoaster)

02 Jul 06:48
@fabiobrz fabiobrz
v0.0.2
18b1e3c
Compare
Choose a tag to compare
Intersmash 0.0.2 (Rollercoaster) Latest
Latest

Release Notes

Here we go with the Intersmash 0.0.2 (Rollercoaster) release! 🎉

It is based on the work done through the Intersmash milestone 2 and it was used to test interoperability between WildFly/JBoss EAP 8/JBoss EAP XP 5 candidate releases and other runtimes, e.g.: Keycloak/Red Hat Build of Keycloak, Kafka/Red Hat AMQ Streams etc..

The 0.0.2 artifacts which were generated from this tag have been deployed to the JBoss Maven repository and can be used in your projects by adding a Maven dependency on them, e.g.:

...
<dependency>
   <groupId>org.jboss.intersmash</groupId>
   <artifactId>intersmash-core</artifactId>
   <version>0.0.2</version>
</dependency>
<dependency>
   <groupId>org.jboss.intersmash</groupId>
   <artifactId>intersmash-provisioners</artifactId>
   <version>0.0.2</version>
</dependency>
...

javadoc and sources artifacts are included as well.

A number of bug fixes and improvements have been delivered, and you can learn more about by looking into the release milestone or by searching the resolved issues.

This release is based on the Intersmash (https://github.com/Intersmash/intersmash) repository:

What's Changed

  • [issue 136] - Adding a specific e2e script for the OpenShift CI periodic prow job (and minor fixes/cleanup) by @fabiobrz in #137
  • [issue 134] - Document next milestone goals by @fabiobrz in #135
  • [issue 138] - Prepare for EAP 8 support by @fabiobrz in #141
  • Mount secrets into bootable jar container in BootableJarImageOpenShiftProvisioner by @mnovak1 in #145
  • [issue 146] - Fix Eap7ImageOpenShiftApplication by @fabiobrz in #147
  • [issue 148] - Fixing missing factories and test by @fabiobrz in #149
  • [issue 27] - Making the Keycloak SAML Adapter feature pack version configurable for WildFly deployments by @fabiobrz in #150
  • [issue 153] - Adding property to externalize the WildFly Datasources Galleon pack by @fabiobrz in #154
  • XP Channel for wildfly-jar-maven-plugin by @tommaso-borgato in #151
  • [issue 140] Examples: demonstrate WildFly with Keycloack SAML adapter Galleon Pack s2i provisioning with Intersmash by @fabiobrz in #152
  • [issue 161] - Use the :centos7 tag for PostgreSql and MySql images by @fabiobrz in #162
  • [issue 144] - Support Red Hat Build of Keycloak (new productised version of Keycloak) by @fabiobrz in #155
  • Freezing the default supported Infinispan operator channel to 2.3.x by @fabiobrz in #169
  • Refactoring to pull out the Maven utils for deployments from the testsuite modules into the provisioners by @fabiobrz in #165
  • [issue-139] Improve documentation by @rsearls in #166
  • [issue 168] Bump Infinispan operator CRDs by @fabiobrz in #171
  • [issue 159] - Freezing supported versions in Intersmash 0.0.2 release by @fabiobrz in #164
  • Adding some reference comments to the Infinispan operator provisioner implementation and test by @fabiobrz in #174
  • [issue 176] - FIxing the InfinispanOperatorProvisioner::scale() method by @fabiobrz in #175
  • Bump WildFly/EAP bits defaults to latest by @fabiobrz in #172

New Contributors

Full Changelog: v0.0.1...v0.0.2

Contributors

rsearls, mnovak1, and 2 other contributors
Assets 2
Loading
0 Join discussion

Intersmash 0.0.1 (Moosetee)

26 Jan 23:06
@fabiobrz fabiobrz
v0.0.1
bead693
Compare
Choose a tag to compare
Intersmash 0.0.1 (Moosetee)

Release Notes

This is the Intersmash 0.0.1 (Moosetee) release, actually the first Intersmash release! 🎉

It is based on the Intersmash 0.0.1 milestone 1 and it aims at enabling interoperability testing on OpenShift between several community runtime services, as WildFly, Keycloak, Kafka, Infinispan etc. and their product counterparts, like Red Hat JBoss EAP, Red Hat SSO, RedHat AMQ Streams, Red Hat Datagrid.

The 0.0.1 artifacts which were generated from this tag have been deployed to the JBoss Maven repository and can be used in your projects by adding a Maven dependency on them, e.g.:

...
<dependency>
   <groupId>org.jboss.intersmash</groupId>
   <artifactId>intersmash-core</artifactId>
   <version>0.0.1</version>
</dependency>
<dependency>
   <groupId>org.jboss.intersmash</groupId>
   <artifactId>intersmash-provisioners</artifactId>
   <version>0.0.1</version>
</dependency>
...

javadoc and sources artifacts are included as well.

A number of bug fixes and improvements have been delivered, and you can learn more about by looking into the release milestone or by searching the resolved issues.

This release is based on the Intersmash (https://github.com/Intersmash/intersmash) repository:

APIs stability commitment

No policy has been finalized yet. At the moment, the guidelines are to keep deprecated code long enough to allow for smooth transition, but given this is the first release this could change, or be better defined, suddenly 🙂

That being said a discussion will be started via an issue or a Wiki thread, to try to draft the final API stability policies and practices.

Known Issues

Notable changes

New Contributors

Full Changelog: https://github.com/Intersmash/intersmash/commits/v0.0.1

Contributors

kabir, rsearls, and 5 other contributors
Assets 2
Loading