Received: by 10.236.35.66 with SMTP id t42mr6133563yha.10.1350921300856;
        Mon, 22 Oct 2012 08:55:00 -0700 (PDT)
X-BeenThere: protobuf@googlegroups.com
Received: by 10.236.139.40 with SMTP id b28ls5333037yhj.3.gmail; Mon, 22 Oct
 2012 08:54:59 -0700 (PDT)
Received: by 10.236.117.66 with SMTP id i42mr6503780yhh.8.1350921299064;
        Mon, 22 Oct 2012 08:54:59 -0700 (PDT)
Received: by 10.236.117.66 with SMTP id i42mr6503779yhh.8.1350921299052;
        Mon, 22 Oct 2012 08:54:59 -0700 (PDT)
Return-Path: <3UmyFUAgOCMk46383q9uv33v0tr3st.r3146383q9uv33v0tv63947....@codesite.bounces.google.com>
Received: from mail-gh0-f203.google.com (mail-gh0-f203.google.com [209.85.160.203])
        by gmr-mx.google.com with ESMTPS id i27si827377yhe.4.2012.10.22.08.54.59
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 22 Oct 2012 08:54:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3UmyFUAgOCMk46383q9uv33v0tr3st.r3146383q9uv33v0tv63947....@codesite.bounces.google.com designates 209.85.160.203 as permitted sender) client-ip=209.85.160.203;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of 3UmyFUAgOCMk46383q9uv33v0tr3st.r3146383q9uv33v0tv63947....@codesite.bounces.google.com designates 209.85.160.203 as permitted sender) smtp.mail=3UmyFUAgOCMk46383q9uv33v0tr3st.r3146383q9uv33v0tv63947....@codesite.bounces.google.com
Received: by mail-gh0-f203.google.com with SMTP id g24so579716ghb.4
        for <protobuf@googlegroups.com>; Mon, 22 Oct 2012 08:54:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.193.72 with SMTP id dt8mr6089117qab.7.1350921298965; Mon,
 22 Oct 2012 08:54:58 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: protobuf
X-GoogleCode-Issue-Id: 298
References: <22-13244680660385734572-7877252497521876740-protobuf=googlecode.com@googlecode.com>
 <0-13244680660385734572-7877252497521876740-protobuf=googlecode.com@googlecode.com>
In-Reply-To: <22-13244680660385734572-7877252497521876740-protobuf=googlecode.com@googlecode.com>
Message-ID: <23-13244680660385734572-7877252497521876740-protobuf=googlecode....@googlecode.com>
Date: Mon, 22 Oct 2012 15:54:58 +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 #23 on issue 298 by cjdo...@gmail.com: protobuf jar's manifest  
should include OSGi metadata
http://code.google.com/p/protobuf/issues/detail?id=298

Re: "Is it the suggested way to add OSGi meta data to every Java jar?" Yes.  
Increased modularity is Java's future, and OSGi is the dominant mechanism  
for modularity today. It's trivial to support it and it's very popular.  
Adding these few header values can increase protobuf's reach with almost no  
work.