Re: Ignite Maven project version number

Not sure about the original reason to fix version of parent POM. However the approach you proposed has one drawback comparing to ${app.version} approach. We again need to copy-paste new parent version number into all module POMs when start working on the next version. Here is more details: 1) Ea

Re: Ignite Maven project version number

On Wed, Aug 17, 2016 at 11:14 PM, Igor Rudyak wrote: > It's not the solution in this case, cause parent version is always "1" > What's the reason we've chosen to handle the hierarchy differently to most other projects out there? ​Have we considered versioning the parent POM? Doesn't a fixed 1 im

Re: Ignite Maven project version number

Raul, It's not the solution in this case, cause parent version is always "1" Igor On Wed, Aug 17, 2016 at 3:04 PM, Raul Kripalani wrote: > Igor, > > To my knowledge, you can just remove the version tag altogether, and the > module will inherit the version from the parent. > > Cheers. > > --- >

Re: Ignite Maven project version number

Igor, You need to make a pull-request and choose the pull-request’s number as a branch name from TeamCity’s drop down list. Refer to this [1] section for more guidance. [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-1.CreateGitHubpull-request — Denis

Re: Ignite Maven project version number

Igor, To my knowledge, you can just remove the version tag altogether, and the module will inherit the version from the parent. Cheers. --- Raúl Kripalani linkedin.com/in/raulkripalani | evosent.com | blog: raul.io

Re: Ignite Maven project version number

Anton, If I'll hit "Run" button in TeamCity on the right from "Run All" task, what git branch it will actually use? How can I specify "ignite-3701" branch from my GitHub repository to be used when running this build configuration in TeamCity? Igor On Wed, Aug 17, 2016 at 3:05 AM, Anton Vinogra

[GitHub] ignite pull request #966: Ignite 3698: ODBC: LEN(string) function implemente...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/966 Ignite 3698: ODBC: LEN(string) function implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3698 Alter

Re: Contribution merged: IGNITE-3263 (Affinity function must check for null keys)

Thank you Denis !!! Regards Saikat On Wed, Aug 17, 2016 at 4:55 AM, Denis Magda wrote: > Saikat, > > Thanks a lot for keep making Apache Ignite better. I’ve just merged you > recent improvements > https://issues.apache.org/jira/browse/IGNITE-3263 > > Regards, > Denis > >

[GitHub] ignite pull request #965: IGNITE-2943 .NET: Fix cache store error propagatio...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/965 IGNITE-2943 .NET: Fix cache store error propagation You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2943 Alternatively yo

[GitHub] ignite pull request #964: Ignite-2968-3

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/964 Ignite-2968-3 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2968-3 Alternatively you can review and apply these c

[jira] [Created] (IGNITE-3706) Web Consloe: add query duration on SQL screen

Alexey Kuznetsov created IGNITE-3706: Summary: Web Consloe: add query duration on SQL screen Key: IGNITE-3706 URL: https://issues.apache.org/jira/browse/IGNITE-3706 Project: Ignite Issue

[jira] [Created] (IGNITE-3705) Warnings when build ignite and ignite-example cpp projects with Visual Studio 2015 (v140) toolset

Ksenia Rybakova created IGNITE-3705: --- Summary: Warnings when build ignite and ignite-example cpp projects with Visual Studio 2015 (v140) toolset Key: IGNITE-3705 URL: https://issues.apache.org/jira/browse/IGNITE

[GitHub] ignite pull request #963: IGNITE-3279 .NET: NLog integration

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/963 IGNITE-3279 .NET: NLog integration You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3279 Alternatively you can review

Re: Ignite Maven project version number

Igor, Pease check it at TeamCity, use Run All task. On Wed, Aug 17, 2016 at 4:30 AM, Igor Rudyak wrote: > Ok, created a pull request for this: > https://github.com/apache/ignite/pull/961 > > Igor > > On Tue, Aug 16, 2016 at 3:12 PM, Igor Rudyak wrote: > > > Ok, I created a ticket: https://issue

[jira] [Created] (IGNITE-3704) .NET: Serialization micro-optimizations

Pavel Tupitsyn created IGNITE-3704: -- Summary: .NET: Serialization micro-optimizations Key: IGNITE-3704 URL: https://issues.apache.org/jira/browse/IGNITE-3704 Project: Ignite Issue Type: Impr

[jira] [Created] (IGNITE-3703) IgniteContext Logging class not found.

Giljae Joo created IGNITE-3703: -- Summary: IgniteContext Logging class not found. Key: IGNITE-3703 URL: https://issues.apache.org/jira/browse/IGNITE-3703 Project: Ignite Issue Type: Wish

[GitHub] ignite pull request #962: IGNITE-3700 Fix behaviour of writeAll/deleteAll to...

GitHub user krosenvold opened a pull request: https://github.com/apache/ignite/pull/962 IGNITE-3700 Fix behaviour of writeAll/deleteAll to comply with contract This fixes #962 You can merge this pull request into a Git repository by running: $ git pull https://github.com/krosen