Re: Creating a central Maven repository for OSGi bundles
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating a central Maven repository for OSGi bundles
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating a central Maven repository for OSGi bundles
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating a central Maven repository for OSGi bundles
On 3/12/07, Brett Porter [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating a central Maven repository for OSGi bundles
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
