[GitHub] ignite pull request: IGNITE-1467: Standalone node application

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

[GitHub] ignite pull request: IGNITE-1467: Standalone node application

andrey-kuznetsov
GitHub user isapego opened a pull request:

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

    IGNITE-1467: Standalone node application

   

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

    $ git pull https://github.com/isapego/ignite ignite-1467

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

    https://github.com/apache/ignite/pull/142.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 #142
   
----
commit 52728ecc9c39d32880ba4ae178e21eb60f0416cf
Author: isapego <[hidden email]>
Date:   2015-10-07T14:02:08Z

    IGNITE-1467: Application stub. Can only be compiled for Windows now.

commit 4aa76b8a2b0450c8dc67c7fc72bb37bb282f7fb5
Author: Igor Sapego <[hidden email]>
Date:   2015-10-07T14:30:33Z

    Support for the autotools build system added.

commit 073e17704d78ae736e081aebe7ad796c6d0d55d0
Author: isapego <[hidden email]>
Date:   2015-10-08T08:06:06Z

    Internal DestroyJvm method added to be used in stand alone application

----


---
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 #142: IGNITE-1467: Standalone node application

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

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


---
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.
---