Further cleanup of remnants of old javadoc build style

Author: akurtakov

eclipse.platform.releng.tychoeclipsebuilder/eclipse-junit-tests/pom.xml

@@ -27,15 +27,6 @@
 
   <properties>
     <timestamp>${buildTimestamp}</timestamp>
-    <!--
-       Compare these doc locations with similar code in
-       ...tychoeclipsebuilder/eclipse/helper.xml around line 275
-       We don't, use ${env.AGGR_DIR} as we do there, in that post-production-build step,
-       since that'd make "local builds" harder for casual users.
-       Caution: using relative directories like can be fragile. There might be
-       a better way?
-    -->
-    <platform.doc.isv.javadoc>../../eclipse.platform.common/bundles/org.eclipse.platform.doc.isv/target/doc.bin.log</platform.doc.isv.javadoc>
   </properties>
 
   <!--

eclipse.platform.releng.tychoeclipsebuilder/eclipse/helper.xml

@@ -39,23 +39,7 @@
 
     <antcall target="generateEclipseIndex" />
 
-    <!--copy javadoc logs -->
     <echo message="DEBUG: BUILD_FAILED: env.BUILD_FAILED: ${env.BUILD_FAILED}" />
-    <!--copy javadoc logs: we use failonerror=false and quiet=true since if "build failed"
-      this files likely do not exist, and quiet=false (default) results in warnings being
-      logged to error log. This can be more distracting, than constructive. And, if the
-      files can not be created, for some reason, then that will cause a failure during main part of build.
-    -->
-    <copy
-      file="${AGGR_DIR}/eclipse.platform.common/bundles/org.eclipse.jdt.doc.isv/target/jdtconvert.txt"
-      tofile="${buildDirectory}/compilelogs/jdt.doc.isv.schema.txt"
-      failonerror="false"
-      quiet="true" />
-    <copy
-      file="${AGGR_DIR}/eclipse.platform.common/bundles/org.eclipse.pde.doc.user/target/pdeconvert.txt"
-      tofile="${buildDirectory}/compilelogs/pde.doc.user.schema.txt"
-      failonerror="false"
-      quiet="true" />
     <echo message="[DEBUG] Eclipse helper.xml publish ending normally" />
   </target>