[Jeremy Vanderburg]

I have been having an issue lately with a persistent warning: “Deployment is out of date due to changes in the underlying project contents…” This does not seem to happen with every project, just on a few of them. There is nothing in common between the projects this happens with that does not exist on the projects that do not exhibit this behavior. I have performed several troubleshooting steps to attempt to resolve the issue to no avail. The steps I have taken thus far are:

close/re-open/deploy project
clean/rebuild/deploy project
restart MyEclipse, clean/deploy project
right click on project -> MyEclipse -> Remove all validation markers
right click on project -> refresh

None of these steps has affected the issue at all. If I make a change to a file in the project, the warning comes up twice. I found an old post that contained the same (or very similar) issue, but none of the steps in there helped either. It does not appear that post was ever officially recognized as being resolved. In any case, I didn’t want to re-open an old thread, so I posted this new one. The old one is here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-9209.html.

I have pasted the output from the installation details at the bottom of this post.

If anyone can help it would be greatly appreciated!

Thanks,
Jeremy

*** Date:
Tuesday, August 5, 2008 2:22:24 PM MDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\MyEclipse 6.5\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files\MyEclipse 6.5\../Pulse\Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\Program Files\MyEclipse 6.5\../Pulse\Common\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-clean
-configuration
C:\Program Files\MyEclipse 6.5\configuration
-vm
C:\Program Files\Pulse\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll

[Loyal Water]

Jeremy,
What server are you deploying the application to?

I would like you to open the Project Deployment window and remove the projects that have been deployed. Now go to your server directory and make sure the projects have been completely undeployed.

Now refresh your projects in the package explorer and try deploying the projects again. Do you still get the error message showing up?

[Jeremy Vanderburg]

Nipun,

I am deploying to WebLogic 9.1. I have completely undepoyed the application from my application server, and verified that it was completely undeployed from the app server. I refreshed the application, and even before I deployed the application, the warning had still not gone away. I deployed it again, and it still made no difference – the warning remains.

Thank you,
Jeremy

[Loyal Water]

Do you have your projects checked into a version control system ?

[Jeremy Vanderburg]

Yes, I have several projects checked in to visual source safe. The project in question at the moment was checked out by me several weeks ago.

EDIT: just to make sure the project was checked out correctly, I have verified there are no read-only files within that project’s directory.

[Loyal Water]

I think its VSS is causing the issue here. If you move the project to another directory and work with it, do you still face the same issue?

[Author]

Posts