[karnokd]

I’m using MyEclipse 6.0.1 with Eclipse 3.3.1 M20071023-1652, and when I create a new J2EE project and run the Generate Javadoc command from Projects menu, the javadoc gives warning about missing classes, typically from javax.servlet.jar:

************************************\utils\CharsetFilter.java:17: package
javax.servlet does not exist
import javax.servlet.ServletResponse;
                    ^

The project compiles perfectly, but it seems, that the jar files from custom Library com.genuitec.eclipse.j2eedt.core.J2EE14_CONTAINER is somehow not included in the classpath of the javadoc.exe.

When I manually create an user library with the very same jar files, it gets included and javadoc.exe runs without problems.

Could be, that there is some installation/registration problem with this J2EE14_CONTAINER library which prevents it from being included in the javadoc.exe’s classpath?

[Riyad Kalla]

The J2EE14_CONTAINER and the other MyEclipse containers are custom classpath containers that we provide that support enhanced abilities over standard classpath containers. They are *custom* though, so the integrated Eclipse/Ant/Javadoc support doesn’t know how to translate them into classpath entries for the Javadoc generation step. Creating the User Library with the same contents is one workaround, however you might run into problems with deploying your project; it might deployed those server classes with your project which should not happen.

You might try and add the appropriate classpath references manually in the generate Ant file to work around it.

[sntechnik]

I ran into a similar problem, but am not sure, that i understand your answer?

In my case, i tried to use javax.mail.*, which is part of J2EE.

On the projects’ package-tree is a leaf with “Java EE 5 libraries”, which includes javax.mail.

If i now compile the project, i run into a classNotFoundExceptopn for the javax.mail.* classes.

Is it the same problem?

If yes, could you please be so kind to tell me in simpler words, what i’ll have to do to solve this? I never used ant directly before.. 🙁

Kind regards, Florian

[Riyad Kalla]

Florian,

The basic problem is that Ant is a command-line based build technology. So when you run it, what happens is a new Java process is spun up from inside the workbench to run that build script.

Ant isn’t aware of the Eclipse environment and isn’t aware of all your project settings… it’s just running.

Eclipse *does* provide some basic translation of it’s own project resources to your Ant script when you run that Javadoc task; but in MyEclipse, the build-path libraries like JavaEE5 and J2EE 1.4 libraries and so on, are all custom classpath containers that we ship, which aren’t translated into your Ant script for you automatically.

So you need to manually enter in the references to those JARs in your Ant script and then reference them from your javadoc task (you can check the Ant docs on how to do this).

I’ve attached a screenshot showing an example of the *actual* path of the libs that you will want to enter into your Ant script.

I hope that helps.

Attachments:

You must be logged in to view attached files.

[Author]

Posts