Barrie, Yes I noticed both of those issues :)
So what do you suggest? Should I create a new maven module called Config and drop my properties, log4net properties files there? I then add that module as a dependancy. Also, during my production build, I will just make sure I have that folder to my classpath right? In my java code, since I was assuming it was in my /resources before, and now it is in a seperate maven module, will I need to change anything or since it is still in my classpath all is good, the ONLY difference now is that it won't be embedded in my .jar right? I am really getting confused by this, I need someone to clarify this as its confusing me :) On Wed, Apr 18, 2012 at 8:19 PM, Barrie Treloar <[email protected]> wrote: > On Thu, Apr 19, 2012 at 6:44 AM, S Ahmed <[email protected]> wrote: > > The problem I was having was, when on the production server, I had a > > properties file in my /resources folder, and I modified in on the server > > but noticed it was still returning the old values. > > > > I then realized that the class loader was loading the file from the .jar > > itself, and not reading from the file (even though the file was updated > to > > reflect production settings). > > Read up on classpath resolution rules. > Your file in the *.jar is trumping the one in the directory. > > The other sin to commit is including a log4j settings file in your jar. :) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
