Hi jan.galinski@holisticon.de,

thank you for raising this issue. I had a quick look in the code and I think it should already display the "-ee" version. Thus, I changed the issue type to "Bug Report".

We will discuss this in the development team and together decide on how we want to proceed with this. We will keep you posted.

Best,
Miklas

Hi Miklas,

well, I implemented that part myself, but although there is an "isEnterprise" check, there is no unit test and I guess it never worked.

I debugged it yesterday ... even when I run the ee version, the camunda-engine jar that is used to get the package/manifest/implementation version is always the regular open source engine jar ... with the 7.12.0 version.

I guess a possible fix would be to  put the camunda and starter versions with the correct ee suffix in the MANIFEST of the starter jar itself rather then relying on derived information.

Jan

Hi Jan,

Thanks for letting us know about this. As I currently do not consider this a crucial problem, we will not schedule it for implementation as of now. As a support customer you can raise a support case if you would like us to prioritize this. If you would like to contribute a fix and implement a test case, maybe our ProcessEngineLoggingRule can help (see https://github.com/camunda/camunda-commons/tree/master/testing and https://github.com/camunda/camunda-bpm-platform/blob/7.12.0/engine/src/test/java/org/camunda/bpm/engine/test/standalone/authentication/LoginAttemptsTest.java for an example).

Cheers,
Thorben

We are closing this ticket as part of our backlog grooming. Reasons:

• We did not receive sufficient evidence that this ticket is important