problems with keeping uptodate with 5.1-EAP

And why has the signature of the constructor of DefaultJ2EEServerEvent
been changed? This IS part of OpenApi, and there's no reason for not
leaving the old constructor, possibly by marking it deprecated... :-(((

Yann Cebron wrote:

why are ReferenceProvidersRegistry.PATH_REFERENCES_PROVIDER
and friends now private? it would be really nice if I don't have to develop 2 versions of my plugin, given the difference between 5.0.x and 5.1 is only a point release :-(((

yes I know it's not part of OpenApi, but until Demetra there will be no other possibility..

--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

Fixed in next build.

Yann Cebron wrote:

why are ReferenceProvidersRegistry.PATH_REFERENCES_PROVIDER
and friends now private? it would be really nice if I don't have to develop 2 versions of my plugin, given the difference between 5.0.x and 5.1 is only a point release :-(((

yes I know it's not part of OpenApi, but until Demetra there will be no other possibility..

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

And why has the signature of the constructor of DefaultJ2EEServerEvent

This one is also fixed in next build.


-

Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Thanks! :)

Maxim Shafirov (JetBrains) wrote:
>> And why has the signature of the constructor of DefaultJ2EEServerEvent

This one is also fixed in next build.


------------------
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

apparently not in 4055 :(

sorry, I meant PROPERTY_FILE_PROVIDER which changed to
PROPERTIES_FILE_PROVIDER..

nevermind, it seems plugin authors must watch and test each and every single build separately :(