Plugin update center doesn't provide the newest verified plugins
* Download the verified plugin from http://plugins.netbeans.org/plugin/47589/additional-hints and you get version 1.0.1 -> OK
* Download the same verified plugin from http://plugins.netbeans.org/nbpluginportal/updates/7.3/catalog.xml.gz and you'll get the old version 1.0.0 (not 1.0.1) -> NOK
IMHO all the catalogs have to be rebuild. At best nightly in a CI-Build.
Honzo, can you please investigate what's wrong here? I have verified what Benno said. It's really strange that PP offers version 1.0.1 while PPUC still refers to version 1.0.0. Plugin log shows that Benno uploaded version 1.0.1 on 2013-03-23 18:51:12 and the second Go vote came on 2013-03-31 11:57:02. The core question is why the catalog was not regenerated? Its timestamp is 09/03/04/18/3/2013. BTW, the same happened to 7.2 PPUC.
This is a candidate for Plugin Portal 2.2.
Other plugins are not also updated.
For example,  and  are not displayed on plugins list.  is
displayed old version. (These status is "PASSED")
Increasing priority due to more people complaining. Honzo, can you please take a look at this?
BTW, it is not even possible to re-generate the update center manually. So this basically means that content of the Plugin Portal Update Center is now static since March 18th, 2013. Increasing priority to P1. This is an obvious showstopper.
issue is that generated catalog fails validation against it's DTD which is after the migration unavailable!
https://netbeans.org/dtds/autoupdate-catalog-2_6.dtd -> 404 page not found
I will work with kenai team on resolution.
until missing DTD is resolved I will disable catalog validation against it and I will regenerate all catalogs
Thanks Honzo. This temporary solution will help a lot!
We can update to new version of plugins now.
I hope that this is resolved successfully.
Thanks a lot!
Unfortunately not fully. Module catalogs must pass validation against the DTD file which is now turned off. When the access is renewed and the check is back this issue can be finally resolved as fixed.
this is now fixed for real, catalog DTD is in place and validation works again...
Excellent work Honzo. Thanks a lot!
Thanks a lot!