[GitHub] ignite pull request: GG-11005 - NPE on start sender hub. Fix.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: GG-11005 - NPE on start sender hub. Fix.

andrey-kuznetsov
GitHub user dkarachentsev opened a pull request:

    https://github.com/apache/ignite/pull/600

    GG-11005 - NPE on start sender hub. Fix.

    Changed initialization order of plugins and components. Plugins inited after component, because they depend on components.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11005

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/600.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 #600
   
----
commit 788cdf249ba4e8682f79d21f9edc2c6c9bd4a721
Author: dkarachentsev <[hidden email]>
Date:   2016-04-04T13:10:25Z

    GG-11005 - NPE on start sender hub. Fix.
   
    Changed initialization order of plugins and components. Plugins inited after component, because they depend on components.

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #600: GG-11005 - NPE on start sender hub. Fix.

andrey-kuznetsov
Github user dkarachentsev closed the pull request at:

    https://github.com/apache/ignite/pull/600


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---