Včera 14:26:37 
Hi. 
I've been just talking with Radek about his wizard to create option panel and  
realized that we are exposing an API which is not stable in 5.0. The module  
uses /0 to indicate that and this is going to change to /1[a] or /2[b]. 
 
As a result the code generated using the wizard is not going to work  
correctly[c]  in next version of NetBeans. 
 
I believe that the correct solution would be generate a range dependency on  
core/options/0-1 As a result in next version the module would link  
correctly[d] without any warnings. 
 
Can Radek rewrite its wizard to insert range dependency[e]? 
-jst 
 
 
[a] if there is a compatible change 
[b]  if there is an incompatible one 
[c] either will not work or will work, but print warning messages on startup  
about auto upgrade of module deps 
[d]  assuming the module is going to remain compatible 
[e] is it even possible to have range dependency in project.xml and in  
apisupport infrastructure?