You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Dockerfile includes steps to build/package the configuration resources, which from a seperation of concerns viewpoint is not ideal. Traditionally configurations were built/packaged with Maven into a JAR-file, which was then added onto the classpath in some way together with Frank!Framework/WebApp.
It would be great if we could use Maven to build/package the configuration resources and simply copy the resulting JAR-file to the Docker image in the Dockerfile. Frank!Framework Test should cover our use-case for the most part already and could be used as example.
Initial scope for the Maven build/package should be just packaging all the resources into a JAR-file and modifying the Dockerfile to simply copy the resulting JAR-file.
The text was updated successfully, but these errors were encountered:
Currently the Dockerfile includes steps to build/package the configuration resources, which from a seperation of concerns viewpoint is not ideal. Traditionally configurations were built/packaged with Maven into a JAR-file, which was then added onto the classpath in some way together with Frank!Framework/WebApp.
It would be great if we could use Maven to build/package the configuration resources and simply copy the resulting JAR-file to the Docker image in the Dockerfile. Frank!Framework Test should cover our use-case for the most part already and could be used as example.
Initial scope for the Maven build/package should be just packaging all the resources into a JAR-file and modifying the Dockerfile to simply copy the resulting JAR-file.
The text was updated successfully, but these errors were encountered: