It appears that ejbjar ignores any child classpath elements.  Has anyone
else experienced this problem?

I am getting the awful "check super class" warnings with ejbjar when using a
nested classpath element.  If I move the relevant jars to my system
classpath, all is well.  Anyone know what the deal is?

Thanks,

Paul

Reply via email to