ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3701) Ignite Maven project version number
Date Wed, 17 Aug 2016 01:32:23 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423728#comment-15423728

ASF GitHub Bot commented on IGNITE-3701:

GitHub user irudyak reopened a pull request:


    IGNITE-3701 Ignite Maven project version number


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

    $ git pull https://github.com/irudyak/ignite ignite-3701

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


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #961
commit 90af6ebc3b71add0326a52a8b426febd0441f45f
Author: Igor <irudyak@gmail.com>
Date:   2016-08-17T01:26:47Z



> Ignite Maven project version number
> -----------------------------------
>                 Key: IGNITE-3701
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3701
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Igor Rudyak
>            Assignee: Igor Rudyak
> Each time after publishing new Ignite release and switching to development of next version,
version numbers are copy-pasted in all module POMs. It's better just to define project version
variable in one place to reuse it in module POMs.
> For example, variable like ${app.version} could be defined in parent POM and all module
POMs can just reuse it like this:
>     <artifactId>my-module</artifactId>
>     <version>${app.version}</version>

This message was sent by Atlassian JIRA

View raw message