Community
Participate
Working Groups
Install eclipse-platform-3.3M6 and start it. Help > Software Updates > Find and Install > Search for new features Select Eclipse Project 3.3milestones update site --> PDE and PDE Sources are not available in 3.3M6 version (The 3.3M4 version is there but this does not help) Workaround: Install eclipse-SDK. But I dont want ISV docs, only PDE in order to get the PDE Errorlog. I guess that since eclipse-SDK is there, the features and plugins are on the 3.3milestones site, they are only missing from site.xml I propose to fix this even though 3.3m6 is already past, since this may be relevant for Europa M6.
I think this is a problem with the generated qualifiers - will investigate. bash-3.00$ pwd /builds/transfer/files/updates/3.3milestones/features bash-3.00$ ls -l *pde* -rw-r--r-- 1 sdimitro ottawa 27760 Mar 27 16:18 org.eclipse.pde_3.3.0.v20061114-0800-7M7M-6NUEF6EbRV6EWGC.jar -rw-r--r-- 1 sdimitro ottawa 25045 Mar 27 16:18 org.eclipse.pde_3.3.0.v20061114-0800-7M7M-6NUEF6EbRV6EWGC.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 27748 Dec 15 17:17 org.eclipse.pde_3.3.0.v20061114-0800-87cMN7UcTc-JRPJ.jar -rw-r--r-- 1 sdimitro ottawa 25036 Dec 15 17:17 org.eclipse.pde_3.3.0.v20061114-0800-87cMN7UcTc-JRPJ.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 27748 Feb 23 14:29 org.eclipse.pde_3.3.0.v20061114-080-87cMNDNcOD-KLPM.jar -rw-r--r-- 1 sdimitro ottawa 25036 Feb 23 14:29 org.eclipse.pde_3.3.0.v20061114-080-87cMNDNcOD-KLPM.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 28272 Mar 27 16:18 org.eclipse.pde.source_3.3.0.v20061114-0800-7M7M-6NUEF6EbRV6EWGC.jar -rw-r--r-- 1 sdimitro ottawa 25411 Mar 27 16:18 org.eclipse.pde.source_3.3.0.v20061114-0800-7M7M-6NUEF6EbRV6EWGC.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 28266 Dec 15 17:17 org.eclipse.pde.source_3.3.0.v20061114-0800-87cMN7UcTc-JRPJ.jar -rw-r--r-- 1 sdimitro ottawa 25402 Dec 15 17:17 org.eclipse.pde.source_3.3.0.v20061114-0800-87cMN7UcTc-JRPJ.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 28265 Feb 23 14:29 org.eclipse.pde.source_3.3.0.v20061114-080-87cMNDNcOD-KLPM.jar -rw-r--r-- 1 sdimitro ottawa 25403 Feb 23 14:29 org.eclipse.pde.source_3.3.0.v20061114-080-87cMNDNcOD-KLPM.jar.pack.gz
*** Bug 175281 has been marked as a duplicate of this bug. ***
Also examples has a problem, see bash-3.00$ ls -l *examples* -rw-r--r-- 1 sdimitro ottawa 28005 Dec 15 17:17 org.eclipse.sdk.examples_3.1.100.v20060612-cwSLaYgpn-SqNOT.jar -rw-r--r-- 1 sdimitro ottawa 25282 Dec 15 17:17 org.eclipse.sdk.examples_3.1.100.v20060612-cwSLaYgpn-SqNOT.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 28007 Feb 23 14:29 org.eclipse.sdk.examples_3.1.100.v2006061-IcwSLooWmx-R6NM.jar -rw-r--r-- 1 sdimitro ottawa 25288 Feb 23 14:29 org.eclipse.sdk.examples_3.1.100.v2006061-IcwSLooWmx-R6NM.jar.pack.gz -rw-r--r-- 1 sdimitro ottawa 28014 Mar 27 16:18 org.eclipse.sdk.examples_3.1.100.v20070318-807QEN-DWU2z0KwAe77HYJE.jar
I think you are right! They are all there, but the M6 version has qualifier 7M7M... which is the lowest of all. So, if I have "show latest version of a feature only" I'm getting the M4 version (87cm...) which is considered higher than the M5 version (-...) It's funny that it's an issue for the PDE feature only, and all other features seem to have re-released their feature thus changing the CVS tag. Changing the CVS tag for PDE too would be the right solution here... but since M6 is already released this is probably out of scope. So the user's workaround is to disable "show latest version only". The other workaround is to get rid of the M4 and M5 features from the site.
I think examples is good because the M6 cvs tag is the highest: v20070318 > all others
Actually, knowing more now I don't think this is relevant for Europa since Europa will copy the M6 bits only to its own site so the older bits won't interfere.
Right, we don't really advise people to use our milestone update site and it's not listed in our features. I just use it to store our updates that are submitted to Europa. We run a comparison tool in our builds that compares the versions of the plugins and features in the previous release with the current I-build. However, we don't compare it with the previous milestone because there has been so many changes with generated qualifiers. I'll close this bug as wont fix.
(In reply to comment #7) > However, we don't compare it with the previous milestone because there has been > so many changes with generated qualifiers. I'll close this bug as wont fix. If you don't use milestones older than 3.3M6 why not just remove them from the 3.3milestones site, or at least remove them from the site.xml file? This would fix the issue.
reopening
Removed milestones < M6 from the site.xml and regenerated digest.
