Did you do a maven "clean" before building?
I always do a "clean install" when I'm doing things, because if you don't clean it, maven seems to keep old versions in the target directory, and then will include those in the resulting jar / war file.
The easiest way to see if this is your problem is to go to your build area and look at the exploded version in the target directory and double check to see if is has the old dialogs.js file.
If you are using the maven repository to get the files, perhaps someone else forgot to clean before building it.
Ryan On Feb 27, 2008, at 5:41 AM, Martin Breuer wrote:
Hi list, I tried to update our productive system and I found something I can't resolve. It seems that the old /.resources/admin-js/dialogs/dialogs.js (from version 3.0.2) will be used instead of the new one from 3.5.4 What I don't understand: First, on my local system it works and second where this old file came from. All libs are updated and the old one are deleted! I found the dialog.js in the magnolia-module-admininterface-3.5.4.jar and there is the right one. The old one disable the "save" button in every dialog. So what can I do? Best Regards! ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
