Deployment Assembly: The currently displayed page contains invalid values

Question

I imported a Java Web application from Sourceforge, and I did three working weeks efforts to get rid off all red crosses attached to the project name and packages, but now I cou

Answer 1

I experienced this issue as well. It was caused by me deleting another project on which my current project was dependent. I fixed the issue by opening the file org.eclipse.wst.common.component in the .settings folder and deleting the dependency. This fixed the issues and I was able to edit the deployment assembly.

Section I removed: (utility.jar is the name of my offending jar)

   <dependent-module archiveName="utility.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/utility/utility">
        <dependency-type>uses</dependency-type>
    </dependent-module>

Someone else I work with was able to fix it by deleting the jar from their build path.

Hope this helps anyone that hits this issue.

Answer 2

eclipse -clean didn't fix it for me. My workaround: In eclipse delete the project (don't delete on disk). Then in the filesystem delete .project .classpath and .settings/* Then in eclipse, same workspace, create new webproject with same name as the old one. It created the project and found all my source. Now Deployment Assembly works again! After that, I updated build path to have the proper project and lib dependencies.

Answer 3

Please look at this answer. If clean won't help, then probably something is wrong with your project's specific settings. I would suggest you to examine every file inside .settings/ directory.

I know this is not a ready-to-go solution, but may be at least a starting point.

Answer 4

Delete .project .classpath and .settings then cleate a new(temporally) workspace import your project in the new workspace, this will generate new .project .classpath and .settings files. Then open the old workspace again and issue is fixed. You can delete the temporally workspace if you don't need it

Answer 5

I suffered the same problem, and I realized it started just after I installed into my Neon.1a Eclipse a certain old plugin, aimed to versions 3.x.

So I uninstalled that plugin, and the problem dissapeared without changing my workspace in any.

(Just to complete the information, I'll say that the "culprit" was the Randalco EHP plugin, but I suppose any old version plugin might be suspicious too).

Answer 6

Please check this file ".settings/org.eclipse.wst.common.component" under .settings folder which maps to the deployment assembly in the UI.Please check "wb-module" tag and clean up the wb-resource items inside it if present.

This file will be visible in navigator view in eclipse