From dev-return-69629-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Wed Jan 30 17:14:44 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4FCBB180652 for ; Wed, 30 Jan 2019 18:14:44 +0100 (CET) Received: (qmail 86237 invoked by uid 500); 30 Jan 2019 17:14:43 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 86224 invoked by uid 99); 30 Jan 2019 17:14:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2019 17:14:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3AD10180A7D for ; Wed, 30 Jan 2019 17:14:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.2 X-Spam-Level: X-Spam-Status: No, score=-0.2 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id hEPU0ZYyybTE for ; Wed, 30 Jan 2019 17:14:40 +0000 (UTC) Received: from mail-pl1-f193.google.com (mail-pl1-f193.google.com [209.85.214.193]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C358E5F180 for ; Wed, 30 Jan 2019 17:14:39 +0000 (UTC) Received: by mail-pl1-f193.google.com with SMTP id b5so111828plr.4 for ; Wed, 30 Jan 2019 09:14:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=UnJK5tmCzP3shlfzgsrqY+NtNgPZc2KmqaAzRCGEBNU=; b=F6XFAvZOOOpeK3dPPlXjCFoOco/pG1LlWSbFtiNbOJ+AWUMWuAiS3jLBGVu45ksi2d WRAcwUUsRKnb9j3A29a64N6ZS9i/J1w+uFf8ubvjbnarK7QR0GQJty73fI+rFHw2CI13 ekypis67xRx2JcZauiTsZ8uea4TO6BvWZp2rhDsTYnINV8905XfWpiY4pHzrcZEMf1aj 9EwGhLA6RpIjjSskve6jaXr6B5LhqntC4QeFdb82GwyHllSf+ah/kDiDwKos41UcrE8Q /YsvYY1NKXKm18HGlz2FidXIo5/f9jBV2tnl3G0ApfrAD5pLD/zcTjjfRClKtNWHENd5 TQMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=UnJK5tmCzP3shlfzgsrqY+NtNgPZc2KmqaAzRCGEBNU=; b=SkkD7PMg+HRFp+9OgEWFyUqBKy7iuyavEwebFT8LqCl5G4x1EoHiKzq/2RrVshi7i1 ITTXjyN0ydqqGvyNjdwxas9yVftQG940lGy2OBGyRl2P+vz/YgSdu5wk9mjIOwpHrqSx M2pUtpLBmCdTmdSeS8FlZf5KzhVPOvUATcio3vpzCXKmTtOF9LRTvM+BMUrh8fr/qUje u5ygDgtjIbk000x2FzjjycX5RiRrMhEvbVdNnHILfwlwz8LEu1f0kx+x2tJf3li8HWRi Omfav28EvQoPVK+FkuaGMm740DMRIT8h/plOGcOUkceIWvL2QJWx9FEjKaiyOSq+aCwN +TfA== X-Gm-Message-State: AJcUukf0bZxiWyHRcK7YKGo7WifJVVFptIUkPfqzxW8SZX2iG8DU15A8 WZBXbbHD6JDirj3xQDstmwQALZz40EX2e3ibPFPNyA== X-Google-Smtp-Source: ALg8bN4mc1gIWiAUiIFZCZlxZgHQyLwPeoLqFbGrTe8Ty2VH+6ad3J3Ugn21iXfBiV+cOb2rTO7J6l2ljDSBO0WjFpI= X-Received: by 2002:a17:902:76cb:: with SMTP id j11mr31957227plt.179.1548868478070; Wed, 30 Jan 2019 09:14:38 -0800 (PST) MIME-Version: 1.0 References: <5c51d62d.1c69fb81.b41cc.db8dSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: <5c51d62d.1c69fb81.b41cc.db8dSMTPIN_ADDED_MISSING@mx.google.com> From: Clebert Suconic Date: Wed, 30 Jan 2019 12:14:26 -0500 Message-ID: Subject: Re: [DISCUSS] ActiveMQ Artemis Native as a separated project To: dev@activemq.apache.org Content-Type: text/plain; charset="UTF-8" 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 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 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