When launching the build in PNC with mvn deploy the flatten-maven-plugin is not applied. Make the required changes so this plugin is applied on both builds.

https://issues.redhat.com/browse/WINDUPRULE-614

• Create branch sb-2.7.x
• Bump Spring Boot dependencies to 2.7.x

• https://github.com/snowdrop/rest-http-example
• https://github.com/snowdrop/secured-example
• https://github.com/snowdrop/configmap-example
• https://github.com/snowdrop/crud-example
• https://github.com/snowdrop/health-check-example
• https://github.com/snowdrop/istio-distributed-tracing-example
• https://github.com/snowdrop/cache-example
• https://github.com/snowdrop/circuit-breaker-example
• https://github.com/snowdrop/messaging-work-queue-example

Ignored:

• https://github.com/snowdrop/opentracing-example
• https://github.com/snowdrop/tomcat-logging-example

When using spring-cloud-starter-kubernetes-fabric8-config and Dekorate, there is an incompatiblity issue because spring-cloud-starter-kubernetes-fabric8-config requires fabric8:kubernetes-client:4.x and Dekorate fabric8:kubernetes-client:5.x.

This can be sorted out by excluding the fabric8:kubernetes-client:4.x from spring-cloud-starter-kubernetes-fabric8-config, for example:

https://github.com/snowdrop/configmap-example/pull/92/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R84

Automation
Review components versions.

This spring cloud starter is included within the list of the spring boot starter dependencies

     <dependency>
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-starter-openfeign</artifactId>
        <version>${spring-cloud-netflix.version}</version>
      </dependency>

It should be moved under the list of the spring cloud starters

In the bom, we explicitly declare version 2.2.14 for both Kubernetes and OpenShift Client. When using this bom in a booster, there is a conflict with Kubernetes/OpenShift client version 1.4.34 within io.openshift:openshift-test-utils which throws .

Workaround si to explicitly declare version in the booster pom:

    <dependency>
      <groupId>io.fabric8</groupId>
      <artifactId>kubernetes-client</artifactId>
      <version>1.4.34</version>
    </dependency>
    <dependency>
      <groupId>io.fabric8</groupId>
      <artifactId>openshift-client</artifactId>
      <version>1.4.34</version>
    </dependency>

In future, we will replace OpenShiftTestAssistant with Arquillian Cube which has its own solution for version conflicts, see http://arquillian.org/arquillian-cube/#_dealing_with_version_conflicts

Work with Antonio in preparation of the 2.3.2 release.

Correct me if I'm wrong, but the testsuite is only used to test the BOM, right? So maybe it would be more logical to move it under the same repository as the BOM? What do you think?
@cmoulliard @metacosm @geoand @iocanel @aureamunoz @jacobdotcosta

Some components sen't to others are also productized by ourselves. This issue will be used to collect this information and update the release.yaml file accordingly.

• https://github.com/opentracing-contrib/java-spring-web.git

This is a requirement to use Opentelemetry instead of Opentracing.

The configuration that should be added is:

<properties>
  <spring-cloud-sleuth.version>3.1.3</spring-cloud-sleuth.version>
  <spring-cloud-sleuth-otel.version>1.1.0-M6</spring-cloud-sleuth-otel.version>
</properties>

<dependencyManagement>
  <dependencies>
<!-- Sleuth with Brave tracer implementation -->
      <dependency>
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-starter-sleuth</artifactId>
        <version>${spring-cloud-sleuth.version}</version>
        <exclusions>
          <!-- Exclude Brave (the default) -->
          <exclusion>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-sleuth-brave</artifactId>
          </exclusion>
        </exclusions>
      </dependency>
      <!-- Add OpenTelemetry tracer -->
      <dependency>
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-sleuth-otel-autoconfigure</artifactId>
        <version>${spring-cloud-sleuth-otel.version}</version>
      </dependency>
  </dependencies>
</dependencyManagement>

This has to be done for Spring Boot 2.7.x (it's not compatible with Spring Boot 2.5.x) (related task is #203).

Update the examples to use snowdrop-dependencies 2.2.6.Beta1 and fix CI issues if any exists (possibly missing spring-boot.version property)

Remove java client commands used to interact with the booster from section 2.6.5.
Interaction no longer involves the SSO Java library target/sso-client.jar.

Release a new version of SB as Red Hat Productized:

• Contact the Starter's owner to ask them if they will and when release 2.2.
• This document contains the informations about the versions of dependencies of the snowdrop BOM.
• Jira ticket here

This task has to be done after #203 and #204

Narayana 2.1.3, 2.3.2 and 2.4.0 have been released. All of them contain a bug fix that adds a missing synchronization registry configuration. We should update them in appropriate BOM branches so that they could be included in the next release. No need to make a release just for this change though.

Work on this release.
https://gitlab.cee.redhat.com/middleware/build-configurations/-/merge_requests/148

Hi. It's great to see you participating in the Spring Boot ecosystem. We have a section in the Spring Boot reference documentation with some guidelines about artifact naming. The section talks specifically about starters but the intent is that it is more generally applicable to projects and artifacts in the Spring Boot ecosystem.

Would you please consider renaming this repository and the artifacts it produces to align with the guidelines? Similar updates would be welcome in several other repositories in the Snowdrop organisation.

Release a new version of SB as Red Hat Productized:

• Contact the Starter's owner to ask them if they will and when release 2.2.
• This document contains the informations about the versions of dependencies of the snowdrop BOM.
• Jira ticket here

When I was trying to use Spring 1.5.x BOM - I see its too huge with great length of Spring Boot BOM - wondering if we could just import needed spring--bom in them so that they align with right Spring framework versions

The circleci tests are failing for release 2.4.3.

This is the error:

...
[INFO] Snowdrop Test Suite - Parent ....................... SUCCESS [  0.334 s]
[INFO] Snowdrop Test Suite - Common ....................... SUCCESS [  0.019 s]
[INFO] Snowdrop Test Suite - Common - Entities ............ SUCCESS [ 15.939 s]
[INFO] Snowdrop Test Suite - Common - Utils ............... SUCCESS [  7.827 s]
[INFO] Snowdrop Test Suite - Data JDBC .................... FAILURE [  1.132 s]
[INFO] Snowdrop Test Suite - Data JPA ..................... SKIPPED
[INFO] Snowdrop Test Suite - Health Check ................. SKIPPED
[INFO] Snowdrop Test Suite - Hibernate .................... SKIPPED
[INFO] Snowdrop Test Suite - REST ......................... SKIPPED
[INFO] Snowdrop Test Suite - REST - RESTEasy .............. SKIPPED
[INFO] Snowdrop Test Suite - Caching ...................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 27.428 s
[INFO] Finished at: 2021-02-22T16:23:50+00:00
[INFO] Final Memory: 74M/546M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on project data-jdbc: Compilation failure: Compilation failure:
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTest.java:[20,17] package org.junit does not exist
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTest.java:[21,24] package org.junit.runner does not exist
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTestBase.java:[19,17] package org.junit does not exist
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTest.java:[31,2] cannot find symbol
[ERROR] symbol: class RunWith
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationIT.java:[23,17] package org.junit does not exist
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationIT.java:[24,24] package org.junit.runner does not exist
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationIT.java:[31,2] cannot find symbol
[ERROR] symbol: class RunWith
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTest.java:[38,6] cannot find symbol
[ERROR] symbol:   class Before
[ERROR] location: class dev.snowdrop.testsuite.jdbc.RecordsApplicationTest
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTestBase.java:[46,6] cannot find symbol
[ERROR] symbol:   class Test
[ERROR] location: class dev.snowdrop.testsuite.jdbc.RecordsApplicationTestBase
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationTestBase.java:[64,6] cannot find symbol
[ERROR] symbol:   class Test
[ERROR] location: class dev.snowdrop.testsuite.jdbc.RecordsApplicationTestBase
[ERROR] /tmp/testsuite/data-jdbc/src/test/java/dev/snowdrop/testsuite/jdbc/RecordsApplicationIT.java:[38,6] cannot find symbol
[ERROR] symbol:   class Before
[ERROR] location: class dev.snowdrop.testsuite.jdbc.RecordsApplicationIT
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
...

The snowdrop BOM but also other projects include Ales Justin as Red Hat Developer. Question

• Should we remove it from the different projects where it appears ?
• Should we keep it but remove the mention that he is a Red Hat Developer ?

WDYT @geoand @gytis @metacosm @iocanel

hi team,
im looking for the 2.7.x snowdrop bom version in redhat maven ga

https://maven.repository.redhat.com/ga/dev/snowdrop/snowdrop-dependencies/

but the latest version i see is 2.5.12.Final-redhat-00001
are we planning to deploy redhat's version of 2.7.x there?

thank you.

It is my understanding (ready to stand corrected!) that creating a spring boot application that uses the snowdrop bom follows this expected pattern:

<project>
  ...
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>me.snowdrop</groupId>
        <artifactId>spring-boot-bom</artifactId>
        <version>2.1.6.SP3-redhat-00001</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>
  ...
</project>

The problem with dependency imports is that it doesn't apply to plugins.

In the appsody stack, I've opted to use the spring-boot-dependencies pom as the parent (it introduces no behavior, but does pin versions using property values). While I know a lot of people don't like parent poms, it does make sense for the relationship between an appsody stack and its related/managed/dependent projects.

Bearing Andy Wilkinson's naming conventions in mind, is there a way to split this bom into two pieces: a snowdrop-spring-boot-dependencies pom, and then the snowdrop-spring-boot-bom that can use those dependencies (which then has the release profile in it, etc.)

My goal would be to switch the parent pom for a snowdrop-based stack from the "generic" spring-boot-dependencies to a "snowdrop-spring-boot-dependencies". And the only difference between them should be the values of version variables, and the addition of any dependencies or plugins that might be missing.

Include the request for Narayana supported version in the EAP JIRA ticket

• 2.4.x
• 2.3.x

• Replace the dependency
• Ask docs team to update the documentation
• Ask QE team to update their tests

This might need:

• Tweak the message to make the expectations clearer
• Re-shuffle components in a different way
• Add more product definitions associated to starter we own / productize

Remove CXF dependency

Update versions:

• keycloak to 9.0.3
• resteasy to 4.5.3.Final
• resteasy-spring-boot-starter to 4.5.1.Final

In addition track down all it's mentions (examples, readme, docs) and update them.

We need to investigate this:

Mail from Marek Novotny:

Naina, Rajesh,

We (me and Ant) looked at multiple places and that confused us.

First PNC build for 2.1.12 referenced in released folder supports earlier change which was merged in our source code
http://orch.psi.redhat.com/pnc-web/#/projects/22/build-configs/817/build-records/41786/dependencies -> Spring Boot
2.1.12.RELEASE and Springframework at 5.1.13.RELEASE
and [2] Spring boot parent too have defined that 2.1.12.RELEASE version. So far so good we did that change which looks correct.

But there was a seed of confusion in point 3 in the following still coming from
http://download.eng.brq.redhat.com/released/jboss/rhoar/spring-boot/2.1.12/ which has these details in lists of dependencies:

1. the redhat starters have 2.1.1.redhat-00001
2. redhat built BOM - me.snowdrop:spring-boot-bom:2.1.12.Final-redhat-00001
3. BOM for upstream managed dependencies org.springframework.boot:spring-boot-dependencies:2.1.4.RELEASE-redhat-00001 which
   doesn't corresponds with the above versions.

It seems as an internal version from a different like AMQ boot starter(s) as we would expect it will be 2.1.12.RELEASE-redhat-00001

And that 2.1.4.RELEASE-redhat-00001 [3] declares the values which I wrote in the email with showing wrong versions.

So it could be that, but with careful looking at top of RHOAR SB BOM and confirmation that transitive AMQ SB starter BOM is just
outdated and doesn't matter for us is lucky output from this email thread.

Regards,

[1] - http://download.eng.brq.redhat.com/released/jboss/rhoar/spring-boot/2.1.12/extras/repository-artifact-list.txt
[2] -
https://code.engineering.redhat.com/gerrit/gitweb?p=spring-boot/bom-parent.git;a=blobdiff;f=pom.xml;h=8de837f441f6b704abbd884b9040ae7836501b24;hp=1d73ec390e076ac8dac0f4d430e04a26df70985e;hb=5fb131866aa5ac34e31b5c8f6ea0fbd81625947a;hpb=6d72a7387cd6a9138107af27bd1d0dfdfbba3881
[3] -
https://repository.jboss.org/nexus/service/local/repositories/product-amq-client-02_04_00/content/org/springframework/boot/spring-boot-dependencies/2.1.4.RELEASE-redhat-00001/spring-boot-dependencies-2.1.4.RELEASE-redhat-00001.pom

The keycloak-spring-boot-2-adapter has been released for Spring Boot 2.0.3.RELEASE. We need to update our BOM in order to pull it.