Quarkus native integration with Dynatrace Maven OneAgent

Hello Team,

I am trying to implement the below  feature in a Quarkus application 

The version of Quarkus is 3.8.5 as mentioned in the support document.  JDK version 21 , dynatrace-native-maven-plugin version is  2.0.1. 
It is rest based application which makes a call towards oracle database. 
What we see is that during the native complie the  dynatrace binaries are not getting attached, due to which the agent is not running when we deploy the application in Openshift.  
The --native-agent-path path is not getting set during the build time.  Had anyone integrated  dynatrace-native-maven-plugin with  Quarkus application  ? 
I need some pointers to debug this  issue.

<plugin>
	<groupId>com.dynatrace.buildtools.graalnative</groupId>
	<artifactId>dynatrace-native-maven-plugin</artifactId>
	<version>2.0.1</version>
	<executions>
		<execution>
			<id>setup-agent</id>
			<phase>generate-resources</phase>
			<goals>
				<goal>setup-build-agent</goal>
				<goal>copy-runtime-agent</goal>
			</goals>
			<configuration>
				<agentDownload>
					<environmentUrl>masked</environmentUrl>
					<apiToken>masked</apiToken>
				</agentDownload>
				<agentOptions>loglevelcon=info,agentconfigpath=src/main/resources/agent.json</agentOptions>
			</configuration>
		</execution>
	</executions>
	<extensions>true</extensions>
</plugin>

Hi,
I found this link where some issues with building the Quarkus Native image are mentioned. In my case, I followed their recommendation to build it directly pointing to my local GraalVM .
“./mvnw clean package -Pdynatrace-native -Dnative -Dquarkus.native.container-build=false -Dquarkus.native.builder-image=graalvm -DskipTests”
I hope this helps.
Regards, Gustavo.
Not able to build Quarkus Native image using container build while using dynatrace-native-maven-plugin · Issue #45325 · quarkusio/quarkus · GitHub.

One way to solve the problem regarding dynatrace-native-maven-plugin is to mount the .dynatrace folder into the container using a -v volume. Then update the -J-agentpath to use the in-container location and also update the -cp path that references the oneagent-graalnative-feature.jar.