Received: by 10.58.246.37 with SMTP id xt5mr3447461vec.13.1350911741815;
        Mon, 22 Oct 2012 06:15:41 -0700 (PDT)
X-BeenThere: protobuf@googlegroups.com
Received: by 10.52.20.7 with SMTP id j7ls4455868vde.0.gmail; Mon, 22 Oct 2012
 06:15:39 -0700 (PDT)
Received: by 10.58.127.226 with SMTP id nj2mr3434639veb.3.1350911739930;
        Mon, 22 Oct 2012 06:15:39 -0700 (PDT)
Received: by 10.58.127.226 with SMTP id nj2mr3434638veb.3.1350911739920;
        Mon, 22 Oct 2012 06:15:39 -0700 (PDT)
Return-Path: <3-0aFUAgOCCgTVSXSFYJKSSKPIGSHI.GSQTVSXSFYJKSSKPIKVSYTW....@codesite.bounces.google.com>
Received: from mail-vb0-f75.google.com (mail-vb0-f75.google.com [209.85.212.75])
        by gmr-mx.google.com with ESMTPS id dj17si2314766vdb.1.2012.10.22.06.15.39
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 22 Oct 2012 06:15:39 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3-0aFUAgOCCgTVSXSFYJKSSKPIGSHI.GSQTVSXSFYJKSSKPIKVSYTW....@codesite.bounces.google.com designates 209.85.212.75 as permitted sender) client-ip=209.85.212.75;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3-0aFUAgOCCgTVSXSFYJKSSKPIGSHI.GSQTVSXSFYJKSSKPIKVSYTW....@codesite.bounces.google.com designates 209.85.212.75 as permitted sender) smtp.mail=3-0aFUAgOCCgTVSXSFYJKSSKPIGSHI.GSQTVSXSFYJKSSKPIKVSYTW....@codesite.bounces.google.com
Received: by mail-vb0-f75.google.com with SMTP id fr13so16081vbb.4
        for <protobuf@googlegroups.com>; Mon, 22 Oct 2012 06:15:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.180.141 with SMTP id bu13mr1918129qab.2.1350911739713;
 Mon, 22 Oct 2012 06:15:39 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: protobuf
X-GoogleCode-Issue-Id: 298
References: <17-13244680660385734572-7877252497521876740-protobuf=googlecode.com@googlecode.com>
 <0-13244680660385734572-7877252497521876740-protobuf=googlecode.com@googlecode.com>
In-Reply-To: <17-13244680660385734572-7877252497521876740-protobuf=googlecode.com@googlecode.com>
Message-ID: <18-13244680660385734572-7877252497521876740-protobuf=googlecode....@googlecode.com>
Date: Mon, 22 Oct 2012 13:15:39 +0000
Subject: Re: Issue 298 in protobuf: protobuf jar's manifest should include
 OSGi metadata
From: proto...@googlecode.com
To: protobuf@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes


Comment #18 on issue 298 by rocketra...@gmail.com: protobuf jar's manifest  
should include OSGi metadata
http://code.google.com/p/protobuf/issues/detail?id=298

"it doesn't seem right to me that we should change protobuf to make it  
conform to the specification of a certain container." --> In addition to  
the other comments, I might also note that, to be completey accurate, you  
aren't really *changing* protobuf as such. Rather you are *adding* support  
for many containers and applications that use OSGi meta-data. And the good  
part is that this addition is trivial and completely compatible with  
non-OSGi containers and applications.