[jeffhoran]

ERROR: org.apache.taglibs cannot be resolved or is not a type

This error seems to be occuring on laptops and not on desktops. This error shows on a project that 2 people in my group experience on their laptops running xp os and both version 2 an 3 of eclipse and myeclipse. We are using putty to tunnel to our cvs server. We can build and deploy with ant scripts just fine with no errors. However, these errors appear in our jsp pages where custom taglibs are being used. Those libs are jarred and included in the project build path.

[jeffhoran]

Follow up: These errors appear due to the build process or settings inherent in myeclipse.

[Riyad Kalla]

Jeff,
The org.apache.taglibs package is from the Jakarta Commons Taglib subproject isn’t it? Do these developers include the necessary JAR file containing those taglib implementations in their buildpath?

[jeffhoran]

Thanks for your reply. All libs are installed in the project and work on the desktop. On the notebook, an ant build compiles and deploys without error. Myeclipse provides the errors on their compile of the jsps.

The installed java compiler used on both is: j2sdk1.4.2_04

I hope that helps.

[Riyad Kalla]

Let me clarify:

1) What JAR file provides the org.apache.taglibs package?
2) What is the Java Build Path > Libraries (tab) set to on the laptops?

You are basically getting a class not found problem, and I’m trying to nail down exactly which JAR file provides this class, so we can fix up your classpath settings.

[ingesol]

I solved this issue by adding standard.jar (jakarta taglibs) to the project classpath. This hasn’t been necessary before, but when upgrading to eclipse 3.0 final with 3.8 beta 2, it was broken.

[Author]

Posts