GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/889
STORM-1202: Migrate APIs to org.apache.storm, but try to provide some form
of backwards compatability
This is not a typical pull request, because changing the packages is a huge
task, and keeping it upmerged while this is reviewed and other patches goes in
is a huge task, and error prone.
Instead the actual changes to the package/namespace is done by running
```./dev-tools/move_packages.sh ./```
you can wipe all of the changes clean again (Including any modifications on
your branch that you have not checked in) by running
```./dev-tools/cleanup.sh ./```
once the changes are approved/committed these two scripts should be removed.
The other code is intended to provide a single executable that can shade a
user jar so instead of using `backtype.storm` and `storm.trident` it uses
`org.apache.storm` and `org.apache.storm.trident`.
These are off by default by can be enabled by adding
```
client.jartransformer.class: "org.apache.storm.hack.StormShadeTransformer"
```
to storm.yaml. I would expect all of the code related to this to be
removed when we go to the 2.0 release.
I have tested this by running a 0.10.0-SNAPSHOT storm starter topologies
against a cluster running this patch (along with the move_package.sh executed).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-1202
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/889.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #889
----
commit dab5b0de51a6c83562d18ab8d823f77ff5c4d757
Author: Robert (Bobby) Evans <[email protected]>
Date: 2015-11-13T19:42:13Z
STORM-1202: Migrate APIs to org.apache.storm, but try to provide some form
of backwards compatability
----
---
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.
---
