Geek Answers Handbook

Eclipse problem: project link itself

I have a small project consisting of one maven project and two maven modules. One of the modules is webapp, and I use WTP to run all my web applications. Everything was fine until today, when webapp began to refuse compilation, citing:

Project 'sdx.client' cannot reference itself

If I remove the following line from .classpath :

 <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>

my project is compiling again. From googling, I believe that this is a WTP element, but I'm not quite sure what it does and why it believes that it contains a reflexive link to the project containing it. Suggestions on where to look to find the source of the problem will be very welcome.

Update

I did not solve the problem, but all my symptoms disappeared, deleting the project and checking it again from svn. So this seems like a mistake, but I don’t know where to report it or how to propose a decision procedure to determine when it has been fixed.

+6
eclipse eclipse-wtp
source share
2 answers

At the beginning of this year, there is a discussion in dev-eclipse: http://dev.eclipse.org/newslists/news.eclipse.webtools/msg18400.html which suggests that this may be a mistake.

-3
source share

I had the same problem and I found a way to fix it through the .classpath file in my project: This entry caused the problem:

 <classpathentry kind="lib" path="C:/....jar"> <attributes> <attribute name="javadoc_location" value="jar:file:/C:/....jar!/"/> </attributes> </classpathentry>

Comparing with the previous version, it turned out that the next line did not disappear after the attribute <attribute name = ...> line. Adding it again made the problem go away:

 <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>

I don’t know how to explain it, but maybe it helps someone.

0
source share

More articles:


All Articles