[jira] [Commented] (STORM-1202) Migrate APIs to org.apache.storm, but try to provide backwards compatability as a bridge

["Robert Joseph Evans (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004112#comment-15004112 ] 

Robert Joseph Evans commented on STORM-1202:
--------------------------------------------

OK so a shim layer is not going to work.  To make it happen I would have to modify the generated thrift code, which really is a non-starter, but thinking about this I think I have a way to still do it.  I should be able to borrow code from the maven shade plugin, and shade the submitted jar to translate backtype.storm -> org.apache.storm and storm.trident -> org.apache.storm.trident.  This code would exist in a separate jar and would be a plugin that could be configured on for those that want it, and off for those that don't.  That way we have a way to support backwards compatibility but can be turned off when you know everyone has upgraded.

> Migrate APIs to org.apache.storm, but try to provide backwards compatability as a bridge
> ----------------------------------------------------------------------------------------
>
>                 Key: STORM-1202
>                 URL: https://issues.apache.org/jira/browse/STORM-1202
>             Project: Apache Storm
>          Issue Type: New Feature
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>
> We want to move the storm classpaths to org.apache.storm wherever possible, but we also want to provide backwards compatibility for user facing APIs whenever possible.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)