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 <[email protected]> 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 <[email protected]> wrote: > >> Ok, I'll create a ticket and implement it. >> >> Igor >> >> On Tue, Aug 16, 2016 at 12:46 AM, Anton Vinogradov < >> [email protected]> 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 <[email protected]> >>> wrote: >>> >>> > Anton, would you mind providing your thoughts on this. >>> > >>> > — >>> > Denis >>> > >>> > > On Aug 12, 2016, at 6:02 PM, Igor Rudyak <[email protected]> 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 >>> > >>> > >>> >> >> >
