Roo 1.1.4 is non-backward compatible with 1.1.2

[eruiz]

Hi guys,

We, 3rd party add-ons developers, have a serious problem: our 1.1 compatible add-ons don't work in Spring Roo 1.1.4.

We commented about that in https://jira.springsource.org/browse/ROO-2092 , but currently there isn't any solution for this issue. Latest changes reported in https://jira.springsource.org/browse/ROO-2358 caused that some 3rd party add-ons published in RooBot won't work in Spring Roo 1.1.4.

For example, I tried to install the add-on "org.gvnix.web.menu.roo.addon" and it didn't work due to the removed "listeners" package:

~.web roo> addon install bundle --bundleSymbolicName org.gvnix.web.menu.roo.addon
Unsatisfied requirement(s):
---------------------------
   (&(package=org.springframework.roo.project.listeners)(version>=1.1.0)(!(version>=2.0.0)))
      gvNIX - Spring Roo - Addon - Web MVC Menu

Unable to install add-on: gvNIX - Spring Roo - Addon - Web MVC Menu [version: 0.6.0]

These changes make the maintenance of 3rd party add-ons harder. Please guys, we need a maintenance guide or a deprecation policy.

Cheers

[Alan Stewart]

Apart from having the presence of the listener package, are you using the listeners and relying on notifications?

Alan

[eruiz]

Hi Alan, yes we use it to monitor project dependencies.

Anyway, I think this isn't the matter, the issue is that we developed 3rd parties add-ons, we spend a lot of time to migrate them to Roo 1.1.2 and now in Roo 1.1.4 some of these add-ons don't work.

We are trying to collaborate with Roo but without a deprecation policy or maintenance guide, it is a really hard work.

I have known Spring projects since Springframework 1.0 and this is the 1st time I have seen this issue. I want believe you have a good reason to do that, but please take us in account.

Thanks.

[Alan Stewart]

I reinstated them - sorry for the inconvenience

[eruiz]

Alan, thank you so much.

[eruiz]

Alan, I was thinking about this issue and I think a deprecation policy is needed.

I think Roo should take the Springframework way. For example, look how Springframework 2.5 inform developers about deprecated code: http://static.springsource.org/sprin...ated-list.html , http://static.springsource.org/sprin...ated-list.html

Springframework has been working in this way since 1.0. I am convinced that this is one of the keys for its success.

Please, Alan, Roo team, consider the possibility to work with deprecated code list.

Thanks.

[MiB]

I concur. We all need to take great care of add-on developers. I feel they are very valuable for the possibilities to use Roo for real stuff.