Community
Participate
Working Groups
Many OCL plugins contain package.html files that have been copied from src/ to bin/ by the Java builder. This not only adds no value and increases the jar size, it also confuses dependend JavaDoc generations (JavaDoc builds that refer to OCL and have OCL in their classpath). Here's an example from my build: [javadoc] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ocl" [javadoc] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ocl.ecore" [javadoc] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ocl.expressions" [javadoc] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ocl.helper" [javadoc] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ocl.types" [javadoc] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ocl.util" This can be solved by opening the project properties dialog, select the Java Compiler/Building category, enabling project specific settings and adding "doc-files/,package.html" to Filtered resources.
The plugins affected by this issue are: org.eclipse.ocl org.eclipse.ocl.ecore org.eclipse.ocl.uml I've added the suggested project settings to those projects. I'll seize the opportunity to check the javadoc management with the new Core - Tools releng layout. Cheers, Adolfo.
After fixing this Bug 366853 I may verify that javadoc creation is working fine and no package.html is included in the generated binary jar [1]. Changes pushed to master. commit 08a2518ba18b852b79f3cd8f33e3f648b18f68f4 Resolving as fixed. [1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-tools-3.2-master/89/artifact/MDT-OCL.p2.repository/plugins/org.eclipse.ocl_3.2.0.v20111215-1240.jar Cheers, Adolfo.
CLOSED after a year in the RESOLVED state.
