> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I value strict compatibility rules very highly, and would be
> > > happy
> > > > if
> > > > > > we
>
> in a minor release.
> > > > > > > Unfortunately, Ignite is far from that place for now. We don’t
> > have
> > > > any
> > > > > > > distinction between API and internal classes, don’t have
> > > > > > > p
don’t have
> > > > > > plugin-only APIs, etc. All classes are public, everything is
> > > accessible
> > > > > to
> > > > > > user code. We even refer to internal classes in public Javadoc
> > > > > > (e.g. I recall
d there).
> > > > > Considering this, moving CommandHandler from ignite-core to
> > > > > ignite-control-utility
> > > > > doesn't look that bad. It doesn’t differ to much from any other
> > change
> > > > > that
ing this, moving CommandHandler from ignite-core to
> > > > ignite-control-utility
> > > > doesn't look that bad. It doesn’t differ to much from any other
> change
> > > > that removes or renames a class.
> > > > There could be required changes with a
doesn’t differ to much from any other change
> > > that removes or renames a class.
> > > There could be required changes with a higher compatibility impact but
> I
> > > don’t see them after a superficial glance.
> > >
> > > Stan
> > >
> >
required changes with a higher compatibility impact but I
> > don’t see them after a superficial glance.
> >
> > Stan
> >
> > From: Sergey Antonov
> > Sent: 23 января 2019 г. 19:15
> > To: dev@ignite.apache.org
> > Subject: Re: [DISCUSSION] Control.sh glo
; From: Sergey Antonov
> Sent: 23 января 2019 г. 19:15
> To: dev@ignite.apache.org
> Subject: Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0
>
> Stan, thank you for response!
>
> I my view we shouldn't make incompatible changes and switch extendable
> classes (i.e.
Subject: Re: [DISCUSSION] Control.sh global rework in apache ignite 3.0
Stan, thank you for response!
I my view we shouldn't make incompatible changes and switch extendable
classes (i.e. VisorDataTransferObject -> IgniteDataTransferObject) between
minor releases. Therefore we couldn't rework util
es are
> internal and unlikely to be used in the wild.
> On paper it’s an incompatible change, of course, but I think in this case
> it’s fine.
>
> My 2 cents,
> Stan
>
> From: Sergey Antonov
> Sent: 23 января 2019 г. 17:10
> To: dev@ignite.apache.org
> Subject: [DISC
in the wild.
On paper it’s an incompatible change, of course, but I think in this case it’s
fine.
My 2 cents,
Stan
From: Sergey Antonov
Sent: 23 января 2019 г. 17:10
To: dev@ignite.apache.org
Subject: [DISCUSSION] Control.sh global rework in apache ignite 3.0
Hello, Igniters!
I think, we should
Hello, Igniters!
I think, we should rework control.sh utility in Apache Ignite 3.0 release.
I made umbrella ticket [1] for it.
For a start we should move utitlity from ignite-core to separate module
[2]. It's enable using 3rd-party libraries, for example commons-cli [3].
Also we should add
12 matches
Mail list logo
