Github user aledsage commented on the pull request:
https://github.com/apache/brooklyn-server/pull/143#issuecomment-220024594
It feels like this should be an override in downstream projects, rather
than in Brooklyn itself. Do you want to close this?
As discussed with @nakomis offline, a longer-term change we want to make
is... instead of a single `deserializingClassRenames.properties`, we'd like to
pick up multiple files so that downstream projects can be additive.
We could have a '/brooklyn/deserializingClassRenames' resource folder. For
any `.properties` file inside that folder (how ever it was added to the
classpath), we'd load it and include it in the renames.
We could also do multiple calls to rename for a given class, until the name
became stable (or an infinite loop was detected!). Then we can have separate
files for 0.7.0->0.8.0, 0.8.0->0.9.0.
Not sure how that would working with OSGi with Karaf @neykov ? What
different configuration mechanism would we use, instead of searching the
classpath?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
