I want to add some configuration to classpath (generated by Maven-Jar-plugin), but I do not want them to have a jar Inside, but in an external folder. In this way I will be able to edit the configuration of no impersonation. I got a solution, but is there no less complex solution?
Or maybe I'm wrong and this is a bad pattern - in the classpath but storing structures outside the jar? It is possible that it is better to store app config and add app to runtime in user's home directory? For example, I want to allow the end user to edit log4j.properties and translations.
Regards,
I like app configs (like user home directory, as you suggested ), But allow the user to provide agreement / system property to override this location. To look at the classpath, in my opinion, is not the best solution, since the concept of a classpath is quite a foreign thing for most users, and it may be difficult for some programmers too.
Comments
Post a Comment