Community
Participate
Working Groups
I've found several problems [1] when producing javadoc in the Core build. However, this could make sense since the javadoc ant script tries to build javadoc for all the project[2], and the Core build doesn't have the proper target platform for all the project. I have to try to generate the javadoc in the Tools build. [1] master/workspace/org.eclipse.ocl.git/examples/org.eclipse.ocl.examples.impactanalyzer.util/src/org/eclipse/ocl/examples/impactanalyzer/util/OCLFactory.java:55: warning - Tag @link: can't find newInstance(org.eclipse.ocl.EnvironmentFactory) in org.eclipse.ocl.examples.impactanalyzer.util.OCL [ant] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast to com.sun.javadoc.AnnotationTypeDoc [ant] at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46) [ant] at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811) [ant] at com.sun.tools.doclets.formats.html.SubWriterHolderWriter.printIndexComment(SubWriterHolderWriter.java:101) [ant] at com.sun.tools.doclets.formats.html.SubWriterHolderWriter.printSummaryLinkComment(SubWriterHolderWriter.java:137) [2] <property name="pluginsSourcesLocation" value="${checkoutLocation}/org.eclipse.ocl.git/plugins/" /> <property name="examplesSourcesLocation" value="${checkoutLocation}/org.eclipse.ocl.git/examples/" />
Indeed, the javadoc must be managed in the Tools job. Removing unnecessary manage-javadoc parameter from the Core job, plus other minor changes in the scripts. Changes pushed to master. commit 44334b43908b58d82a18fef59bfe844f407f5fa8 Resolving as fixed. P.S: Commit IDs are linked in the mylyn tasks !!! The integration git-mylyn integration is probably needed. Regards, Adolfo.
CLOSED after a year in the RESOLVED state.
