[GitHub] ignite pull request #1147: Ignite 1924 2

Github user anton-vinogradov closed the pull request at: https://github.com/apache/ignite/pull/1147 --- 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

[GitHub] ignite pull request #1162: ignite-1.6.10

GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/1162 ignite-1.6.10 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.6.10 Alternatively you can review and apply

[GitHub] ignite pull request #1163: Ignite permission set and builder

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/1163 Ignite permission set and builder You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11588

Welcome message

Hello Ignite Community! My name is Sergej. I want to contribute to Apache Ignite. Thanks!

[jira] [Created] (IGNITE-4089) Hadoop: Add MapR installation instructions to readme.io.

Vladimir Ozerov created IGNITE-4089: --- Summary: Hadoop: Add MapR installation instructions to readme.io. Key: IGNITE-4089 URL: https://issues.apache.org/jira/browse/IGNITE-4089 Project: Ignite

[jira] [Created] (IGNITE-4091) Refactor direct usage of Angular API

Alexey Kuznetsov created IGNITE-4091: Summary: Refactor direct usage of Angular API Key: IGNITE-4091 URL: https://issues.apache.org/jira/browse/IGNITE-4091 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4090) CPP: Make sure Ignite C++ can be compiled with g++ 4.4.7

Igor Sapego created IGNITE-4090: --- Summary: CPP: Make sure Ignite C++ can be compiled with g++ 4.4.7 Key: IGNITE-4090 URL: https://issues.apache.org/jira/browse/IGNITE-4090 Project: Ignite

[GitHub] ignite pull request #1165: IGNITE-4090: Ignite C++ can be now compiled with ...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1165 IGNITE-4090: Ignite C++ can be now compiled with g++ 4.4.7 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4090

Contribute to Ignite

Hi I'm Akshay. I want to contribute to Apache Ignite.

Re: Welcome message

Hi Sergey, Welcome to the Ignite community! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here:

Re: Contribute to Ignite

Hi Akshay, Welcome to the Ignite community! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute

[GitHub] ignite pull request #1166: Ignite security processor test

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/1166 Ignite security processor test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11476 Alternatively

Re: Using WiX for the ASF product.

Igor, In my understanding, it is OK to use any tool, as long as it does not get into Ignite source or binary distributions. Everything in the source code should either be licensed under Apache license or have a friendly license. Given the above, can you please clarify whether using this tool is

Using WiX for the ASF product.

Hello Igniters, Recently I've been working on .msi installer for the ODBC driver [1]. I've decided to use WiX toolset [2] for this task. However, I'm not quite sure if it's OK from the legal standpoint to use this tool for the Apache product. What we are going to distribute is two XML files