[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] Fwd: Automatically generated bundles for Maven Central artifacts

The manifest quality issue is no different than with any other manifest. We believe we provide a meaningful default but it may not be optimal in all cases.
IMO, the tweaking of the manifest should be the result of a community / consumer effort, as the generation facility can actually be tweaked with having a different template. Of course ideally the jar would be bundle-ized directly by the producer, but that a different discussion :)

Here is the link to some ant tasks to download dependencies from maven repos:



On 2011-06-02, at 10:53 AM, Glyn Normington wrote:

> Hi Dmitry
> A very interesting development. I agree about the manifest quality risk, but at least the "friction" is virtually zero. I am told it is possible to download from a Maven repo in an Ant/Ivy build too.
> Regards,
> Glyn
> On 2 Jun 2011, at 14:43, Dmitry Sklyut wrote:
>> This is an interesting (see bellow).  Have not tried it and do not know quality of meta-data for these artifacts.
>> Regards,
>> Dmitry
>> ---------- Forwarded message ----------
>> From: Alin Dreghiciu <adreghiciu@xxxxxxxxx>
>> Date: Thu, Jun 2, 2011 at 9:36 AM
>> Subject: Automatically generated bundles for Maven Central artifacts
>> To: general@xxxxxxxxxxxxxxx
>> Hi,
>> If anyone interested in OSGi version of any of Maven Central artifacts
>> (jars) you can now get them by using the
>> http://grid.sonatype.org:9000/nexus/content/repositories/central/
>> repository.
>> The osgi bundles are created on demand, meaning that the jar will be
>> OSGi-fyed as soon as the first request for it. The generated OSGi
>> bundle will have the same Maven coordinates (group/artifact/version)
>> as the original non OSGI jar but it will have and "osgi" classifier.
>> You can use the bundle in a Maven build as for example:
>> <dependency>
>>  <groupId>commons-logging</groupId>
>>  <artifactId>commons-logging</artifactId>
>>  <version>1.1.1</version>
>>  <classifier>osgi</classifier>
>> </dependency>
>> If you want to directly download the bundle, the URL is similar to
>> original (non OSGi) version of jar with an additional "-osgi" added in
>> front of ".jar" extension as in the following example:
>> Original jar URL:
>> http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
>> OSGi bundle URL:
>> http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1-osgi.jar
>> If using Pax Maven URL (Pax runner, Karaf, ...) you can access the bundle as:
>> mvn:commons-logging/commons-logging/1.1.1/jar/osgi or
>> mvn:commons-logging/commons-logging/1.1.1//osgi
>> Of course that if the jar is already an OSGi bundle it will not be transformed.
>> All of this automatically transformed bundles and all existing bundles
>> accessed via the above mentioned repository are available also via OBR
>> at:
>> http://grid.sonatype.org:9000/nexus/content/shadows/central-obr/.meta/obr.xml
>> Soon I will als make this bundles available as an P2 repository.
>> Note that this is an "lab" project for now so things might change and
>> will have downtimes as I will upgrade them with latest builds of Nexus
>> plugins we develop for OSGi.
>> Feel free to send me your feedback about it so I can improve/fix it if
>> needed. Also same features could be enabled for other Maven
>> repositories out there.
>> --
>> Alin Dreghiciu
>> Software Developer
>> My profile: http://www.linkedin.com/in/alindreghiciu
>> My blog: http://adreghiciu.wordpress.com
>> http://sonatype.com - Sonatype - The Maven Company
>> http://www.ops4j.org - New Energy for OSS Communities - Open
>> Participation Software.
>> _______________________________________________
>> general mailing list
>> general@xxxxxxxxxxxxxxx
>> http://lists.ops4j.org/mailman/listinfo/general
>> _______________________________________________
>> virgo-dev mailing list
>> virgo-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/virgo-dev
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev