You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Carlos Sanchez <ca...@apache.org> on 2007/03/13 00:46:57 UTC

Creating a central Maven repository for OSGi bundles

There are some initiatives like Apache Felix about repackaging
libraries from the maven repository until projects themselves include
the OSGi manifest.

It makes sense in the meantime to have a Maven repo with same
structure but with OSGi bundles. This repo would be temporal and
things could change over the time until it's stable.

There was already a temporal repo from eclipse installation in
http://repo1.maven.org/eclipse/ Artifacts there can go into central
with one change, bundle id = groupId + artifactId, meaning that they
are going to be stored in the repo with different name than they are
in the eclipse installation.
eg. org.eclipse.equinox.common will be group=org.eclipse.equinox artifact=common

About infrastructure, we'd need to know if maven.org has enough
bandwidth to host it or we need to look for alternatives. I'm gonna
run it also through infra@apache to see if we can have apache
artifacts in apache machines and sync as we do with the usual maven
repo.

comments?

-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

Re: Creating a central Maven repository for OSGi bundles

Posted by Carlos Sanchez <ca...@apache.org>.
On 3/12/07, Brett Porter <br...@apache.org> wrote:
> Is this going to result in a copy of all the artifacts with added
> bundled metadata?
>
> Will the structure will be same? Just wondering if the bundles should
> just be included in the main repository with a classifier.

this is going to be a "beta" so i wanted to make clear the distinction
between central where nothing can change and the OSGi repo where we
will be mostly testing the definitive stuff

>
> - Brett
>
> On 12/03/2007, at 4:46 PM, Carlos Sanchez wrote:
>
> > There are some initiatives like Apache Felix about repackaging
> > libraries from the maven repository until projects themselves include
> > the OSGi manifest.
> >
> > It makes sense in the meantime to have a Maven repo with same
> > structure but with OSGi bundles. This repo would be temporal and
> > things could change over the time until it's stable.
> >
> > There was already a temporal repo from eclipse installation in
> > http://repo1.maven.org/eclipse/ Artifacts there can go into central
> > with one change, bundle id = groupId + artifactId, meaning that they
> > are going to be stored in the repo with different name than they are
> > in the eclipse installation.
> > eg. org.eclipse.equinox.common will be group=org.eclipse.equinox
> > artifact=common
> >
> > About infrastructure, we'd need to know if maven.org has enough
> > bandwidth to host it or we need to look for alternatives. I'm gonna
> > run it also through infra@apache to see if we can have apache
> > artifacts in apache machines and sync as we do with the usual maven
> > repo.
> >
> > comments?
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> >                             -- The Princess Bride
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Creating a central Maven repository for OSGi bundles

Posted by Brett Porter <br...@apache.org>.
Is this going to result in a copy of all the artifacts with added  
bundled metadata?

Will the structure will be same? Just wondering if the bundles should  
just be included in the main repository with a classifier.

- Brett

On 12/03/2007, at 4:46 PM, Carlos Sanchez wrote:

> There are some initiatives like Apache Felix about repackaging
> libraries from the maven repository until projects themselves include
> the OSGi manifest.
>
> It makes sense in the meantime to have a Maven repo with same
> structure but with OSGi bundles. This repo would be temporal and
> things could change over the time until it's stable.
>
> There was already a temporal repo from eclipse installation in
> http://repo1.maven.org/eclipse/ Artifacts there can go into central
> with one change, bundle id = groupId + artifactId, meaning that they
> are going to be stored in the repo with different name than they are
> in the eclipse installation.
> eg. org.eclipse.equinox.common will be group=org.eclipse.equinox  
> artifact=common
>
> About infrastructure, we'd need to know if maven.org has enough
> bandwidth to host it or we need to look for alternatives. I'm gonna
> run it also through infra@apache to see if we can have apache
> artifacts in apache machines and sync as we do with the usual maven
> repo.
>
> comments?
>
> -- 
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
>                             -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Creating a central Maven repository for OSGi bundles

Posted by Ole Ersoy <ol...@gmail.com>.
It processes all jar artifacts contained in a repo.

So if the repo it points to contains the whole maven repo, it will do 
the whole thing.


Carlos Sanchez wrote:
> there's already a bundleall goal in the felix bundle plugin that will
> generate osgi bundles for each dependency in the tree
> https://issues.apache.org/jira/browse/FELIX-199
>
> are you processing the whole repo or just a tree of dependencies
>
> On 3/13/07, Ole Ersoy <ol...@gmail.com> wrote:
>> Hi Carloz,
>>
>> Just in case you need a mojo to process the repository,
>> I'm almost done with this RPM Factory mojo.
>>
>> I'm going to use it to RPM the maven repository, but
>> with a little modification, it could be used to create and add
>> manifests to all the jars in the maven repository as well.
>>
>> I'll probably have the RPM factory in my sandbox tomorrow some time,
>> if you are interested.
>>
>> Cheers,
>> - Ole
>>
>>
>>
>> Carlos Sanchez wrote:
>> > There are some initiatives like Apache Felix about repackaging
>> > libraries from the maven repository until projects themselves include
>> > the OSGi manifest.
>> >
>> > It makes sense in the meantime to have a Maven repo with same
>> > structure but with OSGi bundles. This repo would be temporal and
>> > things could change over the time until it's stable.
>> >
>> > There was already a temporal repo from eclipse installation in
>> > http://repo1.maven.org/eclipse/ Artifacts there can go into central
>> > with one change, bundle id = groupId + artifactId, meaning that they
>> > are going to be stored in the repo with different name than they are
>> > in the eclipse installation.
>> > eg. org.eclipse.equinox.common will be group=org.eclipse.equinox
>> > artifact=common
>> >
>> > About infrastructure, we'd need to know if maven.org has enough
>> > bandwidth to host it or we need to look for alternatives. I'm gonna
>> > run it also through infra@apache to see if we can have apache
>> > artifacts in apache machines and sync as we do with the usual maven
>> > repo.
>> >
>> > comments?
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Creating a central Maven repository for OSGi bundles

Posted by Carlos Sanchez <ca...@apache.org>.
there's already a bundleall goal in the felix bundle plugin that will
generate osgi bundles for each dependency in the tree
https://issues.apache.org/jira/browse/FELIX-199

are you processing the whole repo or just a tree of dependencies

On 3/13/07, Ole Ersoy <ol...@gmail.com> wrote:
> Hi Carloz,
>
> Just in case you need a mojo to process the repository,
> I'm almost done with this RPM Factory mojo.
>
> I'm going to use it to RPM the maven repository, but
> with a little modification, it could be used to create and add
> manifests to all the jars in the maven repository as well.
>
> I'll probably have the RPM factory in my sandbox tomorrow some time,
> if you are interested.
>
> Cheers,
> - Ole
>
>
>
> Carlos Sanchez wrote:
> > There are some initiatives like Apache Felix about repackaging
> > libraries from the maven repository until projects themselves include
> > the OSGi manifest.
> >
> > It makes sense in the meantime to have a Maven repo with same
> > structure but with OSGi bundles. This repo would be temporal and
> > things could change over the time until it's stable.
> >
> > There was already a temporal repo from eclipse installation in
> > http://repo1.maven.org/eclipse/ Artifacts there can go into central
> > with one change, bundle id = groupId + artifactId, meaning that they
> > are going to be stored in the repo with different name than they are
> > in the eclipse installation.
> > eg. org.eclipse.equinox.common will be group=org.eclipse.equinox
> > artifact=common
> >
> > About infrastructure, we'd need to know if maven.org has enough
> > bandwidth to host it or we need to look for alternatives. I'm gonna
> > run it also through infra@apache to see if we can have apache
> > artifacts in apache machines and sync as we do with the usual maven
> > repo.
> >
> > comments?
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Creating a central Maven repository for OSGi bundles

Posted by Ole Ersoy <ol...@gmail.com>.
Hi Carloz,

Just in case you need a mojo to process the repository,
I'm almost done with this RPM Factory mojo.

I'm going to use it to RPM the maven repository, but
with a little modification, it could be used to create and add
manifests to all the jars in the maven repository as well.

I'll probably have the RPM factory in my sandbox tomorrow some time,
if you are interested.

Cheers,
- Ole



Carlos Sanchez wrote:
> There are some initiatives like Apache Felix about repackaging
> libraries from the maven repository until projects themselves include
> the OSGi manifest.
>
> It makes sense in the meantime to have a Maven repo with same
> structure but with OSGi bundles. This repo would be temporal and
> things could change over the time until it's stable.
>
> There was already a temporal repo from eclipse installation in
> http://repo1.maven.org/eclipse/ Artifacts there can go into central
> with one change, bundle id = groupId + artifactId, meaning that they
> are going to be stored in the repo with different name than they are
> in the eclipse installation.
> eg. org.eclipse.equinox.common will be group=org.eclipse.equinox 
> artifact=common
>
> About infrastructure, we'd need to know if maven.org has enough
> bandwidth to host it or we need to look for alternatives. I'm gonna
> run it also through infra@apache to see if we can have apache
> artifacts in apache machines and sync as we do with the usual maven
> repo.
>
> comments?
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Creating a central Maven repository for OSGi bundles

Posted by Carlos Sanchez <ca...@apache.org>.
On 3/13/07, Upayavira <uv...@odoko.co.uk> wrote:
>
> repo1.maven.org is currently not ASF infrastructure. It is a setup run
> by Jason van Zyl, a Maven committer.
>
> You would be best off, as you have already, taking this to dev@maven
> rather than infra@ who would not have anything to say on the subject at
> this point in time.

I know, infra would need to be involved if we want to create an apache
repo to sync to central repo as we do right now with
http://people.apache.org/repo/m2-ibiblio-rsync-repository/ so apache
people can publish there directly, specially thinking about bundles
made by felix

>
> Regards, Upayavira
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

Re: Creating a central Maven repository for OSGi bundles

Posted by Upayavira <uv...@odoko.co.uk>.
Carlos Sanchez wrote:
> There are some initiatives like Apache Felix about repackaging
> libraries from the maven repository until projects themselves include
> the OSGi manifest.
> 
> It makes sense in the meantime to have a Maven repo with same
> structure but with OSGi bundles. This repo would be temporal and
> things could change over the time until it's stable.
> 
> There was already a temporal repo from eclipse installation in
> http://repo1.maven.org/eclipse/ Artifacts there can go into central
> with one change, bundle id = groupId + artifactId, meaning that they
> are going to be stored in the repo with different name than they are
> in the eclipse installation.
> eg. org.eclipse.equinox.common will be group=org.eclipse.equinox 
> artifact=common
> 
> About infrastructure, we'd need to know if maven.org has enough
> bandwidth to host it or we need to look for alternatives. I'm gonna
> run it also through infra@apache to see if we can have apache
> artifacts in apache machines and sync as we do with the usual maven
> repo.

repo1.maven.org is currently not ASF infrastructure. It is a setup run 
by Jason van Zyl, a Maven committer.

You would be best off, as you have already, taking this to dev@maven 
rather than infra@ who would not have anything to say on the subject at 
this point in time.

Regards, Upayavira