Add notes for unsupported WAR deployment strategy (#1987)

Author: MatKuhr

docs-java/guides/dependencies.mdx

@@ -182,6 +182,10 @@ It does not yet include it as a dependency in your project.
 The [SAP Java Buildpack](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/a3f90069d6cd41da82f34a6123d82ce6.html) brings some dependencies that are also brought by the SAP Cloud SDK.
 This can lead to conflicts when using a `war` deployment.
 
+:::danger WAR Deployments are not recommend
+We strongly advise against using WAR deployments and provide no support for this scenario.
+:::
+
 To prevent any SAP Java Buildpack issues we recommend using the `cf-tomee7-bom`
 ([or Tomcat or TomEE BOMs](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/6c6936e8e4ea40c9a9a69f6783b1e978.html)) followed by our `sdk-bom`.
 
@@ -295,6 +299,8 @@ As a result the SAP Java Buildpack BOM is removed from the `dependencyManagement
 
 </details>
 
+:::
+
 ### Background: Dependency Version Conflicts
 
 The dependency versions from the `sdk-bom` and the Buildpack may differ.

docs-java/guides/spring-boot-war-deployment.mdx

@@ -15,6 +15,12 @@ keywords:
   - cap
 ---
 
+:::danger No longer recommended
+We strongly advise against using WAR deployment and provide no support for this scenario.
+This guide is outdated and was last tested with Spring version 5, which is no longer supported as well.
+Please use the standard JAR deployment strategy instead.
+:::
+
 This document outlines how to adjust a Spring Boot project to use WAR deployment (also known as traditional deployment).
 The traditional deployment of Spring helps overcome exceptions related to the SAP JCo library.