In order to avoid dependency of plugins on a concrete build, Plugin Portal should disable to request verification of plugins who use this kind of dependency in their manifests. Honzo, can you please implement this limitation?
If plugin's module descriptor contains something like this , display this message  under "Request verification".
 <module ..><manifest AutoUpdate-Show-In-Client="true" OpenIDE-Module-Module-Dependencies="org.netbeans.modules.php.api.phpmodule = 201302132200,...>
 Publishing on the NetBeans Plugin Portal Update Center disabled due to hard dependency on a concrete build number.
Honzo, can you please take a look at this? Thanks!
This is a candidate for Plugin Portal 2.2.
Another bug which would not happen if this is implemented.
This applies for example this plugin: http://plugins.netbeans.org/plugin/45919
this is now implemented, any new plugin with such dependency in the info.xml manifest won't be allowed for verification
Great, thanks Honzo.
Information for plugin owners
If you want to have the dependency set correctly please consult this FAQ:
The point is to NOT use build numbers but module specification versions instead. Here is an example:
1. My plugin depends on org.netbeans.modules.php.api.phpmodule so I must find out its module specification version.
2. Let's say I have NetBeans sources cloned in ~/sources/netbeans directory.
3. cd ~/sources/netbeans/php.api.phpmodule
4. cat manifest.mf
5. I must modify info.xml of my plugin to contain the following statement:
OpenIDE-Module-Module-Dependencies="org.netbeans.modules.php.api.phpmodule > 2.19"
If I use specification, I can't even compile
If I use <version>RELEASE82</version>, I can compile, but can't be verify for plugins central :
Plugin has hard dependency to other modules defined in info.xml module descriptor, therefore can't be subject of verification. For more information see issue #226906
PLEASE HELP, THANKS