Community
Participate
Working Groups
I have two properties in the ant file <property name="ROOT" value="c:"/> and <property name="SINDBAD_LIB" value="${ROOT}/project/include"/> which produces the following error: "Unbound classpath container: 'C:project/include/gate30/jar' in project sindbad" obviously a slash was deleted, which is quite important to find anything. I have imported the ant file with "Build project from ant file". Cheers and thanks for the other fantastic work.
Thanks for the bug report. Can you provide the original build file used for import?
The problem is not the interpretation of the class path but the created .classpath file. if I import e.g. nutch it creates those lines: <classpathentry kind="lib" path="C:/project/include/nutch05/concurrent-1.3.4.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/nutch-0.5.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/dom4j-1.4.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/jaf-1.0.2.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/jakarta-oro-2.0.7.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/taglibs-i18n.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/xerces-2_6_2.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05/xerces-2_6_2-apis.jar"/> <classpathentry kind="lib" path="C:/project/include/nutch05"/> the last line creates the error as it is obviously unnecessary.
Can you also indicate the Eclipse build Id you are using: Help>About Eclipse SDK>Build id
Build id: I20050617-1618 What I just realised, if I remove it from the classpath, which lets the library dissapear from the .project and re-add it: <classpathentry kind="con" path="C:/project/include/gate30/jar"/> the error is gone. I don't know if the kind="con" was always there, my original post is not a direct copy of the .classpath, the last line was added by hand!!
The last comment is not entirely true, the error re-appears after a few other changes in the project. The same behaviour happened initially when I did not know what the error means. Some changes let the error disappear but at a later stage it was back. Mostly when the ant file was savedv but not exlusively. I could not find any behaviour pattern provocking the error to be there or not. It only disappears when folders are excluded from the classpath, which impedes including un-jared or un-zipped classes.
Still looking for a reproducealbe test case. A buildfile that when imported creates the problem would be great.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
