zbendhiba commented on pull request #3370:
URL: https://github.com/apache/camel-quarkus/pull/3370#issuecomment-1016167771
> @zbendhiba your suggestion sounds good. I used this way and didn't think
that it is against best practices in native. If it is possible to put a jar
inside docker image, it would be solution. Current fix uploads a jar into
docker container
>
> ```
> container = new FixedHostPortGenericContainer("az82/docker-derby")
> .withFixedExposedPort(SqlHelper.getDerbyDockerPort(),
1527)
> .withCopyFileToContainer(
> MountableFile.forClasspathResource("derby/" +
jars[0].getName()),
> "/dbs/storedProcedure.jar")
> .waitingFor(Wait.forListeningPort());
> ```
>
> Do I understand correctly, that having jar with stored procedure among
dependencies cause quarkus in native to inspect and process it, Maybe I can use
a current solution, where the jar won't be in dependency, but will be copied
(or created) in this module via maven plugin. Would it help?
No I think it's fine. I was looking at related issues, and was thinking we
have a native error because of this.
Thanks for your answer
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
