Community
Participate
Working Groups
Our 4.1 SDK builds have dropped in size between I20110511-2200 and I20110512-2200. ex: 182732224 eclipse-SDK-I20110511-2200-linux-gtk-x86_64.tar.gz 153611492 eclipse-SDK-I20110512-2200-linux-gtk-x86_64.tar.gz for a total of about 27 Meg. A brief scan of the 2 plugins directories wasn't able to shed light on what has changed. PW
Isn't a smaller size better? ;) The ISV javadoc is missing...
Created attachment 195779 [details] log file Attached log file shows the errors, the doc build is failing because it is trying to access files from other plugins which don't exist in the build because we are reconsuming binary versions of those plugins instead of building them again.
Can something be done to platform.doc.isv/buildDoc.xml to copy most of the required content from a binary org.eclipse.platform.doc.isv_3.7.0.* and then generate javadoc for only the plugins that are being compiled in 4.1?
Created attachment 195787 [details] patch Patch copies content from the 3.x binary doc.isv. Requires testing.
Created attachment 196008 [details] updated patch
I have released this change to the R4_HEAD stream and a test build is in progress. However, an open problem remains for the version of the doc.isv bundle. Since we are now taking content from the 3.7 version of the bundle, the tag on the 4.1 version in cvs is no longer sufficient as a qualifier if the 3.7 content has changed more recently. Here, we probably need to use which ever qualifier between 3.7 vs 4.1 is most recent.
(In reply to comment #6) > Since we are now taking content from the 3.7 version of the bundle, the tag on > the 4.1 version in cvs is no longer sufficient as a qualifier if the 3.7 > content has changed more recently. This will cause a comparator failure, but I don't know if we're even running the comparator in the 4.1 build. Longer term we will need another solution since the current setup does not allow the 4.1 doc to publish any new API javadoc.
Andrew fixed this.
