ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Rudyak <irud...@gmail.com>
Subject Re: Ignite Maven project version number
Date Wed, 17 Aug 2016 22:14:35 GMT
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 <raul@evosent.com> wrote:

> 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
> <http://evosent.com/?utm_source=email&utm_medium=email&
> utm_campaign=evosent_raul>
> | blog: raul.io
> <http://raul.io?utm_source=email&utm_medium=email&utm_
> campaign=evosent_raul> |
> skype: raul.fuse
>
> On Wed, Aug 17, 2016 at 2:30 AM, Igor Rudyak <irudyak@gmail.com> 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 <irudyak@gmail.com> wrote:
> >
> > > Ok, I created a ticket: https://issues.apache.org/
> > jira/browse/IGNITE-3701
> > >
> > > Igor
> > >
> > > On Tue, Aug 16, 2016 at 8:34 AM, Igor Rudyak <irudyak@gmail.com>
> wrote:
> > >
> > >> Ok, I'll create a ticket and implement it.
> > >>
> > >> Igor
> > >>
> > >> On Tue, Aug 16, 2016 at 12:46 AM, Anton Vinogradov <
> > >> avinogradov@gridgain.com> wrote:
> > >>
> > >>> Hi All,
> > >>>
> > >>> We used this approach 1.5 years before, but had some problems with
> > >>> assemblying and deploying.
> > >>> I can't remember what type of problem it was, possible they are
> already
> > >>> solved.
> > >>>
> > >>> I think we should refactor master branch as Igor described and check
> it
> > >>> works.
> > >>>
> > >>> Igor,
> > >>> could you please implement it, check assemblying works (Ignite Fabric
> > >>> Maven
> > >>> Build Instructions section at DEVNOTES.txt) and create pullrequest?
> > >>>
> > >>>
> > >>> On Mon, Aug 15, 2016 at 8:46 PM, Denis Magda <dmagda@gridgain.com>
> > >>> wrote:
> > >>>
> > >>> > Anton, would you mind providing your thoughts on this.
> > >>> >
> > >>> > —
> > >>> > Denis
> > >>> >
> > >>> > > On Aug 12, 2016, at 6:02 PM, Igor Rudyak <irudyak@gmail.com>
> > wrote:
> > >>> > >
> > >>> > > Guys,
> > >>> > >
> > >>> > > Found that each time after publishing new Ignite release
and
> > >>> switching to
> > >>> > > development of next version, version numbers are copy-pasted
in
> all
> > >>> > module
> > >>> > > POMs. Isn't it better just to define project version variable
in
> > one
> > >>> > > place(and change it 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>*
> > >>> > >
> > >>> > > Igor
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message