There is one application where I work where there are still manual builds used i.e manually moving the servlet classes and jsp files from Dev to QA and finally to Prod.

This is the method used in this application which cant be changed for some wierd reasons.BTW this is not the problem.

We did a manual build where we transferred jsp files from QA to PROD recently.

And we noticed that the jsp file content does not correspond to the updated jsp's but have the same content to the jsp file which was present in the server prior to the deployment.

We did not re-start tomcat since jsp files upon updation automatically changes its contents.

This problem persisted even after 6 hours of deployment If we consider the time standards which are different which may cause some delay.

So to fix this we had to individually go into every jsp file and just type something save it and delete this change and save it.Then it worked perfectly.

But finally the jsp file content before and after was never changed we just did this to change the modification date.

If we think in terms of timestamp problem how can this be possible coz the old jsp files which were present in the server prior to deployment was atlest one month old and the ones getting deployed were defenitely newer than that.

Why did this happen? This did not happen when we did same type of deployments earlier.

How can we prevent this from happening in the future.