Return-Path: X-Original-To: apmail-felix-users-archive@minotaur.apache.org Delivered-To: apmail-felix-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8856102D0 for ; Thu, 2 Jan 2014 16:49:30 +0000 (UTC) Received: (qmail 61238 invoked by uid 500); 2 Jan 2014 16:49:29 -0000 Delivered-To: apmail-felix-users-archive@felix.apache.org Received: (qmail 61106 invoked by uid 500); 2 Jan 2014 16:49:29 -0000 Mailing-List: contact users-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@felix.apache.org Delivered-To: mailing list users@felix.apache.org Received: (qmail 61098 invoked by uid 99); 2 Jan 2014 16:49:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jan 2014 16:49:27 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of njbartlett@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-wg0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jan 2014 16:49:23 +0000 Received: by mail-wg0-f44.google.com with SMTP id a1so12463469wgh.11 for ; Thu, 02 Jan 2014 08:49:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type; bh=Bc6bteIi/JVMQfbS6QGtL+C1bG/HqCnB2Ijm7pTIz/0=; b=C8vlwZl6mDzVkPKqKlGGks7xriqn+ABZACq+PTAgVjal4nntr6T1839R2//EFKK9nA kB1eH/HhkoN3HFkiXJwlRrkqx7mbK44C7NANCfnfISvzURDW2WCYii/KjbjE4ruK3D62 8eaK4yatN3JAyBPK0ziQ4UbzuUUVqq/+iEpJFqzF+fk6tDEDjjQv6U3e8VARWjMaL/Rj lQpO/u+ZpnBerwFuhfc0B7Y7pUfrxxL3wjIxBHR/MrARgYCIeuzCekxM+gRS/XPirrVD 13l5PCQ2w7gZNRrvhSrWdeF5DNS+VW7dfc0ofFjH0Uo8gE+ZdtvRZ1CkPtYmPga/kkDV 8w2w== X-Received: by 10.194.170.133 with SMTP id am5mr32312426wjc.42.1388681342029; Thu, 02 Jan 2014 08:49:02 -0800 (PST) Received: from Applicative-3.local (cpc6-finc11-2-0-cust112.4-2.cable.virginm.net. [82.31.133.113]) by mx.google.com with ESMTPSA id qk7sm33311263wjc.19.2014.01.02.08.48.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Jan 2014 08:49:01 -0800 (PST) Date: Thu, 2 Jan 2014 16:47:52 +0000 From: Neil Bartlett To: users@felix.apache.org, David Bosschaert Message-ID: In-Reply-To: References: Subject: Re: Fwd: Generating a repository.xml for Felix OBR X-Mailer: Airmail (205) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="52c59877_79e2a9e3_1e6d" X-Virus-Checked: Checked by ClamAV on apache.org --52c59877_79e2a9e3_1e6d Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline That's true... I'd forgotten about the maven-bundle-plugin.=C2=A0Also the= plugin generates a repository.xml under =24HOME/.m2/repository for your = own projects every time you do mvn:install. Neil On 2 January 2014 at 16:27:44, David Bosschaert (david.bosschaert=40gmail= .com) wrote: Thanks Neil=21 That's useful information. =20 In the mean time I also found that you can generate OBR repository.xml =20 files via the maven-obr-plugin with the following command: =20 mvn org.apache.felix:maven-obr-plugin:1.2.0:install-file =20 -Dfile=3D -DgroupId=3D -DartifactId=3D =20 -Dversion=3D -Dpackaging=3Djar =20 -DobrRepository=3D.../somewhere/repository.xml =20 In the mean time I think it would be great to start supporting the =20 OSGi Repository spec in the =46elix Bundle Repository. I've created few =20 issues for that under: =20 https://issues.apache.org/jira/browse/=46ELIX-4368 =20 Cheers, =20 David =20 On 2 January 2014 15:16, Neil Bartlett wrote: =20 > Hi David, =20 > =20 > I'll let somebody else answer whether =46elix OBR can use the spec-comp= liant =20 > XML. As the maintainer of bindex I can tell you that the old R=46C112 f= ormat =20 > is still supported if you checkout the =22preR5=22 tag. You can also ge= t it as a =20 > zip/tarball from https://github.com/osgi/bindex/releases. =20 > =20 > If you are using bnd(tools) then the LocalIndexedRepo plugin will gener= ate =20 > either old-style OBR or new-style R5 spec compliant indexes, or indeed = both, =20 > by setting the type attribute to =22OBR=22. See =20 > http://bndtools.org/repositories.html=23local-indexed-repository =20 > =20 > Neil =20 > =20 > On 2 January 2014 at 14:01:41, David Bosschaert (david.bosschaert=40gma= il.com) =20 > wrote: =20 > =20 > Maybe a silly question, but what is the best way to generate a =20 > repository.xml file for =46elix OBR these days=3F I would simply like t= o =20 > generate one for a directory with bundles... =20 > The =46elix website suggests to use bindex =5B1=5D, but bindex generate= s =20 > OSGi spec-compliant xml files and these are different from what =46elix= =20 > OBR supports. Or am I wrong and can I use spec-compliant =20 > repository.xml files at with =46elix OBR right now=3F =20 > =20 > Thanks, =20 > =20 > David =20 > =20 > =5B1=5D http://felix.apache.org/site/apache-felix-sigil-obr.html =20 > =20 > --------------------------------------------------------------------- =20 > To unsubscribe, e-mail: users-unsubscribe=40felix.apache.org =20 > =46or additional commands, e-mail: users-help=40felix.apache.org =20 > =20 --------------------------------------------------------------------- =20 To unsubscribe, e-mail: users-unsubscribe=40felix.apache.org =20 =46or additional commands, e-mail: users-help=40felix.apache.org =20 --52c59877_79e2a9e3_1e6d--