You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Clebert Suconic <cl...@gmail.com> on 2019/01/30 16:31:11 UTC

[DISCUSS] ActiveMQ Artemis Native as a separated project

One of the modules of ActiveMQ Artemis is the Native Layer:

https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native

We currently hold all JNI Calls (pretty much libaio ATM).

It is stable and the release cycle is very long. Maybe one or two
changes an year with the current scope. This may become different if
we expand the scope of JNI operations supported by the broker).

I would like to make it a separate git repository from ActiveMQ
Artemis, with its own releasy cycle. (we would even be able to remove
the currently .so that are currently checked in on artemis).  It is
the sensitive thing to do.

I don't think it as a separate project, just as a separate repository
with its own release cycle to make things easier.

I would like to name it ActiveMQ-Native, dropping the word Artemis, as
it would be used for any further JNI operations needed for any other
Java Projects part of ActiveMQ Artemis. We currently only have libaio,
but I would keep the door open for other JNI operations we may need.


I was wondering if anyone have any other ideas around it.


Also: Would we need a vote to proceed on such change after we reach a
consensus on what to do here?
-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
The Project has been already created here. It includes the original
logs from the activemq-artemis folder.

https://github.com/apache/activemq-artemis-native

I will send a separate HEADS up to make a release tomorrow.

On Mon, Feb 25, 2019 at 12:33 PM Clebert Suconic
<cl...@gmail.com> wrote:
>
> As a Heads-UP. We have been separating the history on this repository here:
>
> https://github.com/clebertsuconic/activemq-artemis-native
>
> Which is now ready to go.
>
> so I will go ahead and create the github repository tomorrow. and add
> these bits in there.
> I plan to make a first release soon, so I will be working on providing
> a download page.
>
>
>
> And BTW: I have done some progress on how the natives are compiled.
> There's a script that will create a docker image, and use it to
> generate the binaries. So the only building dependency you will need
> is docker. (kind of cool actually).
>
> you will still be able to build it on your own box if you want... but
> this will make it easier to generate the releases.
>
>
>
> I will send another HEADS-UP for a release as soon as I'm ready.
>
> On Fri, Feb 1, 2019 at 7:38 AM Christopher Shannon
> <ch...@gmail.com> wrote:
> >
> > It makes sense to me to have a separate release cycle for the JNI parts.  I
> > think lazy consensus is fine here and as long no one objects you can just
> > go ahead and create it without a formal vote.
> >
> > On Thu, Jan 31, 2019 at 3:51 PM Clebert Suconic <cl...@gmail.com>
> > wrote:
> >
> > > yep, so far the best name is ActiveMQ-Artemis-native
> > >
> > >
> > > I don't think this is a big deal and I don't intend to create a vote
> > > for this.. as this is regular business. We are creating a separate
> > > repository for the native part, not a project!
> > >
> > > Let me know If you anyone think I'm wrong and this needs a vote please.
> > >
> > > On Thu, Jan 31, 2019 at 1:59 PM Arthur Naseef <ar...@amlinv.com> wrote:
> > > >
> > > > That makes sense then - having a separate repo and release cycle for the
> > > > native JNI library.
> > > >
> > > > Perhaps, as Jeff suggested, ActiveMQ-Artemis-native would be a good name?
> > > >
> > > > Art
> > > >
> > > >
> > > > On Thu, Jan 31, 2019 at 10:04 AM Clebert Suconic <
> > > clebert.suconic@gmail.com>
> > > > wrote:
> > > >
> > > > > forgot to answer another point.
> > > > >
> > > > > Right now it's for posix (Linux) only. but that could change as the
> > > > > project progresses.
> > > > >
> > > > > On Thu, Jan 31, 2019 at 11:51 AM Clebert Suconic
> > > > > <cl...@gmail.com> wrote:
> > > > > >
> > > > > > -- If the library is intended as a holder for "any JNI needed by
> > > > > Artemis,"
> > > > > > then I don't see value in dis-associating it from Artemis.  OTOH, if
> > > the
> > > > > > library has functionality that could be useful to other projects,
> > > outside
> > > > > > of Artemis, then I can see a value to breaking it away from the
> > > Artemis
> > > > > > name and making it more reusable.
> > > > > >
> > > > > >
> > > > > > I thought about the possibility of dis-associating. .but you're
> > > right..
> > > > > it's a bit more complicated... I wouldn't disassociate.
> > > > > >
> > > > > >
> > > > > > >>>>  I don't have a concern either way on that front.  Although I am
> > > > > not sure why it helps to do so.
> > > > > >
> > > > > >
> > > > > > This is a chicken / egg situation. Right now when we build the native
> > > > > layer, we have to commit binary file on the git repository.
> > > > > > I'm intending to fix that part.
> > > > > >
> > > > > > And that makes it difficult to have a real build from source
> > > experience.
> > > > > I have had a few cases where users needed to rebuild it from scratch,
> > > and
> > > > > bumped into this native issue, which I'm trying to improve here.
> > > > > >
> > > > > > The native layer build wouldn't have any .so, and the .so would be
> > > part
> > > > > of the release.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com>
> > > wrote:
> > > > > >>
> > > > > >> JNI is a broad category - which really just means calling out from
> > > Java
> > > > > to
> > > > > >> native O/S libraries.
> > > > > >>
> > > > > >> If the library is intended as a holder for "any JNI needed by
> > > Artemis,"
> > > > > >> then I don't see value in dis-associating it from Artemis.  OTOH,
> > > if the
> > > > > >> library has functionality that could be useful to other projects,
> > > > > outside
> > > > > >> of Artemis, then I can see a value to breaking it away from the
> > > Artemis
> > > > > >> name and making it more reusable.
> > > > > >>
> > > > > >> As for making it a separate repo with its own lifecycle, I don't
> > > have a
> > > > > >> concern either way on that front.  Although I am not sure why it
> > > helps
> > > > > to
> > > > > >> do so.  Well, one question comes to mind - isn't this library
> > > Linux, or
> > > > > >> Posix, specific?  Or, does it build on all systems that might be
> > > used to
> > > > > >> build Artemis?
> > > > > >>
> > > > > >> Art
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <
> > > > > clebert.suconic@gmail.com>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Currently it’s used for JNi operations around storage.  Mostly
> > > > > libido.  But
> > > > > >> > I foresee being used for other cases where we may need JNI.
> > > > > >> >
> > > > > >> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com>
> > > wrote:
> > > > > >> >
> > > > > >> > > What is in the library?
> > > > > >> > >
> > > > > >> > > Art
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > > > > >> > > clebert.suconic@gmail.com>
> > > > > >> > > wrote:
> > > > > >> > >
> > > > > >> > > > I thought Since the native project had open scope like I'm
> > > > > proposing,
> > > > > >> > > > it would eventually be useful anywhere that needs a JNI
> > > library.
> > > > > >> > > >
> > > > > >> > > > But we can go with activemq-artemis-native. That's fine.
> > > > > >> > > >
> > > > > >> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <
> > > jgenender@apache.org>
> > > > > >> > wrote:
> > > > > >> > > > >
> > > > > >> > > > > Hey Clebert,
> > > > > >> > > > >
> > > > > >> > > > > This is really cool stuff.  But I don't like it being called
> > > > > >> > > > ActiveMQ-native
> > > > > >> > > > > because it will confuse people with ActiveMQ classic (which
> > > > > really is
> > > > > >> > > > > ActiveMQ for now) or that it would even work with ActiveMQ
> > > > > 5.x.  I
> > > > > >> > > would
> > > > > >> > > > > recommend retaining the Artemis in the name, or
> > > > > >> > > ActiveMQ-Artemis-native.
> > > > > >> > > > > If/when Artemis becomes ActiveMQ, then that could certainly
> > > be
> > > > > an
> > > > > >> > > option
> > > > > >> > > > to
> > > > > >> > > > > drop Artemis. But at this stage I think its too confusing.
> > > > > >> > > > >
> > > > > >> > > > > Jeff
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > > > --
> > > > > >> > > > > Sent from:
> > > > > >> > > >
> > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > > > --
> > > > > >> > > > Clebert Suconic
> > > > > >> > > >
> > > > > >> > >
> > > > > >> > --
> > > > > >> > Clebert Suconic
> > > > > >> >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Clebert Suconic
> > > > >
> > >
> > >
> > >
> > > --
> > > Clebert Suconic
> > >
>
>
>
> --
> Clebert Suconic



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
As a Heads-UP. We have been separating the history on this repository here:

https://github.com/clebertsuconic/activemq-artemis-native

Which is now ready to go.

so I will go ahead and create the github repository tomorrow. and add
these bits in there.
I plan to make a first release soon, so I will be working on providing
a download page.



And BTW: I have done some progress on how the natives are compiled.
There's a script that will create a docker image, and use it to
generate the binaries. So the only building dependency you will need
is docker. (kind of cool actually).

you will still be able to build it on your own box if you want... but
this will make it easier to generate the releases.



I will send another HEADS-UP for a release as soon as I'm ready.

On Fri, Feb 1, 2019 at 7:38 AM Christopher Shannon
<ch...@gmail.com> wrote:
>
> It makes sense to me to have a separate release cycle for the JNI parts.  I
> think lazy consensus is fine here and as long no one objects you can just
> go ahead and create it without a formal vote.
>
> On Thu, Jan 31, 2019 at 3:51 PM Clebert Suconic <cl...@gmail.com>
> wrote:
>
> > yep, so far the best name is ActiveMQ-Artemis-native
> >
> >
> > I don't think this is a big deal and I don't intend to create a vote
> > for this.. as this is regular business. We are creating a separate
> > repository for the native part, not a project!
> >
> > Let me know If you anyone think I'm wrong and this needs a vote please.
> >
> > On Thu, Jan 31, 2019 at 1:59 PM Arthur Naseef <ar...@amlinv.com> wrote:
> > >
> > > That makes sense then - having a separate repo and release cycle for the
> > > native JNI library.
> > >
> > > Perhaps, as Jeff suggested, ActiveMQ-Artemis-native would be a good name?
> > >
> > > Art
> > >
> > >
> > > On Thu, Jan 31, 2019 at 10:04 AM Clebert Suconic <
> > clebert.suconic@gmail.com>
> > > wrote:
> > >
> > > > forgot to answer another point.
> > > >
> > > > Right now it's for posix (Linux) only. but that could change as the
> > > > project progresses.
> > > >
> > > > On Thu, Jan 31, 2019 at 11:51 AM Clebert Suconic
> > > > <cl...@gmail.com> wrote:
> > > > >
> > > > > -- If the library is intended as a holder for "any JNI needed by
> > > > Artemis,"
> > > > > then I don't see value in dis-associating it from Artemis.  OTOH, if
> > the
> > > > > library has functionality that could be useful to other projects,
> > outside
> > > > > of Artemis, then I can see a value to breaking it away from the
> > Artemis
> > > > > name and making it more reusable.
> > > > >
> > > > >
> > > > > I thought about the possibility of dis-associating. .but you're
> > right..
> > > > it's a bit more complicated... I wouldn't disassociate.
> > > > >
> > > > >
> > > > > >>>>  I don't have a concern either way on that front.  Although I am
> > > > not sure why it helps to do so.
> > > > >
> > > > >
> > > > > This is a chicken / egg situation. Right now when we build the native
> > > > layer, we have to commit binary file on the git repository.
> > > > > I'm intending to fix that part.
> > > > >
> > > > > And that makes it difficult to have a real build from source
> > experience.
> > > > I have had a few cases where users needed to rebuild it from scratch,
> > and
> > > > bumped into this native issue, which I'm trying to improve here.
> > > > >
> > > > > The native layer build wouldn't have any .so, and the .so would be
> > part
> > > > of the release.
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com>
> > wrote:
> > > > >>
> > > > >> JNI is a broad category - which really just means calling out from
> > Java
> > > > to
> > > > >> native O/S libraries.
> > > > >>
> > > > >> If the library is intended as a holder for "any JNI needed by
> > Artemis,"
> > > > >> then I don't see value in dis-associating it from Artemis.  OTOH,
> > if the
> > > > >> library has functionality that could be useful to other projects,
> > > > outside
> > > > >> of Artemis, then I can see a value to breaking it away from the
> > Artemis
> > > > >> name and making it more reusable.
> > > > >>
> > > > >> As for making it a separate repo with its own lifecycle, I don't
> > have a
> > > > >> concern either way on that front.  Although I am not sure why it
> > helps
> > > > to
> > > > >> do so.  Well, one question comes to mind - isn't this library
> > Linux, or
> > > > >> Posix, specific?  Or, does it build on all systems that might be
> > used to
> > > > >> build Artemis?
> > > > >>
> > > > >> Art
> > > > >>
> > > > >>
> > > > >> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <
> > > > clebert.suconic@gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >> > Currently it’s used for JNi operations around storage.  Mostly
> > > > libido.  But
> > > > >> > I foresee being used for other cases where we may need JNI.
> > > > >> >
> > > > >> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com>
> > wrote:
> > > > >> >
> > > > >> > > What is in the library?
> > > > >> > >
> > > > >> > > Art
> > > > >> > >
> > > > >> > >
> > > > >> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > > > >> > > clebert.suconic@gmail.com>
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > > > I thought Since the native project had open scope like I'm
> > > > proposing,
> > > > >> > > > it would eventually be useful anywhere that needs a JNI
> > library.
> > > > >> > > >
> > > > >> > > > But we can go with activemq-artemis-native. That's fine.
> > > > >> > > >
> > > > >> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <
> > jgenender@apache.org>
> > > > >> > wrote:
> > > > >> > > > >
> > > > >> > > > > Hey Clebert,
> > > > >> > > > >
> > > > >> > > > > This is really cool stuff.  But I don't like it being called
> > > > >> > > > ActiveMQ-native
> > > > >> > > > > because it will confuse people with ActiveMQ classic (which
> > > > really is
> > > > >> > > > > ActiveMQ for now) or that it would even work with ActiveMQ
> > > > 5.x.  I
> > > > >> > > would
> > > > >> > > > > recommend retaining the Artemis in the name, or
> > > > >> > > ActiveMQ-Artemis-native.
> > > > >> > > > > If/when Artemis becomes ActiveMQ, then that could certainly
> > be
> > > > an
> > > > >> > > option
> > > > >> > > > to
> > > > >> > > > > drop Artemis. But at this stage I think its too confusing.
> > > > >> > > > >
> > > > >> > > > > Jeff
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > --
> > > > >> > > > > Sent from:
> > > > >> > > >
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > --
> > > > >> > > > Clebert Suconic
> > > > >> > > >
> > > > >> > >
> > > > >> > --
> > > > >> > Clebert Suconic
> > > > >> >
> > > >
> > > >
> > > >
> > > > --
> > > > Clebert Suconic
> > > >
> >
> >
> >
> > --
> > Clebert Suconic
> >



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Christopher Shannon <ch...@gmail.com>.
It makes sense to me to have a separate release cycle for the JNI parts.  I
think lazy consensus is fine here and as long no one objects you can just
go ahead and create it without a formal vote.

On Thu, Jan 31, 2019 at 3:51 PM Clebert Suconic <cl...@gmail.com>
wrote:

> yep, so far the best name is ActiveMQ-Artemis-native
>
>
> I don't think this is a big deal and I don't intend to create a vote
> for this.. as this is regular business. We are creating a separate
> repository for the native part, not a project!
>
> Let me know If you anyone think I'm wrong and this needs a vote please.
>
> On Thu, Jan 31, 2019 at 1:59 PM Arthur Naseef <ar...@amlinv.com> wrote:
> >
> > That makes sense then - having a separate repo and release cycle for the
> > native JNI library.
> >
> > Perhaps, as Jeff suggested, ActiveMQ-Artemis-native would be a good name?
> >
> > Art
> >
> >
> > On Thu, Jan 31, 2019 at 10:04 AM Clebert Suconic <
> clebert.suconic@gmail.com>
> > wrote:
> >
> > > forgot to answer another point.
> > >
> > > Right now it's for posix (Linux) only. but that could change as the
> > > project progresses.
> > >
> > > On Thu, Jan 31, 2019 at 11:51 AM Clebert Suconic
> > > <cl...@gmail.com> wrote:
> > > >
> > > > -- If the library is intended as a holder for "any JNI needed by
> > > Artemis,"
> > > > then I don't see value in dis-associating it from Artemis.  OTOH, if
> the
> > > > library has functionality that could be useful to other projects,
> outside
> > > > of Artemis, then I can see a value to breaking it away from the
> Artemis
> > > > name and making it more reusable.
> > > >
> > > >
> > > > I thought about the possibility of dis-associating. .but you're
> right..
> > > it's a bit more complicated... I wouldn't disassociate.
> > > >
> > > >
> > > > >>>>  I don't have a concern either way on that front.  Although I am
> > > not sure why it helps to do so.
> > > >
> > > >
> > > > This is a chicken / egg situation. Right now when we build the native
> > > layer, we have to commit binary file on the git repository.
> > > > I'm intending to fix that part.
> > > >
> > > > And that makes it difficult to have a real build from source
> experience.
> > > I have had a few cases where users needed to rebuild it from scratch,
> and
> > > bumped into this native issue, which I'm trying to improve here.
> > > >
> > > > The native layer build wouldn't have any .so, and the .so would be
> part
> > > of the release.
> > > >
> > > >
> > > >
> > > > On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com>
> wrote:
> > > >>
> > > >> JNI is a broad category - which really just means calling out from
> Java
> > > to
> > > >> native O/S libraries.
> > > >>
> > > >> If the library is intended as a holder for "any JNI needed by
> Artemis,"
> > > >> then I don't see value in dis-associating it from Artemis.  OTOH,
> if the
> > > >> library has functionality that could be useful to other projects,
> > > outside
> > > >> of Artemis, then I can see a value to breaking it away from the
> Artemis
> > > >> name and making it more reusable.
> > > >>
> > > >> As for making it a separate repo with its own lifecycle, I don't
> have a
> > > >> concern either way on that front.  Although I am not sure why it
> helps
> > > to
> > > >> do so.  Well, one question comes to mind - isn't this library
> Linux, or
> > > >> Posix, specific?  Or, does it build on all systems that might be
> used to
> > > >> build Artemis?
> > > >>
> > > >> Art
> > > >>
> > > >>
> > > >> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <
> > > clebert.suconic@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Currently it’s used for JNi operations around storage.  Mostly
> > > libido.  But
> > > >> > I foresee being used for other cases where we may need JNI.
> > > >> >
> > > >> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com>
> wrote:
> > > >> >
> > > >> > > What is in the library?
> > > >> > >
> > > >> > > Art
> > > >> > >
> > > >> > >
> > > >> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > > >> > > clebert.suconic@gmail.com>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > I thought Since the native project had open scope like I'm
> > > proposing,
> > > >> > > > it would eventually be useful anywhere that needs a JNI
> library.
> > > >> > > >
> > > >> > > > But we can go with activemq-artemis-native. That's fine.
> > > >> > > >
> > > >> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <
> jgenender@apache.org>
> > > >> > wrote:
> > > >> > > > >
> > > >> > > > > Hey Clebert,
> > > >> > > > >
> > > >> > > > > This is really cool stuff.  But I don't like it being called
> > > >> > > > ActiveMQ-native
> > > >> > > > > because it will confuse people with ActiveMQ classic (which
> > > really is
> > > >> > > > > ActiveMQ for now) or that it would even work with ActiveMQ
> > > 5.x.  I
> > > >> > > would
> > > >> > > > > recommend retaining the Artemis in the name, or
> > > >> > > ActiveMQ-Artemis-native.
> > > >> > > > > If/when Artemis becomes ActiveMQ, then that could certainly
> be
> > > an
> > > >> > > option
> > > >> > > > to
> > > >> > > > > drop Artemis. But at this stage I think its too confusing.
> > > >> > > > >
> > > >> > > > > Jeff
> > > >> > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > Sent from:
> > > >> > > >
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > > Clebert Suconic
> > > >> > > >
> > > >> > >
> > > >> > --
> > > >> > Clebert Suconic
> > > >> >
> > >
> > >
> > >
> > > --
> > > Clebert Suconic
> > >
>
>
>
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
yep, so far the best name is ActiveMQ-Artemis-native


I don't think this is a big deal and I don't intend to create a vote
for this.. as this is regular business. We are creating a separate
repository for the native part, not a project!

Let me know If you anyone think I'm wrong and this needs a vote please.

On Thu, Jan 31, 2019 at 1:59 PM Arthur Naseef <ar...@amlinv.com> wrote:
>
> That makes sense then - having a separate repo and release cycle for the
> native JNI library.
>
> Perhaps, as Jeff suggested, ActiveMQ-Artemis-native would be a good name?
>
> Art
>
>
> On Thu, Jan 31, 2019 at 10:04 AM Clebert Suconic <cl...@gmail.com>
> wrote:
>
> > forgot to answer another point.
> >
> > Right now it's for posix (Linux) only. but that could change as the
> > project progresses.
> >
> > On Thu, Jan 31, 2019 at 11:51 AM Clebert Suconic
> > <cl...@gmail.com> wrote:
> > >
> > > -- If the library is intended as a holder for "any JNI needed by
> > Artemis,"
> > > then I don't see value in dis-associating it from Artemis.  OTOH, if the
> > > library has functionality that could be useful to other projects, outside
> > > of Artemis, then I can see a value to breaking it away from the Artemis
> > > name and making it more reusable.
> > >
> > >
> > > I thought about the possibility of dis-associating. .but you're right..
> > it's a bit more complicated... I wouldn't disassociate.
> > >
> > >
> > > >>>>  I don't have a concern either way on that front.  Although I am
> > not sure why it helps to do so.
> > >
> > >
> > > This is a chicken / egg situation. Right now when we build the native
> > layer, we have to commit binary file on the git repository.
> > > I'm intending to fix that part.
> > >
> > > And that makes it difficult to have a real build from source experience.
> > I have had a few cases where users needed to rebuild it from scratch, and
> > bumped into this native issue, which I'm trying to improve here.
> > >
> > > The native layer build wouldn't have any .so, and the .so would be part
> > of the release.
> > >
> > >
> > >
> > > On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com> wrote:
> > >>
> > >> JNI is a broad category - which really just means calling out from Java
> > to
> > >> native O/S libraries.
> > >>
> > >> If the library is intended as a holder for "any JNI needed by Artemis,"
> > >> then I don't see value in dis-associating it from Artemis.  OTOH, if the
> > >> library has functionality that could be useful to other projects,
> > outside
> > >> of Artemis, then I can see a value to breaking it away from the Artemis
> > >> name and making it more reusable.
> > >>
> > >> As for making it a separate repo with its own lifecycle, I don't have a
> > >> concern either way on that front.  Although I am not sure why it helps
> > to
> > >> do so.  Well, one question comes to mind - isn't this library Linux, or
> > >> Posix, specific?  Or, does it build on all systems that might be used to
> > >> build Artemis?
> > >>
> > >> Art
> > >>
> > >>
> > >> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <
> > clebert.suconic@gmail.com>
> > >> wrote:
> > >>
> > >> > Currently it’s used for JNi operations around storage.  Mostly
> > libido.  But
> > >> > I foresee being used for other cases where we may need JNI.
> > >> >
> > >> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com> wrote:
> > >> >
> > >> > > What is in the library?
> > >> > >
> > >> > > Art
> > >> > >
> > >> > >
> > >> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > >> > > clebert.suconic@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > I thought Since the native project had open scope like I'm
> > proposing,
> > >> > > > it would eventually be useful anywhere that needs a JNI library.
> > >> > > >
> > >> > > > But we can go with activemq-artemis-native. That's fine.
> > >> > > >
> > >> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org>
> > >> > wrote:
> > >> > > > >
> > >> > > > > Hey Clebert,
> > >> > > > >
> > >> > > > > This is really cool stuff.  But I don't like it being called
> > >> > > > ActiveMQ-native
> > >> > > > > because it will confuse people with ActiveMQ classic (which
> > really is
> > >> > > > > ActiveMQ for now) or that it would even work with ActiveMQ
> > 5.x.  I
> > >> > > would
> > >> > > > > recommend retaining the Artemis in the name, or
> > >> > > ActiveMQ-Artemis-native.
> > >> > > > > If/when Artemis becomes ActiveMQ, then that could certainly be
> > an
> > >> > > option
> > >> > > > to
> > >> > > > > drop Artemis. But at this stage I think its too confusing.
> > >> > > > >
> > >> > > > > Jeff
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > --
> > >> > > > > Sent from:
> > >> > > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Clebert Suconic
> > >> > > >
> > >> > >
> > >> > --
> > >> > Clebert Suconic
> > >> >
> >
> >
> >
> > --
> > Clebert Suconic
> >



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Arthur Naseef <ar...@amlinv.com>.
That makes sense then - having a separate repo and release cycle for the
native JNI library.

Perhaps, as Jeff suggested, ActiveMQ-Artemis-native would be a good name?

Art


On Thu, Jan 31, 2019 at 10:04 AM Clebert Suconic <cl...@gmail.com>
wrote:

> forgot to answer another point.
>
> Right now it's for posix (Linux) only. but that could change as the
> project progresses.
>
> On Thu, Jan 31, 2019 at 11:51 AM Clebert Suconic
> <cl...@gmail.com> wrote:
> >
> > -- If the library is intended as a holder for "any JNI needed by
> Artemis,"
> > then I don't see value in dis-associating it from Artemis.  OTOH, if the
> > library has functionality that could be useful to other projects, outside
> > of Artemis, then I can see a value to breaking it away from the Artemis
> > name and making it more reusable.
> >
> >
> > I thought about the possibility of dis-associating. .but you're right..
> it's a bit more complicated... I wouldn't disassociate.
> >
> >
> > >>>>  I don't have a concern either way on that front.  Although I am
> not sure why it helps to do so.
> >
> >
> > This is a chicken / egg situation. Right now when we build the native
> layer, we have to commit binary file on the git repository.
> > I'm intending to fix that part.
> >
> > And that makes it difficult to have a real build from source experience.
> I have had a few cases where users needed to rebuild it from scratch, and
> bumped into this native issue, which I'm trying to improve here.
> >
> > The native layer build wouldn't have any .so, and the .so would be part
> of the release.
> >
> >
> >
> > On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com> wrote:
> >>
> >> JNI is a broad category - which really just means calling out from Java
> to
> >> native O/S libraries.
> >>
> >> If the library is intended as a holder for "any JNI needed by Artemis,"
> >> then I don't see value in dis-associating it from Artemis.  OTOH, if the
> >> library has functionality that could be useful to other projects,
> outside
> >> of Artemis, then I can see a value to breaking it away from the Artemis
> >> name and making it more reusable.
> >>
> >> As for making it a separate repo with its own lifecycle, I don't have a
> >> concern either way on that front.  Although I am not sure why it helps
> to
> >> do so.  Well, one question comes to mind - isn't this library Linux, or
> >> Posix, specific?  Or, does it build on all systems that might be used to
> >> build Artemis?
> >>
> >> Art
> >>
> >>
> >> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <
> clebert.suconic@gmail.com>
> >> wrote:
> >>
> >> > Currently it’s used for JNi operations around storage.  Mostly
> libido.  But
> >> > I foresee being used for other cases where we may need JNI.
> >> >
> >> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com> wrote:
> >> >
> >> > > What is in the library?
> >> > >
> >> > > Art
> >> > >
> >> > >
> >> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> >> > > clebert.suconic@gmail.com>
> >> > > wrote:
> >> > >
> >> > > > I thought Since the native project had open scope like I'm
> proposing,
> >> > > > it would eventually be useful anywhere that needs a JNI library.
> >> > > >
> >> > > > But we can go with activemq-artemis-native. That's fine.
> >> > > >
> >> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org>
> >> > wrote:
> >> > > > >
> >> > > > > Hey Clebert,
> >> > > > >
> >> > > > > This is really cool stuff.  But I don't like it being called
> >> > > > ActiveMQ-native
> >> > > > > because it will confuse people with ActiveMQ classic (which
> really is
> >> > > > > ActiveMQ for now) or that it would even work with ActiveMQ
> 5.x.  I
> >> > > would
> >> > > > > recommend retaining the Artemis in the name, or
> >> > > ActiveMQ-Artemis-native.
> >> > > > > If/when Artemis becomes ActiveMQ, then that could certainly be
> an
> >> > > option
> >> > > > to
> >> > > > > drop Artemis. But at this stage I think its too confusing.
> >> > > > >
> >> > > > > Jeff
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Sent from:
> >> > > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> >> > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Clebert Suconic
> >> > > >
> >> > >
> >> > --
> >> > Clebert Suconic
> >> >
>
>
>
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
forgot to answer another point.

Right now it's for posix (Linux) only. but that could change as the
project progresses.

On Thu, Jan 31, 2019 at 11:51 AM Clebert Suconic
<cl...@gmail.com> wrote:
>
> -- If the library is intended as a holder for "any JNI needed by Artemis,"
> then I don't see value in dis-associating it from Artemis.  OTOH, if the
> library has functionality that could be useful to other projects, outside
> of Artemis, then I can see a value to breaking it away from the Artemis
> name and making it more reusable.
>
>
> I thought about the possibility of dis-associating. .but you're right.. it's a bit more complicated... I wouldn't disassociate.
>
>
> >>>>  I don't have a concern either way on that front.  Although I am not sure why it helps to do so.
>
>
> This is a chicken / egg situation. Right now when we build the native layer, we have to commit binary file on the git repository.
> I'm intending to fix that part.
>
> And that makes it difficult to have a real build from source experience. I have had a few cases where users needed to rebuild it from scratch, and bumped into this native issue, which I'm trying to improve here.
>
> The native layer build wouldn't have any .so, and the .so would be part of the release.
>
>
>
> On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com> wrote:
>>
>> JNI is a broad category - which really just means calling out from Java to
>> native O/S libraries.
>>
>> If the library is intended as a holder for "any JNI needed by Artemis,"
>> then I don't see value in dis-associating it from Artemis.  OTOH, if the
>> library has functionality that could be useful to other projects, outside
>> of Artemis, then I can see a value to breaking it away from the Artemis
>> name and making it more reusable.
>>
>> As for making it a separate repo with its own lifecycle, I don't have a
>> concern either way on that front.  Although I am not sure why it helps to
>> do so.  Well, one question comes to mind - isn't this library Linux, or
>> Posix, specific?  Or, does it build on all systems that might be used to
>> build Artemis?
>>
>> Art
>>
>>
>> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <cl...@gmail.com>
>> wrote:
>>
>> > Currently it’s used for JNi operations around storage.  Mostly libido.  But
>> > I foresee being used for other cases where we may need JNI.
>> >
>> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com> wrote:
>> >
>> > > What is in the library?
>> > >
>> > > Art
>> > >
>> > >
>> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
>> > > clebert.suconic@gmail.com>
>> > > wrote:
>> > >
>> > > > I thought Since the native project had open scope like I'm proposing,
>> > > > it would eventually be useful anywhere that needs a JNI library.
>> > > >
>> > > > But we can go with activemq-artemis-native. That's fine.
>> > > >
>> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org>
>> > wrote:
>> > > > >
>> > > > > Hey Clebert,
>> > > > >
>> > > > > This is really cool stuff.  But I don't like it being called
>> > > > ActiveMQ-native
>> > > > > because it will confuse people with ActiveMQ classic (which really is
>> > > > > ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I
>> > > would
>> > > > > recommend retaining the Artemis in the name, or
>> > > ActiveMQ-Artemis-native.
>> > > > > If/when Artemis becomes ActiveMQ, then that could certainly be an
>> > > option
>> > > > to
>> > > > > drop Artemis. But at this stage I think its too confusing.
>> > > > >
>> > > > > Jeff
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Sent from:
>> > > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Clebert Suconic
>> > > >
>> > >
>> > --
>> > Clebert Suconic
>> >



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
-- If the library is intended as a holder for "any JNI needed by Artemis,"
then I don't see value in dis-associating it from Artemis.  OTOH, if the
library has functionality that could be useful to other projects, outside
of Artemis, then I can see a value to breaking it away from the Artemis
name and making it more reusable.


I thought about the possibility of dis-associating. .but you're right..
it's a bit more complicated... I wouldn't disassociate.


>>>>  I don't have a concern either way on that front.  Although I am not
sure why it helps to do so.


This is a chicken / egg situation. Right now when we build the native
layer, we have to commit binary file on the git repository.
I'm intending to fix that part.

And that makes it difficult to have a real build from source experience. I
have had a few cases where users needed to rebuild it from scratch, and
bumped into this native issue, which I'm trying to improve here.

The native layer build wouldn't have any .so, and the .so would be part of
the release.



On Thu, Jan 31, 2019 at 12:36 AM Arthur Naseef <ar...@amlinv.com> wrote:

> JNI is a broad category - which really just means calling out from Java to
> native O/S libraries.
>
> If the library is intended as a holder for "any JNI needed by Artemis,"
> then I don't see value in dis-associating it from Artemis.  OTOH, if the
> library has functionality that could be useful to other projects, outside
> of Artemis, then I can see a value to breaking it away from the Artemis
> name and making it more reusable.
>
> As for making it a separate repo with its own lifecycle, I don't have a
> concern either way on that front.  Although I am not sure why it helps to
> do so.  Well, one question comes to mind - isn't this library Linux, or
> Posix, specific?  Or, does it build on all systems that might be used to
> build Artemis?
>
> Art
>
>
> On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <clebert.suconic@gmail.com
> >
> wrote:
>
> > Currently it’s used for JNi operations around storage.  Mostly libido.
> But
> > I foresee being used for other cases where we may need JNI.
> >
> > On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com> wrote:
> >
> > > What is in the library?
> > >
> > > Art
> > >
> > >
> > > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > > clebert.suconic@gmail.com>
> > > wrote:
> > >
> > > > I thought Since the native project had open scope like I'm proposing,
> > > > it would eventually be useful anywhere that needs a JNI library.
> > > >
> > > > But we can go with activemq-artemis-native. That's fine.
> > > >
> > > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org>
> > wrote:
> > > > >
> > > > > Hey Clebert,
> > > > >
> > > > > This is really cool stuff.  But I don't like it being called
> > > > ActiveMQ-native
> > > > > because it will confuse people with ActiveMQ classic (which really
> is
> > > > > ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I
> > > would
> > > > > recommend retaining the Artemis in the name, or
> > > ActiveMQ-Artemis-native.
> > > > > If/when Artemis becomes ActiveMQ, then that could certainly be an
> > > option
> > > > to
> > > > > drop Artemis. But at this stage I think its too confusing.
> > > > >
> > > > > Jeff
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from:
> > > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> > > >
> > > >
> > > >
> > > > --
> > > > Clebert Suconic
> > > >
> > >
> > --
> > Clebert Suconic
> >
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Arthur Naseef <ar...@amlinv.com>.
JNI is a broad category - which really just means calling out from Java to
native O/S libraries.

If the library is intended as a holder for "any JNI needed by Artemis,"
then I don't see value in dis-associating it from Artemis.  OTOH, if the
library has functionality that could be useful to other projects, outside
of Artemis, then I can see a value to breaking it away from the Artemis
name and making it more reusable.

As for making it a separate repo with its own lifecycle, I don't have a
concern either way on that front.  Although I am not sure why it helps to
do so.  Well, one question comes to mind - isn't this library Linux, or
Posix, specific?  Or, does it build on all systems that might be used to
build Artemis?

Art


On Wed, Jan 30, 2019 at 9:52 PM Clebert Suconic <cl...@gmail.com>
wrote:

> Currently it’s used for JNi operations around storage.  Mostly libido.  But
> I foresee being used for other cases where we may need JNI.
>
> On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com> wrote:
>
> > What is in the library?
> >
> > Art
> >
> >
> > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > clebert.suconic@gmail.com>
> > wrote:
> >
> > > I thought Since the native project had open scope like I'm proposing,
> > > it would eventually be useful anywhere that needs a JNI library.
> > >
> > > But we can go with activemq-artemis-native. That's fine.
> > >
> > > On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org>
> wrote:
> > > >
> > > > Hey Clebert,
> > > >
> > > > This is really cool stuff.  But I don't like it being called
> > > ActiveMQ-native
> > > > because it will confuse people with ActiveMQ classic (which really is
> > > > ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I
> > would
> > > > recommend retaining the Artemis in the name, or
> > ActiveMQ-Artemis-native.
> > > > If/when Artemis becomes ActiveMQ, then that could certainly be an
> > option
> > > to
> > > > drop Artemis. But at this stage I think its too confusing.
> > > >
> > > > Jeff
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from:
> > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> > >
> > >
> > >
> > > --
> > > Clebert Suconic
> > >
> >
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
Currently it’s used for JNi operations around storage.  Mostly libido.  But
I foresee being used for other cases where we may need JNI.

On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef <ar...@amlinv.com> wrote:

> What is in the library?
>
> Art
>
>
> On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> clebert.suconic@gmail.com>
> wrote:
>
> > I thought Since the native project had open scope like I'm proposing,
> > it would eventually be useful anywhere that needs a JNI library.
> >
> > But we can go with activemq-artemis-native. That's fine.
> >
> > On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org> wrote:
> > >
> > > Hey Clebert,
> > >
> > > This is really cool stuff.  But I don't like it being called
> > ActiveMQ-native
> > > because it will confuse people with ActiveMQ classic (which really is
> > > ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I
> would
> > > recommend retaining the Artemis in the name, or
> ActiveMQ-Artemis-native.
> > > If/when Artemis becomes ActiveMQ, then that could certainly be an
> option
> > to
> > > drop Artemis. But at this stage I think its too confusing.
> > >
> > > Jeff
> > >
> > >
> > >
> > > --
> > > Sent from:
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
> >
> >
> >
> > --
> > Clebert Suconic
> >
>
-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Arthur Naseef <ar...@amlinv.com>.
What is in the library?

Art


On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <cl...@gmail.com>
wrote:

> I thought Since the native project had open scope like I'm proposing,
> it would eventually be useful anywhere that needs a JNI library.
>
> But we can go with activemq-artemis-native. That's fine.
>
> On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org> wrote:
> >
> > Hey Clebert,
> >
> > This is really cool stuff.  But I don't like it being called
> ActiveMQ-native
> > because it will confuse people with ActiveMQ classic (which really is
> > ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I would
> > recommend retaining the Artemis in the name, or ActiveMQ-Artemis-native.
> > If/when Artemis becomes ActiveMQ, then that could certainly be an option
> to
> > drop Artemis. But at this stage I think its too confusing.
> >
> > Jeff
> >
> >
> >
> > --
> > Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
>
>
>
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
I thought Since the native project had open scope like I'm proposing,
it would eventually be useful anywhere that needs a JNI library.

But we can go with activemq-artemis-native. That's fine.

On Wed, Jan 30, 2019 at 12:51 PM jgenender <jg...@apache.org> wrote:
>
> Hey Clebert,
>
> This is really cool stuff.  But I don't like it being called ActiveMQ-native
> because it will confuse people with ActiveMQ classic (which really is
> ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I would
> recommend retaining the Artemis in the name, or ActiveMQ-Artemis-native.
> If/when Artemis becomes ActiveMQ, then that could certainly be an option to
> drop Artemis. But at this stage I think its too confusing.
>
> Jeff
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by jgenender <jg...@apache.org>.
Hey Clebert,

This is really cool stuff.  But I don't like it being called ActiveMQ-native
because it will confuse people with ActiveMQ classic (which really is
ActiveMQ for now) or that it would even work with ActiveMQ 5.x.  I would
recommend retaining the Artemis in the name, or ActiveMQ-Artemis-native. 
If/when Artemis becomes ActiveMQ, then that could certainly be an option to
drop Artemis. But at this stage I think its too confusing.

Jeff



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Otavio Piske <op...@redhat.com>.
> I don't think it as a separate project, just as a separate repository
with its own release cycle to make things easier.

I like the idea of a separate repository for that component and I like the
idea of a separate release cycle. From my POV, it seems that it would allow
it to evolve at it's own pace. I also think it would add some flexibility
to the feature set of Artemis (for example, one idea I was playing with
recently - just for fun - was whether we could add support for ASYNC AIO on
IBM Power and ARM). Maybe a separate component would allow this sort of
thing without causing too much noise and instabilities risks to the project.

On Wed, Jan 30, 2019 at 5:52 PM michael.andre.pearce
<mi...@me.com.invalid> wrote:

> Tbh, i see nothing wrong with making it a mini sub project. If anything
> having some sub projects is a good thing.
> Would the supporting java code be moved also?
> And would we look to make the interfaces more generic?
> Im keen if we separate something thats currently tighly embedded in
> artemis, we make sure it is much more re-usable (e.g. even example
> alternative uses).
> On that note, i think there are other bits that could be split out, a bit
> like what occured in activemq5.
> E.g. spring integration, protocol manager, other extensions
> And should welcome this a little more with newer extensions or features
> that enhance activemq but not core broker.
>
>
>
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: Clebert Suconic <
> clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a
> separated project
> One of the modules of ActiveMQ Artemis is the Native Layer:
>
>
> https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
>
> We currently hold all JNI Calls (pretty much libaio ATM).
>
> It is stable and the release cycle is very long. Maybe one or two
> changes an year with the current scope. This may become different if
> we expand the scope of JNI operations supported by the broker).
>
> I would like to make it a separate git repository from ActiveMQ
> Artemis, with its own releasy cycle. (we would even be able to remove
> the currently .so that are currently checked in on artemis).  It is
> the sensitive thing to do.
>
> I don't think it as a separate project, just as a separate repository
> with its own release cycle to make things easier.
>
> I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> it would be used for any further JNI operations needed for any other
> Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> but I would keep the door open for other JNI operations we may need.
>
>
> I was wondering if anyone have any other ideas around it.
>
>
> Also: Would we need a vote to proceed on such change after we reach a
> consensus on what to do here?
> --
> Clebert Suconic
>


-- 
Otavio R. Piske
Messaging Quality Assurance Engineer

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
Yes.. We should move the java part as well to be more reusable.

On Wed, Jan 30, 2019 at 11:51 AM michael.andre.pearce
<mi...@me.com.invalid> wrote:
>
> Tbh, i see nothing wrong with making it a mini sub project. If anything having some sub projects is a good thing.
> Would the supporting java code be moved also?
> And would we look to make the interfaces more generic?
> Im keen if we separate something thats currently tighly embedded in artemis, we make sure it is much more re-usable (e.g. even example alternative uses).
> On that note, i think there are other bits that could be split out, a bit like what occured in activemq5.
> E.g. spring integration, protocol manager, other extensions
> And should welcome this a little more with newer extensions or features that enhance activemq but not core broker.
>
>
>
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: Clebert Suconic <cl...@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To: dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a separated project
> One of the modules of ActiveMQ Artemis is the Native Layer:
>
> https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
>
> We currently hold all JNI Calls (pretty much libaio ATM).
>
> It is stable and the release cycle is very long. Maybe one or two
> changes an year with the current scope. This may become different if
> we expand the scope of JNI operations supported by the broker).
>
> I would like to make it a separate git repository from ActiveMQ
> Artemis, with its own releasy cycle. (we would even be able to remove
> the currently .so that are currently checked in on artemis).  It is
> the sensitive thing to do.
>
> I don't think it as a separate project, just as a separate repository
> with its own release cycle to make things easier.
>
> I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> it would be used for any further JNI operations needed for any other
> Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> but I would keep the door open for other JNI operations we may need.
>
>
> I was wondering if anyone have any other ideas around it.
>
>
> Also: Would we need a vote to proceed on such change after we reach a
> consensus on what to do here?
> --
> Clebert Suconic



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
Say that a later point we add a new library to support a new device or
new native API.

I would prefer we still produce a new .SO for artemis. That is..
Artemis-Native-32.so and Artemis-Native-64.so. Just to make it
illustrative lets say we want to support MagneticTapes on the Journal.

The new JNI operations would be embedded as part of the same .so.




On that case, you would have

src/java/main/.... LibAIO.java
/src/java/main/....LibMagneticType.java


that will generate two .c and .h files
src/java/c/.....LibMagnetic.c libMagnetic.h
src/java/c/.....LibAIO.c libAIO.c


and a single .so


The cost to maintain the Cmake and its built it's somewhat high IMO.
Bootstrapping a new project later on to allow the new API would
require a lot more time and investment.
As a matter of fact, I have plans for some APIs in a near future (that
I don't want to bring to this discussion now, as I don't want to make
any promises), but having them on a separate project would make time
investment a bit higher, for no reason.







On Wed, Jan 30, 2019 at 12:29 PM Francesco Nigro <ni...@gmail.com> wrote:
>
> Re the naming: native would be a module for all the sub component sharing
> native interfaces of any kind. I prefer that too even if, effectively ATM
> we will have just libAIO on it...
>
> Il giorno mer 30 gen 2019 alle ore 18:18 Clebert Suconic <
> clebert.suconic@gmail.com> ha scritto:
>
> > I would not like to make the libaio part of the name. A similar
> > mistake happened on the Netty Project, when I tried to bring libaio
> > into netty. Their native library was for epoll at the time only and
> > that made things complicated at the time. They later made things more
> > generic but I never got to bring libaio there again (I don't think it
> > made sense for Netty).
> >
> > We  may have only libaio now, but I can foresee adding more things in
> > the future, like New APIs for future Storage.. future network..
> > dunno... I just like to keep the name open.
> >
> > If you don't like the name native that's fine.. but libaio is too
> > restrictive.
> >
> > On Wed, Jan 30, 2019 at 12:15 PM michael.andre.pearce
> > <mi...@me.com.invalid> wrote:
> > >
> > > Just on name front. I would call it activemq-libaio
> > > Native is a bit too generic, it could mean support for epoll, kqueue or
> > even cpp client also.
> > > Re vote, i think rather than a vote for this specific sub project. We
> > should decide on common guidelines for sub projects and rules for future,
> > for me its better we agree and vote on policies to make clear rules.
> > > E.g.
> > > We could be voting for a policy such as
> > > "a sub project is deemed a project that is supporting or adding to the
> > activemq ecosystem, a sub project can be created without the need for vote,
> > simply by the  support of a single pmc member or two committers sponsoring.
> > On creation a NOTICE should be sent to dev mailing lists"
> > > In such guideline / rule got voted on then this would obviously would
> > not need separate vote, as would have a pmc member sponsoring (yourself
> > clebert)
> > >
> > >
> > > Sent from my Samsung Galaxy smartphone.
> > > -------- Original message --------From: Francesco Nigro <
> > nigro.fra@gmail.com> Date: 30/01/2019  16:58  (GMT+00:00) To:
> > dev@activemq.apache.org Subject: Re: [DISCUSS] ActiveMQ Artemis Native as
> > a separated project
> > > +100 for this one and I would be pleased to do it, maybe with the help of
> > > both Clebert and Otavio  (that's quite good with native stuff!) :)
> > > Obviously Michael you know that you're more then welcome on it as well
> > eh,
> > > I'm just taking the initiative :D
> > >
> > > Il giorno mer 30 gen 2019 alle ore 17:51 michael.andre.pearce
> > > <mi...@me.com.invalid> ha scritto:
> > >
> > > > Tbh, i see nothing wrong with making it a mini sub project. If anything
> > > > having some sub projects is a good thing.
> > > > Would the supporting java code be moved also?
> > > > And would we look to make the interfaces more generic?
> > > > Im keen if we separate something thats currently tighly embedded in
> > > > artemis, we make sure it is much more re-usable (e.g. even example
> > > > alternative uses).
> > > > On that note, i think there are other bits that could be split out, a
> > bit
> > > > like what occured in activemq5.
> > > > E.g. spring integration, protocol manager, other extensions
> > > > And should welcome this a little more with newer extensions or features
> > > > that enhance activemq but not core broker.
> > > >
> > > >
> > > >
> > > > Sent from my Samsung Galaxy smartphone.
> > > > -------- Original message --------From: Clebert Suconic <
> > > > clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> > > > dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as
> > a
> > > > separated project
> > > > One of the modules of ActiveMQ Artemis is the Native Layer:
> > > >
> > > >
> > > >
> > https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
> > > >
> > > > We currently hold all JNI Calls (pretty much libaio ATM).
> > > >
> > > > It is stable and the release cycle is very long. Maybe one or two
> > > > changes an year with the current scope. This may become different if
> > > > we expand the scope of JNI operations supported by the broker).
> > > >
> > > > I would like to make it a separate git repository from ActiveMQ
> > > > Artemis, with its own releasy cycle. (we would even be able to remove
> > > > the currently .so that are currently checked in on artemis).  It is
> > > > the sensitive thing to do.
> > > >
> > > > I don't think it as a separate project, just as a separate repository
> > > > with its own release cycle to make things easier.
> > > >
> > > > I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> > > > it would be used for any further JNI operations needed for any other
> > > > Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> > > > but I would keep the door open for other JNI operations we may need.
> > > >
> > > >
> > > > I was wondering if anyone have any other ideas around it.
> > > >
> > > >
> > > > Also: Would we need a vote to proceed on such change after we reach a
> > > > consensus on what to do here?
> > > > --
> > > > Clebert Suconic
> > > >
> >
> >
> >
> > --
> > Clebert Suconic
> >



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Francesco Nigro <ni...@gmail.com>.
Re the naming: native would be a module for all the sub component sharing
native interfaces of any kind. I prefer that too even if, effectively ATM
we will have just libAIO on it...

Il giorno mer 30 gen 2019 alle ore 18:18 Clebert Suconic <
clebert.suconic@gmail.com> ha scritto:

> I would not like to make the libaio part of the name. A similar
> mistake happened on the Netty Project, when I tried to bring libaio
> into netty. Their native library was for epoll at the time only and
> that made things complicated at the time. They later made things more
> generic but I never got to bring libaio there again (I don't think it
> made sense for Netty).
>
> We  may have only libaio now, but I can foresee adding more things in
> the future, like New APIs for future Storage.. future network..
> dunno... I just like to keep the name open.
>
> If you don't like the name native that's fine.. but libaio is too
> restrictive.
>
> On Wed, Jan 30, 2019 at 12:15 PM michael.andre.pearce
> <mi...@me.com.invalid> wrote:
> >
> > Just on name front. I would call it activemq-libaio
> > Native is a bit too generic, it could mean support for epoll, kqueue or
> even cpp client also.
> > Re vote, i think rather than a vote for this specific sub project. We
> should decide on common guidelines for sub projects and rules for future,
> for me its better we agree and vote on policies to make clear rules.
> > E.g.
> > We could be voting for a policy such as
> > "a sub project is deemed a project that is supporting or adding to the
> activemq ecosystem, a sub project can be created without the need for vote,
> simply by the  support of a single pmc member or two committers sponsoring.
> On creation a NOTICE should be sent to dev mailing lists"
> > In such guideline / rule got voted on then this would obviously would
> not need separate vote, as would have a pmc member sponsoring (yourself
> clebert)
> >
> >
> > Sent from my Samsung Galaxy smartphone.
> > -------- Original message --------From: Francesco Nigro <
> nigro.fra@gmail.com> Date: 30/01/2019  16:58  (GMT+00:00) To:
> dev@activemq.apache.org Subject: Re: [DISCUSS] ActiveMQ Artemis Native as
> a separated project
> > +100 for this one and I would be pleased to do it, maybe with the help of
> > both Clebert and Otavio  (that's quite good with native stuff!) :)
> > Obviously Michael you know that you're more then welcome on it as well
> eh,
> > I'm just taking the initiative :D
> >
> > Il giorno mer 30 gen 2019 alle ore 17:51 michael.andre.pearce
> > <mi...@me.com.invalid> ha scritto:
> >
> > > Tbh, i see nothing wrong with making it a mini sub project. If anything
> > > having some sub projects is a good thing.
> > > Would the supporting java code be moved also?
> > > And would we look to make the interfaces more generic?
> > > Im keen if we separate something thats currently tighly embedded in
> > > artemis, we make sure it is much more re-usable (e.g. even example
> > > alternative uses).
> > > On that note, i think there are other bits that could be split out, a
> bit
> > > like what occured in activemq5.
> > > E.g. spring integration, protocol manager, other extensions
> > > And should welcome this a little more with newer extensions or features
> > > that enhance activemq but not core broker.
> > >
> > >
> > >
> > > Sent from my Samsung Galaxy smartphone.
> > > -------- Original message --------From: Clebert Suconic <
> > > clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> > > dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as
> a
> > > separated project
> > > One of the modules of ActiveMQ Artemis is the Native Layer:
> > >
> > >
> > >
> https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
> > >
> > > We currently hold all JNI Calls (pretty much libaio ATM).
> > >
> > > It is stable and the release cycle is very long. Maybe one or two
> > > changes an year with the current scope. This may become different if
> > > we expand the scope of JNI operations supported by the broker).
> > >
> > > I would like to make it a separate git repository from ActiveMQ
> > > Artemis, with its own releasy cycle. (we would even be able to remove
> > > the currently .so that are currently checked in on artemis).  It is
> > > the sensitive thing to do.
> > >
> > > I don't think it as a separate project, just as a separate repository
> > > with its own release cycle to make things easier.
> > >
> > > I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> > > it would be used for any further JNI operations needed for any other
> > > Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> > > but I would keep the door open for other JNI operations we may need.
> > >
> > >
> > > I was wondering if anyone have any other ideas around it.
> > >
> > >
> > > Also: Would we need a vote to proceed on such change after we reach a
> > > consensus on what to do here?
> > > --
> > > Clebert Suconic
> > >
>
>
>
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by "michael.andre.pearce" <mi...@me.com.INVALID>.
So i dislike native its just too generic for me.
I was just suggesting libaio an alternative. As i dont like saying no to something without supplying an alternative.
I am open to other options.


Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Clebert Suconic <cl...@gmail.com> Date: 30/01/2019  17:18  (GMT+00:00) To: dev@activemq.apache.org Subject: Re: [DISCUSS] ActiveMQ Artemis Native as a separated project 
I would not like to make the libaio part of the name. A similar
mistake happened on the Netty Project, when I tried to bring libaio
into netty. Their native library was for epoll at the time only and
that made things complicated at the time. They later made things more
generic but I never got to bring libaio there again (I don't think it
made sense for Netty).

We  may have only libaio now, but I can foresee adding more things in
the future, like New APIs for future Storage.. future network..
dunno... I just like to keep the name open.

If you don't like the name native that's fine.. but libaio is too restrictive.

On Wed, Jan 30, 2019 at 12:15 PM michael.andre.pearce
<mi...@me.com.invalid> wrote:
>
> Just on name front. I would call it activemq-libaio
> Native is a bit too generic, it could mean support for epoll, kqueue or even cpp client also.
> Re vote, i think rather than a vote for this specific sub project. We should decide on common guidelines for sub projects and rules for future, for me its better we agree and vote on policies to make clear rules.
> E.g.
> We could be voting for a policy such as
> "a sub project is deemed a project that is supporting or adding to the activemq ecosystem, a sub project can be created without the need for vote, simply by the  support of a single pmc member or two committers sponsoring. On creation a NOTICE should be sent to dev mailing lists"
> In such guideline / rule got voted on then this would obviously would not need separate vote, as would have a pmc member sponsoring (yourself clebert)
>
>
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: Francesco Nigro <ni...@gmail.com> Date: 30/01/2019  16:58  (GMT+00:00) To: dev@activemq.apache.org Subject: Re: [DISCUSS] ActiveMQ Artemis Native as a separated project
> +100 for this one and I would be pleased to do it, maybe with the help of
> both Clebert and Otavio  (that's quite good with native stuff!) :)
> Obviously Michael you know that you're more then welcome on it as well eh,
> I'm just taking the initiative :D
>
> Il giorno mer 30 gen 2019 alle ore 17:51 michael.andre.pearce
> <mi...@me.com.invalid> ha scritto:
>
> > Tbh, i see nothing wrong with making it a mini sub project. If anything
> > having some sub projects is a good thing.
> > Would the supporting java code be moved also?
> > And would we look to make the interfaces more generic?
> > Im keen if we separate something thats currently tighly embedded in
> > artemis, we make sure it is much more re-usable (e.g. even example
> > alternative uses).
> > On that note, i think there are other bits that could be split out, a bit
> > like what occured in activemq5.
> > E.g. spring integration, protocol manager, other extensions
> > And should welcome this a little more with newer extensions or features
> > that enhance activemq but not core broker.
> >
> >
> >
> > Sent from my Samsung Galaxy smartphone.
> > -------- Original message --------From: Clebert Suconic <
> > clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> > dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a
> > separated project
> > One of the modules of ActiveMQ Artemis is the Native Layer:
> >
> >
> > https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
> >
> > We currently hold all JNI Calls (pretty much libaio ATM).
> >
> > It is stable and the release cycle is very long. Maybe one or two
> > changes an year with the current scope. This may become different if
> > we expand the scope of JNI operations supported by the broker).
> >
> > I would like to make it a separate git repository from ActiveMQ
> > Artemis, with its own releasy cycle. (we would even be able to remove
> > the currently .so that are currently checked in on artemis).  It is
> > the sensitive thing to do.
> >
> > I don't think it as a separate project, just as a separate repository
> > with its own release cycle to make things easier.
> >
> > I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> > it would be used for any further JNI operations needed for any other
> > Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> > but I would keep the door open for other JNI operations we may need.
> >
> >
> > I was wondering if anyone have any other ideas around it.
> >
> >
> > Also: Would we need a vote to proceed on such change after we reach a
> > consensus on what to do here?
> > --
> > Clebert Suconic
> >



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Clebert Suconic <cl...@gmail.com>.
I would not like to make the libaio part of the name. A similar
mistake happened on the Netty Project, when I tried to bring libaio
into netty. Their native library was for epoll at the time only and
that made things complicated at the time. They later made things more
generic but I never got to bring libaio there again (I don't think it
made sense for Netty).

We  may have only libaio now, but I can foresee adding more things in
the future, like New APIs for future Storage.. future network..
dunno... I just like to keep the name open.

If you don't like the name native that's fine.. but libaio is too restrictive.

On Wed, Jan 30, 2019 at 12:15 PM michael.andre.pearce
<mi...@me.com.invalid> wrote:
>
> Just on name front. I would call it activemq-libaio
> Native is a bit too generic, it could mean support for epoll, kqueue or even cpp client also.
> Re vote, i think rather than a vote for this specific sub project. We should decide on common guidelines for sub projects and rules for future, for me its better we agree and vote on policies to make clear rules.
> E.g.
> We could be voting for a policy such as
> "a sub project is deemed a project that is supporting or adding to the activemq ecosystem, a sub project can be created without the need for vote, simply by the  support of a single pmc member or two committers sponsoring. On creation a NOTICE should be sent to dev mailing lists"
> In such guideline / rule got voted on then this would obviously would not need separate vote, as would have a pmc member sponsoring (yourself clebert)
>
>
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: Francesco Nigro <ni...@gmail.com> Date: 30/01/2019  16:58  (GMT+00:00) To: dev@activemq.apache.org Subject: Re: [DISCUSS] ActiveMQ Artemis Native as a separated project
> +100 for this one and I would be pleased to do it, maybe with the help of
> both Clebert and Otavio  (that's quite good with native stuff!) :)
> Obviously Michael you know that you're more then welcome on it as well eh,
> I'm just taking the initiative :D
>
> Il giorno mer 30 gen 2019 alle ore 17:51 michael.andre.pearce
> <mi...@me.com.invalid> ha scritto:
>
> > Tbh, i see nothing wrong with making it a mini sub project. If anything
> > having some sub projects is a good thing.
> > Would the supporting java code be moved also?
> > And would we look to make the interfaces more generic?
> > Im keen if we separate something thats currently tighly embedded in
> > artemis, we make sure it is much more re-usable (e.g. even example
> > alternative uses).
> > On that note, i think there are other bits that could be split out, a bit
> > like what occured in activemq5.
> > E.g. spring integration, protocol manager, other extensions
> > And should welcome this a little more with newer extensions or features
> > that enhance activemq but not core broker.
> >
> >
> >
> > Sent from my Samsung Galaxy smartphone.
> > -------- Original message --------From: Clebert Suconic <
> > clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> > dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a
> > separated project
> > One of the modules of ActiveMQ Artemis is the Native Layer:
> >
> >
> > https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
> >
> > We currently hold all JNI Calls (pretty much libaio ATM).
> >
> > It is stable and the release cycle is very long. Maybe one or two
> > changes an year with the current scope. This may become different if
> > we expand the scope of JNI operations supported by the broker).
> >
> > I would like to make it a separate git repository from ActiveMQ
> > Artemis, with its own releasy cycle. (we would even be able to remove
> > the currently .so that are currently checked in on artemis).  It is
> > the sensitive thing to do.
> >
> > I don't think it as a separate project, just as a separate repository
> > with its own release cycle to make things easier.
> >
> > I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> > it would be used for any further JNI operations needed for any other
> > Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> > but I would keep the door open for other JNI operations we may need.
> >
> >
> > I was wondering if anyone have any other ideas around it.
> >
> >
> > Also: Would we need a vote to proceed on such change after we reach a
> > consensus on what to do here?
> > --
> > Clebert Suconic
> >



-- 
Clebert Suconic

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by "michael.andre.pearce" <mi...@me.com.INVALID>.
Just on name front. I would call it activemq-libaio
Native is a bit too generic, it could mean support for epoll, kqueue or even cpp client also.
Re vote, i think rather than a vote for this specific sub project. We should decide on common guidelines for sub projects and rules for future, for me its better we agree and vote on policies to make clear rules.
E.g. 
We could be voting for a policy such as
"a sub project is deemed a project that is supporting or adding to the activemq ecosystem, a sub project can be created without the need for vote, simply by the  support of a single pmc member or two committers sponsoring. On creation a NOTICE should be sent to dev mailing lists"
In such guideline / rule got voted on then this would obviously would not need separate vote, as would have a pmc member sponsoring (yourself clebert)


Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Francesco Nigro <ni...@gmail.com> Date: 30/01/2019  16:58  (GMT+00:00) To: dev@activemq.apache.org Subject: Re: [DISCUSS] ActiveMQ Artemis Native as a separated project 
+100 for this one and I would be pleased to do it, maybe with the help of
both Clebert and Otavio  (that's quite good with native stuff!) :)
Obviously Michael you know that you're more then welcome on it as well eh,
I'm just taking the initiative :D

Il giorno mer 30 gen 2019 alle ore 17:51 michael.andre.pearce
<mi...@me.com.invalid> ha scritto:

> Tbh, i see nothing wrong with making it a mini sub project. If anything
> having some sub projects is a good thing.
> Would the supporting java code be moved also?
> And would we look to make the interfaces more generic?
> Im keen if we separate something thats currently tighly embedded in
> artemis, we make sure it is much more re-usable (e.g. even example
> alternative uses).
> On that note, i think there are other bits that could be split out, a bit
> like what occured in activemq5.
> E.g. spring integration, protocol manager, other extensions
> And should welcome this a little more with newer extensions or features
> that enhance activemq but not core broker.
>
>
>
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: Clebert Suconic <
> clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a
> separated project
> One of the modules of ActiveMQ Artemis is the Native Layer:
>
>
> https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
>
> We currently hold all JNI Calls (pretty much libaio ATM).
>
> It is stable and the release cycle is very long. Maybe one or two
> changes an year with the current scope. This may become different if
> we expand the scope of JNI operations supported by the broker).
>
> I would like to make it a separate git repository from ActiveMQ
> Artemis, with its own releasy cycle. (we would even be able to remove
> the currently .so that are currently checked in on artemis).  It is
> the sensitive thing to do.
>
> I don't think it as a separate project, just as a separate repository
> with its own release cycle to make things easier.
>
> I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> it would be used for any further JNI operations needed for any other
> Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> but I would keep the door open for other JNI operations we may need.
>
>
> I was wondering if anyone have any other ideas around it.
>
>
> Also: Would we need a vote to proceed on such change after we reach a
> consensus on what to do here?
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by Francesco Nigro <ni...@gmail.com>.
+100 for this one and I would be pleased to do it, maybe with the help of
both Clebert and Otavio  (that's quite good with native stuff!) :)
Obviously Michael you know that you're more then welcome on it as well eh,
I'm just taking the initiative :D

Il giorno mer 30 gen 2019 alle ore 17:51 michael.andre.pearce
<mi...@me.com.invalid> ha scritto:

> Tbh, i see nothing wrong with making it a mini sub project. If anything
> having some sub projects is a good thing.
> Would the supporting java code be moved also?
> And would we look to make the interfaces more generic?
> Im keen if we separate something thats currently tighly embedded in
> artemis, we make sure it is much more re-usable (e.g. even example
> alternative uses).
> On that note, i think there are other bits that could be split out, a bit
> like what occured in activemq5.
> E.g. spring integration, protocol manager, other extensions
> And should welcome this a little more with newer extensions or features
> that enhance activemq but not core broker.
>
>
>
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------From: Clebert Suconic <
> clebert.suconic@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To:
> dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a
> separated project
> One of the modules of ActiveMQ Artemis is the Native Layer:
>
>
> https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native
>
> We currently hold all JNI Calls (pretty much libaio ATM).
>
> It is stable and the release cycle is very long. Maybe one or two
> changes an year with the current scope. This may become different if
> we expand the scope of JNI operations supported by the broker).
>
> I would like to make it a separate git repository from ActiveMQ
> Artemis, with its own releasy cycle. (we would even be able to remove
> the currently .so that are currently checked in on artemis).  It is
> the sensitive thing to do.
>
> I don't think it as a separate project, just as a separate repository
> with its own release cycle to make things easier.
>
> I would like to name it ActiveMQ-Native, dropping the word Artemis, as
> it would be used for any further JNI operations needed for any other
> Java Projects part of ActiveMQ Artemis. We currently only have libaio,
> but I would keep the door open for other JNI operations we may need.
>
>
> I was wondering if anyone have any other ideas around it.
>
>
> Also: Would we need a vote to proceed on such change after we reach a
> consensus on what to do here?
> --
> Clebert Suconic
>

Re: [DISCUSS] ActiveMQ Artemis Native as a separated project

Posted by "michael.andre.pearce" <mi...@me.com.INVALID>.
Tbh, i see nothing wrong with making it a mini sub project. If anything having some sub projects is a good thing.
Would the supporting java code be moved also?
And would we look to make the interfaces more generic?
Im keen if we separate something thats currently tighly embedded in artemis, we make sure it is much more re-usable (e.g. even example alternative uses). 
On that note, i think there are other bits that could be split out, a bit like what occured in activemq5.
E.g. spring integration, protocol manager, other extensions
And should welcome this a little more with newer extensions or features that enhance activemq but not core broker.



Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Clebert Suconic <cl...@gmail.com> Date: 30/01/2019  16:31  (GMT+00:00) To: dev@activemq.apache.org Subject: [DISCUSS] ActiveMQ Artemis Native as a separated project 
One of the modules of ActiveMQ Artemis is the Native Layer:

https://github.com/apache/activemq-artemis/tree/056cee4183a048028c0a5417304eb89a540e1316/artemis-native

We currently hold all JNI Calls (pretty much libaio ATM).

It is stable and the release cycle is very long. Maybe one or two
changes an year with the current scope. This may become different if
we expand the scope of JNI operations supported by the broker).

I would like to make it a separate git repository from ActiveMQ
Artemis, with its own releasy cycle. (we would even be able to remove
the currently .so that are currently checked in on artemis).  It is
the sensitive thing to do.

I don't think it as a separate project, just as a separate repository
with its own release cycle to make things easier.

I would like to name it ActiveMQ-Native, dropping the word Artemis, as
it would be used for any further JNI operations needed for any other
Java Projects part of ActiveMQ Artemis. We currently only have libaio,
but I would keep the door open for other JNI operations we may need.


I was wondering if anyone have any other ideas around it.


Also: Would we need a vote to proceed on such change after we reach a
consensus on what to do here?
-- 
Clebert Suconic