-
Bug Report
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
Problem
- There are two artifacts that imply to be the enterprise version of the Spring Boot Webapps:
- camunda-bpm-spring-boot-starter-webapp-ee:7.13.0-alpha3-ee
- camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee
- While it might not be a problem in context of other containers (e. g. JBoss), spring boot users are facing maven artifacts heavily because of its highly maven based development workflow
- From a users perspective, it is hard to decide which artifact is the right one
- This might lead to confusion and even bubble up in support
- On top of that, camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee effectively contains the community edition
Solution
Only provide one enterprise artifact for the webapps
Bonus
The -ee suffix is removed from the enterprise artifact id so the user can select enterprise by adding the -ee suffix to the version.
This is the controller panel for Smart Panels app
[CAM-11726] In Spring Boot, two enterprise webapp artifacts are available
| Description |
Original:
*Problem*
* There are two artifacts that imply to be the enterprise version: ** {{camunda-bpm-spring-boot-starter-webapp-ee:7.13.0-alpha3-ee}} ** {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} * While it might not be a problem in context of other containers (e. g. JBoss), spring boot users are facing maven artifacts heavily because of its nature * From a users perspective, it is hard to decide which artifact is the right one which might lead to confusion * On top of that, {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} effectively contains the community edition *Solution* Only provide one enterprise artifact for the webapps *Bonus* The {{-ee}} suffix is removed from the enterprise artifact id so the user can select enterprise by adding the {{-ee}} suffix to the version. |
New:
*Problem*
* There are two artifacts that imply to be the enterprise version of the Spring Boot Webapps: ** {{camunda-bpm-spring-boot-starter-webapp-ee:7.13.0-alpha3-ee}} ** {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} * While it might not be a problem in context of other containers (e. g. JBoss), spring boot users are facing maven artifacts heavily because of its highly maven based development workflow * From a users perspective, it is hard to decide which artifact is the right one * This might lead to confusion and even bubble up in support * On top of that, {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} effectively contains the community edition :) *Solution* Only provide one enterprise artifact for the webapps *Bonus* The {{-ee}} suffix is removed from the enterprise artifact id so the user can select enterprise by adding the {{-ee}} suffix to the version. |
| Mentioned Roles |
| Mentioned Groups |
| Attachment | New: Screenshot 2020-04-02 at 12.05.28.png [ 32999 ] | |
| Attachment | New: Screenshot 2020-04-02 at 12.13.32.png [ 33000 ] |
| Description |
Original:
*Problem*
* There are two artifacts that imply to be the enterprise version of the Spring Boot Webapps: ** {{camunda-bpm-spring-boot-starter-webapp-ee:7.13.0-alpha3-ee}} ** {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} * While it might not be a problem in context of other containers (e. g. JBoss), spring boot users are facing maven artifacts heavily because of its highly maven based development workflow * From a users perspective, it is hard to decide which artifact is the right one * This might lead to confusion and even bubble up in support * On top of that, {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} effectively contains the community edition :) *Solution* Only provide one enterprise artifact for the webapps *Bonus* The {{-ee}} suffix is removed from the enterprise artifact id so the user can select enterprise by adding the {{-ee}} suffix to the version. |
New:
*Problem*
* There are two artifacts that imply to be the enterprise version of the Spring Boot Webapps: ** {{camunda-bpm-spring-boot-starter-webapp-ee:7.13.0-alpha3-ee}} ** {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} ** !Screenshot 2020-04-02 at 12.13.32.png|thumbnail! * While it might not be a problem in context of other containers (e. g. JBoss), spring boot users are facing maven artifacts heavily because of its highly maven based development workflow * From a users perspective, it is hard to decide which artifact is the right one * This might lead to confusion and even bubble up in support * On top of that, {{camunda-bpm-spring-boot-starter-webapp:7.13.0-alpha3-ee}} effectively contains the community edition :) *Solution* Only provide one enterprise artifact for the webapps *Bonus* The {{-ee}} suffix is removed from the enterprise artifact id so the user can select enterprise by adding the {{-ee}} suffix to the version. !Screenshot 2020-04-02 at 12.05.28.png|thumbnail! |
| Mentioned Roles |
| Mentioned Groups |
| Mentioned Roles |
| Mentioned Groups |