Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A918110D4E for ; Sat, 28 Sep 2013 06:50:40 +0000 (UTC) Received: (qmail 17692 invoked by uid 500); 28 Sep 2013 06:46:27 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 17596 invoked by uid 500); 28 Sep 2013 06:45:18 -0000 Mailing-List: contact dev-help@stratos.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.incubator.apache.org Delivered-To: mailing list dev@stratos.incubator.apache.org Received: (qmail 17472 invoked by uid 99); 28 Sep 2013 06:45:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Sep 2013 06:45:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,LOTS_OF_MONEY,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul@wso2.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Sep 2013 06:45:01 +0000 Received: by mail-qc0-f179.google.com with SMTP id l4so2368613qcv.10 for ; Fri, 27 Sep 2013 23:44:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=VVVYC6S7PicZfqn4S1/XSDr855eA/Bkp8jY7LIug3DA=; b=M2PHsha+84DawfTYDxCdgtlCvU9TXinM27YPutGb6XWDqyW9mYKa92c3K3gvbZx9Ib qnUexAx6nmCnxZFUp4LSCw/cQp+xkbbrhfuX2Pz5e8Qa1OeMGq7fUZRjg8VVlYXjrV7W cK9lFY3M7bheqzf3PnSdlmsLfR1l0HTb8FCr0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=VVVYC6S7PicZfqn4S1/XSDr855eA/Bkp8jY7LIug3DA=; b=FeYpBwb1jBQYuTAy8j6n4DT3uVNtL7MfHEr6NG8zzyBLZFy+jXXHlrVSh9xeV4qXuG 63ipFs+dHwxoE5FIkKwX7Py7NHEUc7Bxmd9FWz3YYBOWF3H5txMtl78S3ODFARHKIp9C l/NnnAfduvlTqSZHbfR3786tVsPImGbCgrFJwxnViWid9eRB89gsybVA1xmP4zwPyv2X yIecFVR2JqH1vqoZ8l3n8hFTXr9Io69jhqyoCOs+N83/RE/2tKvlOu6pmgQ4LqZdjZCj bsTM+D9EVQ0kBkyHo2me6JfDdM0tTV8Lolk0c2eBtJbN6s2iukoeQ2UcNrWCTNM1l85o HTZQ== X-Gm-Message-State: ALoCoQlSIlQA3CV/slHgFptYL+o52s3aQ058tXP+WQFDTpDuThNtj2XDMMQn+B0LGLmfgSXjus4Y X-Received: by 10.49.95.135 with SMTP id dk7mr13920549qeb.3.1380350679463; Fri, 27 Sep 2013 23:44:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.171.135 with HTTP; Fri, 27 Sep 2013 23:43:58 -0700 (PDT) In-Reply-To: References: From: Paul Fremantle Date: Sat, 28 Sep 2013 07:43:58 +0100 Message-ID: Subject: Re: Shipping source as a complete pack for Apache Stratos incubating release To: dev@stratos.incubator.apache.org Content-Type: multipart/alternative; boundary=047d7b677f0cea5b3e04e76bef52 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b677f0cea5b3e04e76bef52 Content-Type: text/plain; charset=ISO-8859-1 Yes a single source code file is completely acceptable - and in this case the right thing to do. We should be clear in the README and on the website that this source code builds all the released binary artifacts, and it must be easy to do that. Paul On 28 September 2013 04:46, Imesh Gunaratne wrote: > Hi Lahiru, > > Yes as Lakmal has suggested I think it should be ok to ship one source > package with several binary packages. > > Since Stratos is built on a single platform with multiple products if we > were to create separate source packages we might need to duplicate > component source code in different product source packages. Therefore I > guess it should be cleaner to ship one source package. > > WDYT? > > Thanks > > > On Sat, Sep 28, 2013 at 8:55 AM, Lakmal Warusawithana wrote: > >> I think that's fine. >> >> sent from phone >> On Sep 28, 2013 7:45 AM, "Lahiru Sandaruwan" wrote: >> >>> Hi all, >>> >>> I just want to get clarified $subject. >>> Apache Stratos products are based on Osgi components and hence develop >>> as components, features, products source separately. >>> So products directory only does an assembling of features. Therefore if >>> we ship products directory, it doesn't contain real source. >>> >>> Is it fine to ship complete source without shipping products as separate >>> source packs? >>> >>> Thanks. >>> >>> -- >>> -- >>> Lahiru Sandaruwan >>> Software Engineer, >>> Platform Technologies, >>> WSO2 Inc., http://wso2.com >>> lean.enterprise.middleware >>> >>> email: lahirus@wso2.com cell: (+94) 773 325 954 >>> blog: http://lahiruwrites.blogspot.com/ >>> twitter: http://twitter.com/lahirus >>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>> >>> > > > -- > *Imesh Gunaratne* > Technical Lead > WSO2 Inc | http://wso2.com > T: +94 11 214 5345 | M: +94 77 374 2057 > W: http://imesh.gunaratne.org > Lean . Enterprise . Middleware > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, Apache Member UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo paul@wso2.com wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. --047d7b677f0cea5b3e04e76bef52 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Yes a single source code file is completely acceptable - a= nd in this case the right thing to do. We should be clear in the README and= on the website that this source code builds all the released binary artifa= cts, and it must be easy to do that.

Paul


On 28 September 2013 04:46, Imesh Gunaratne <imesh@wso2.com= > wrote:
Hi Lahiru,
Yes as Lakmal has suggested I think it should be ok to ship one sour= ce package with several binary packages.

Since Stratos is built on a single platform with multiple products if w= e were to create separate source packages we might need to duplicate compon= ent source code in different product source packages. Therefore I guess it = should be cleaner to ship one source package.

WDYT?

Thanks


On S= at, Sep 28, 2013 at 8:55 AM, Lakmal Warusawithana <lakmal@wso2.com> wrote:

I think that's fine.

sent from phone

On Sep 28, 2013 7:45 AM, "Lahiru Sandaruwan= " <lahirus@ws= o2.com> wrote:
Hi all,

I just want to get clarified $s= ubject.
Apache Stratos products are based on Osgi components and = hence develop as components, features, products source separately.=A0
So products directory only does an assembling of features. Therefore if we = ship products directory, it doesn't contain real source.

=
Is it fine to ship complete source without shipping products as = separate source packs?

Thanks.

--
--
Lahiru Sandaruwan
S= oftware Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: lahirus@wso2.com cell: (+94) 773 325 95= 4
blog: http:= //lahiruwrites.blogspot.com/
twitter: http://tw= itter.com/lahirus
linked-in: http://lk.linkedin.com/pub/l= ahiru-sandaruwan/16/153/146




--
Imesh Gunaratne
Technical Lea= d
WSO2 Inc |=A0http://wso2.com<= /a>
T: +94 11 214 5345 | M: +94 77 374 2057
W: http://imesh.gu= naratne.org
Lean . Enterprise . Middleware


--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair,= Apache Member

UK: +44 207 096 0336
US: +1 646 595 7= 614

blog: http://pzf= .fremantle.org
twitter.com/pzfreo
paul@wso2.com

wso2.com L= ean Enterprise Middleware

Disclaimer: This communication may contain= privileged or other confidential information and is intended exclusively f= or the addressee/s. If you are not the intended recipient/s, or believe tha= t you may have received this communication in error, please reply to the se= nder indicating that fact and delete the copy you received and in addition,= you should not print, copy, retransmit, disseminate, or otherwise use the = information contained in this communication. Internet communications cannot= be guaranteed to be timely, secure, error or virus-free. The sender does n= ot accept liability for any errors or omissions.
--047d7b677f0cea5b3e04e76bef52--