You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Rudyak (JIRA)" <ji...@apache.org> on 2018/02/05 06:10:00 UTC

[jira] [Resolved] (IGNITE-3701) Ignite Maven project version number

     [ https://issues.apache.org/jira/browse/IGNITE-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Rudyak resolved IGNITE-3701.
---------------------------------
    Resolution: Won't Fix

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)