Bump various dependencies

[prthakre]

mojo-executor: 2.4.1
qdox: 2.2.0
maven-plugin-annotations: 3.15.1
jaxws-ri: 2.3.7
logback: 1.5.18
commons-lang3: 3.17.0
freemarker: 2.3.34
grizzly-framework: 2.4.4
metrics-core: 4.2.30
various maven plug-ins

Retain current formatting.

[prthakre]

Why was maven-source-plugin removed

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-source-plugin</artifactId>
</plugin>

To fix following maven error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-source-plugin:3.3.1:jar-no-fork (attach-sources) on project opendj-core: Presumably you have configured maven-source-plugin to execute twice in your build. You have to configure a classifier for at least one of them.

[prthakre]

[build-maven (17, macos-latest)]
(https://github.com/OpenIdentityPlatform/OpenDJ/actions/runs/14080233351/job/39431714914?pr=508#logs)

[26/Mar/2025:10:49:30 +0000] category=org.opends.messages.external severity=ERROR msgID=1 msg=Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
	UnixSocketClientProviderStrategy: failed with exception InvalidConfigurationException (Could not find unix domain socket). Root cause NoSuchFileException (/var/run/docker.sock)
	DockerDesktopClientProviderStrategy: failed with exception NullPointerException (Cannot invoke "java.nio.file.Path.toString()" because the return value of "org.testcontainers.dockerclient.DockerDesktopClientProviderStrategy.getSocketPath()" is null)As no valid configuration was found, execution cannot continue.

[prthakre]

Failure with 21 on ubuntu:

Error:  Failures: 
Error:    ReplicationDomainTest.exportAndImport:361->assertExportSucessful:458 expected [83890] but found [0]
[INFO] 
Error:  Tests run: 24940, Failures: 1, Errors: 0, Skipped: 0

guava and grizzly were bumped, should I revert grizzly?

[maximthomas]

guava and grizzly were bumped, should I revert grizzly?

Yes, please. We need to ensure that this update doesn't cause any issues. We could update the grizzly library in a future pull request.

[prthakre]

guava and grizzly were bumped, should I revert grizzly?

Yes, please. We need to ensure that this update doesn't cause any issues. We could update the grizzly library in a future pull request.

Done.

[vharseko]

@maximthomas grizzly affected to OpenIDM
very complex PR

[maximthomas]

Hello @prthakre
Thank you for the contribution.
There are conflicts in the PR and grizzly-framework still affected.
Please fix the PR.
Thanks!

[prthakre]

@maximthomas Looking into this.

EDIT: grizzly-framework was bumped to 2.4.1 since anything newer was causing tests to fail

<groupId>org.glassfish.grizzly</groupId>
    <artifactId>grizzly-framework</artifactId>
    <version>2.4.1</version>

[prthakre]

@maximthomas my local builds are passing with grizzly-framework:2.4.4, is it alright to use this version?
If I recall correctly, 3.x and above have issues

[maximthomas]

Hello @prthakre,
Thank you for your contribution! Everything seems fine except some minor issues.
Please check them.

[vharseko]

may be failed on release stage
use version=15.0
https://mvnrepository.com/artifact/org.sonatype.plugins/nexus-staging-maven-plugin/1.7.0

[prthakre]

Build went through fine and all tests have passed.
Why do we want to go back to such a older version?

[vharseko]

This step used in release workflow only

[prthakre]

Do you mean mvn release:clean release:prepare?
Is the above step failing with 33.4.x, will revert to 15.0