Hi Samuel, I think that's normal. There is a sling/startup directory, that I believe holds the JAR binaries. If that directory exists I don't think it gets refreshed with the binaries in the app jar. If you just delete that single directory, it should suffice.
Also, to actually update code on a *running* Nakamura server, the Maven deploy target should let you do that when deploying bundles. I'm pretty sure the startup directory then gets updated with the new binary so it sticks when the server reboots.. probably want to just double-check that tidbit first in a dev environment if you plan to use live code updates. Cheers, Branden On Wed, Nov 21, 2012 at 1:13 PM, Samuel Champoux <sam...@1337.ca> wrote: > Hi all, > > We recently lost hours of work trying to figure out why the code we > changed did not work on the server, while it was working locally. > The server runs with postgres and nakamura starts as a "nakamura" user. > We though that updating the jar and re-starting the server would be enough > for our changes to work, but it wasn't the case. We had to delete all the > data directory and start a new container to make it work. > > Is this normal? Did we do something wrong? > > Thank you, > *---* > *Samuel Champoux* > > > _______________________________________________ > oae-dev mailing list > oae-dev@collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/oae-dev > >
_______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
