Skip to content

Update framework name for JMX to be inline with other frameworks#1216

Merged
ramonskie merged 5 commits intocloudfoundry:feature/go-migrationfrom
stokpop:feature/go-migration-jmx-name
Mar 19, 2026
Merged

Update framework name for JMX to be inline with other frameworks#1216
ramonskie merged 5 commits intocloudfoundry:feature/go-migrationfrom
stokpop:feature/go-migration-jmx-name

Conversation

@stokpop
Copy link
Copy Markdown
Contributor

@stokpop stokpop commented Mar 19, 2026

Now reported as "jmx=5000", changed into "JMX":

 Detected frameworks: [Client Certificate Mapper Container Security Provider jmx=5000 Java Opts]

Also added comma's to this list. And made this line simelar with brackets and comma's:

Finalizing frameworks: Client Certificate Mapper,Container Security Provider,jmx=5000,Java Opts

Note that the port is reported already in this log, so it will not be missing:

   Installing framework: JMX
   -----> JMX enabled on port 5000

Just noticed there is also an integration test for Java 25 in there. Let me know if that should be removed for this PR.

@ramonskie
Copy link
Copy Markdown
Contributor

yeah the integration test is a bit to much in this case. please remove that and i wil merge it.
we are going to cut a release today.

@stokpop
Copy link
Copy Markdown
Contributor Author

stokpop commented Mar 19, 2026

@ramonskie Java 25 integration test is reverted

@ramonskie ramonskie merged commit c75e705 into cloudfoundry:feature/go-migration Mar 19, 2026
1 check passed
@ramonskie
Copy link
Copy Markdown
Contributor

thanks or your contribution @stokpop

@stokpop stokpop deleted the feature/go-migration-jmx-name branch March 24, 2026 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants