One of the primary tasks in release management is environment promotion.From development to test or from test to production, environment promotion is a step which should be as much automated as possible.If i put my properties files in a jar, and put them in a folder on my classpath everything worked.But I did not want to have jar my files everytime a change was made. If i place the properties files in %WEBLOGIC_HOME%/user_projects/domains/MYDOMAIN then they are getting picked up, without having to be placed in a jar file.However, these operations are limited to the ‘predefined fields whose values are very likely to change’…and what happens if we need to modify one of the considered ‘not very likely’?For this reason, spring-boot-devtools will disable those caching options by default.Cache options are usually configured by settings in your will automatically restart whenever files on the classpath change.
Flagging the dependency as optional is a best practice that prevents devtools from being transitively applied to other modules using your project.Does anyone know how to include external properties files in Weblogic?Thanks, I figured this out and have it working the way I would expect. If i added a folder to my classpath, or put the properties files in a folder on my classpath, the jars in the file were picked up, but not properties files.First step is to create a Maven POM file and put this on the Eclipse Workspace or Project level.The Workspace pom should build the whole workspace and the pom in a project only that particular OSB project.
With Maven we are able to build & deploy OSB projects.