Up to now, I have used Eclipse’s export function to create executable jars for both, the main program and the JUnit test program. Automate the creation of the executable jar Update/Comment (): I now have created a blog, which (in my opinion) shows a better way of creating a lean executable JAR file using gradle: see here. In this post, I will show, how to make configuration and template files accessible again. However, if a developer creates an executable jar, all needed files, including configuration and template files are packed into the jar file as a default. JAR files are java archive files and as such, are not designed to be manipulated by operations folks („ops“). Have you ever tried to create an executable jar file, while keeping all configuration files outside of the jar file, accessible to operations folks? Here is a step by step guide.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |