> Thanks Mark.
>
> BTW, to cleanup some stale information, you can try to close your
> projects, open them again, then refresh and clean.
>
> regards,
> Eugene
Eugene,
That doesn't seem to help in this case, although I've used that trick
in the past. I did some more digging around. It seems that the key
difference is that the working project (picks up the dependency) is a
regular Java/JAR project, while the non-working project (missing the
dependency) is a WAR project with the WST voodoo enabled.
The issue is somehow related to the following lines from the .project file:
<nature>org.eclipse.wst.common.project.facet.core.nature</nature>
<nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
If I delete these two lines, the project dependency is picked up.
With them present it is missing. I'm going to see if I can replicate
this with some sample projects, and if so I'll file a bug report -
unless this sounds like an already known issue.
Thanks,
Mark
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
