You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by "peter.doornbosch" <pe...@gmail.com> on 2008/05/09 11:33:34 UTC
obr for felix bundles?
Hi,
I wonder if there is an obr repository for the (current versions of
the) felix bundles. When i start felix (1.0.4), obr is configured with
the url http://oscar-osgi.sourceforge.net/obr2/repository.xml, which
contains only a few really old bundles....
Regards,
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Clement Escoffier wrote:
> Hi,
>
> By using the maven-bundle-plugin and specially OBR releated features, it is
> really easy to create this kind of repository automatically.
> I just create a pom file at the root of the releases directory. This pom
> file contains the "genuine" bundle modules (genuine in the sense that some
> artifacts are created as a bundle but are not real bundles as the framework
> artifact). [Note: the reactor can contain only one version of each
> artifact].
>
> Once created, I just launch the following command:
> mvn deploy org.apache.felix:maven-bundle-plugin:deploy
> -DaltDeploymentRepository=plop-plop.felix.releases::default::ftp://plop-plop
> .net -DremoteOBR=enable
>
> We add to use an alternative repository as the default repository is the
> Apache Maven one. Moreover, by default the remote OBR feature is disable, so
> we just need to enable it.
>
> It creates a maven repository and the OBR description file:
> http://plop-plop.net/obr/
> http://plop-plop.net/obr/repository.xml
>
> This step could become something to do during the release process.
>
I think this sounds reasonable. So, the question becomes, where can we
generate this repository?
-> richard
> Clement
>
>
>
>
>> -----Message d'origine-----
>> De : Richard S. Hall [mailto:heavy@ungoverned.org]
>> Envoyé : vendredi 9 mai 2008 10:11
>> À : users@felix.apache.org; dev@felix.apache.org
>> Objet : Re: obr for felix bundles?
>>
>> There currently is not. We definitely need this. It basically involves
>> determining at least two things:
>>
>> 1. How should we go about generating the repo?
>> * We have the capability to generate OBR repository files,
>> but
>> how do we get one generated for our current set of released
>> bundle versions?
>> 2. Where do we put the repository?
>>
>> I don't really know the best way to do (1). As for (2), I am not sure
>> if
>> it matters, I don't think it needs to be hosted on our Apache site. I
>> could put the repo on my own personal web site or we could just put
>> them
>> on the Source Forge web site.
>>
>> -> richard
>>
>> p.s. Sorry to cross post, it is not necessary to cross post replies...I
>> just want to make sure that this discussion is seen on the dev list.
>>
>> peter.doornbosch wrote:
>>
>>> Hi,
>>>
>>> I wonder if there is an obr repository for the (current versions of
>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>>>
>> with
>>
>>> the url http://oscar-osgi.sourceforge.net/obr2/repository.xml, which
>>> contains only a few really old bundles....
>>>
>>> Regards,
>>> Peter
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>
>
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
Hi,
By using the maven-bundle-plugin and specially OBR releated features, it is
really easy to create this kind of repository automatically.
I just create a pom file at the root of the releases directory. This pom
file contains the "genuine" bundle modules (genuine in the sense that some
artifacts are created as a bundle but are not real bundles as the framework
artifact). [Note: the reactor can contain only one version of each
artifact].
Once created, I just launch the following command:
mvn deploy org.apache.felix:maven-bundle-plugin:deploy
-DaltDeploymentRepository=plop-plop.felix.releases::default::ftp://plop-plop
.net -DremoteOBR=enable
We add to use an alternative repository as the default repository is the
Apache Maven one. Moreover, by default the remote OBR feature is disable, so
we just need to enable it.
It creates a maven repository and the OBR description file:
http://plop-plop.net/obr/
http://plop-plop.net/obr/repository.xml
This step could become something to do during the release process.
Clement
> -----Message d'origine-----
> De : Richard S. Hall [mailto:heavy@ungoverned.org]
> Envoyé : vendredi 9 mai 2008 10:11
> À : users@felix.apache.org; dev@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> There currently is not. We definitely need this. It basically involves
> determining at least two things:
>
> 1. How should we go about generating the repo?
> * We have the capability to generate OBR repository files,
> but
> how do we get one generated for our current set of released
> bundle versions?
> 2. Where do we put the repository?
>
> I don't really know the best way to do (1). As for (2), I am not sure
> if
> it matters, I don't think it needs to be hosted on our Apache site. I
> could put the repo on my own personal web site or we could just put
> them
> on the Source Forge web site.
>
> -> richard
>
> p.s. Sorry to cross post, it is not necessary to cross post replies...I
> just want to make sure that this discussion is seen on the dev list.
>
> peter.doornbosch wrote:
> > Hi,
> >
> > I wonder if there is an obr repository for the (current versions of
> > the) felix bundles. When i start felix (1.0.4), obr is configured
> with
> > the url http://oscar-osgi.sourceforge.net/obr2/repository.xml, which
> > contains only a few really old bundles....
> >
> > Regards,
> > Peter
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
> -----Message d'origine-----
> De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de Stuart
> McCulloch
> Envoyé : jeudi 29 mai 2008 21:17
> À : users@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> 2008/5/30 Clement Escoffier <cl...@gmail.com>:
>
> > Hi,
> >
> > I finally merge the goal that I created with the deploy AND the
> deploy-file
> > goals. In fact, I add to merge with both because the deploy-file goal
> does
> > not support multi-module projects (and it's normal, just I don't
> expect to
> > have this issue yesterday).
> >
> > Finally, the resulting plug-in is very similar to the actual one:
> >
> > The deploy goal can take an prefix attribute used to compute absolute
> URLs.
> > This allows deploying an OBR file with pointing on bundles located on
> > another server (the configured deployment repository and the
> > altDeploymentRepository attribute are generally used to deploy the
> OBR
> > file,
> > but I add an url attribute to differentiate the two potential
> locations).
> > If
> > the prefix is not specified, the process is executed normally and the
> url
> > attribute is ignored.
> >
> > The deploy-file goal checks if a project is attached to the build. If
> it
> > is,
> > it uses this project. This allows simplifying the usage (no more need
> to
> > specify the pom file and the obr.xml file). The url attribute (giving
> > information to upload the repository file) supports the maven syntax
> too.
> > Absolute URLs are computed if the bundleURL (that can be an absolute
> url)
> > attribute and file attribute are not specified. In this case, the
> prefix
> > attribute is used to computes the URL. This attribute has a default
> value
> > pointing on repo1.maven.org/maven2.
> >
> > The repository file http://oscar-osgi.sf.net/obr-repo/releases.xml
> was
> > generated with the plugin.
> >
> > I commit the modifications in my sandbox :
> >
> > https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-
> utils/maven-bundl
> > e-plugin<https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-
> utils/maven-bundle-plugin>
> > .
> >
> > WDYT?
> >
>
> the patch looks good in general, but there are a couple of
> minor fixes needed (e.g. when you don't have a pom.xml
> Maven actually provides its own super-pom, so the check
> for a local project in deploy-file needs tweaking)
>
It goes past my weak knowledge about Maven :-)
> could you create a JIRA issue for this work, and attach your
> current patch, so we can track this new feature - thanks!
>
I open the following issue, and attach the patch:
https://issues.apache.org/jira/browse/FELIX-580
Clement
> >
> >
> > > -----Message d'origine-----
> > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> Stuart
> > > McCulloch
> > > Envoyé : mercredi 28 mai 2008 09:10
> > > À : users@felix.apache.org
> > > Objet : Re: obr for felix bundles?
> > >
> > > On 28/05/2008, Clement Escoffier <cl...@gmail.com>
> wrote:
> > > >
> > > > > -----Message d'origine-----
> > > > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> > > Stuart
> > > > > McCulloch
> > > > > Envoyé : mercredi 28 mai 2008 08:15
> > > >
> > > > > À : users@felix.apache.org
> > > > > Objet : Re: obr for felix bundles?
> > > > >
> > > >
> > > > > 2008/5/28 Felix Meschberger <fm...@gmail.com>:
> > > > >
> > > > > > Hi Richard,
> > > > > >
> > > > > > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S.
> Hall:
> > > > > > > Felix,
> > > > > > >
> > > > > > > I don't have a problem with this approach (or any approach
> for
> > > that
> > > > > > matter).
> > > > > > >
> > > > > > > My only request is that we devise a method that is easy for
> us
> > > to
> > > > > update
> > > > > > > any time we have a new release.
> > > > > >
> > > > > > That would be mine, too. Clement seems to be working on a
> maven
> > > > > plugin
> > > > > > to update repository.xml files, with entries of deployed
> > > artifacts
> > > > > with
> > > > > > absolute URIs such that the repository.xml need not be
> located at
> > > the
> > > > > > maven repository root.
> > > > > >
> > > > >
> > > > > note that this is already possible, just use the bundle:deploy-
> file
> > > > > goal...
> > > > >
> > > > >
> > > > > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> > > > > bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
> > > > >
> > > > > you can set the bundle URL separately from the repository
> location.
> > > >
> > > >
> > > > I agree, the goal that I'm developing is very close of the
> deploy-
> > > file
> > > > goal.
> > > > In fact it's a mix between the deploy and the deploy-file goals.
> > > Instead of
> > > > giving the absolute bundle URL (required in the deploy-file if
> you
> > > want
> > > > absolute URL), the goal computes the URL from a given prefix
> > > > (http://repo1.maven.org or can be specified by the user) and from
> the
> > > > artifact. You don't have to specify the pom file to use, as it
> uses
> > > the
> > > > project pom file. The repository file access is given by
> following
> > > the
> > > > "maven way" (name::default::url).
> > > >
> > > > In fact, it's just a specific kind of deploy-file goal. Right
> now,
> > > it's a
> > > > separate goal, but it is easily "mergeable" with the deploy-file
> > > goal.
> > >
> > >
> > > sounds like a useful addition, if it reduces configuration :)
> > >
> > > Clement
> > > >
> > >
> > > --
> > > Cheers, Stuart
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
>
> --
> Cheers, Stuart
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Stuart McCulloch <st...@jayway.net>.
2008/5/30 Clement Escoffier <cl...@gmail.com>:
> Hi,
>
> I finally merge the goal that I created with the deploy AND the deploy-file
> goals. In fact, I add to merge with both because the deploy-file goal does
> not support multi-module projects (and it's normal, just I don't expect to
> have this issue yesterday).
>
> Finally, the resulting plug-in is very similar to the actual one:
>
> The deploy goal can take an prefix attribute used to compute absolute URLs.
> This allows deploying an OBR file with pointing on bundles located on
> another server (the configured deployment repository and the
> altDeploymentRepository attribute are generally used to deploy the OBR
> file,
> but I add an url attribute to differentiate the two potential locations).
> If
> the prefix is not specified, the process is executed normally and the url
> attribute is ignored.
>
> The deploy-file goal checks if a project is attached to the build. If it
> is,
> it uses this project. This allows simplifying the usage (no more need to
> specify the pom file and the obr.xml file). The url attribute (giving
> information to upload the repository file) supports the maven syntax too.
> Absolute URLs are computed if the bundleURL (that can be an absolute url)
> attribute and file attribute are not specified. In this case, the prefix
> attribute is used to computes the URL. This attribute has a default value
> pointing on repo1.maven.org/maven2.
>
> The repository file http://oscar-osgi.sf.net/obr-repo/releases.xml was
> generated with the plugin.
>
> I commit the modifications in my sandbox :
>
> https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-utils/maven-bundl
> e-plugin<https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-utils/maven-bundle-plugin>
> .
>
> WDYT?
>
the patch looks good in general, but there are a couple of
minor fixes needed (e.g. when you don't have a pom.xml
Maven actually provides its own super-pom, so the check
for a local project in deploy-file needs tweaking)
could you create a JIRA issue for this work, and attach your
current patch, so we can track this new feature - thanks!
> Clement
>
>
> > -----Message d'origine-----
> > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de Stuart
> > McCulloch
> > Envoyé : mercredi 28 mai 2008 09:10
> > À : users@felix.apache.org
> > Objet : Re: obr for felix bundles?
> >
> > On 28/05/2008, Clement Escoffier <cl...@gmail.com> wrote:
> > >
> > > > -----Message d'origine-----
> > > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> > Stuart
> > > > McCulloch
> > > > Envoyé : mercredi 28 mai 2008 08:15
> > >
> > > > À : users@felix.apache.org
> > > > Objet : Re: obr for felix bundles?
> > > >
> > >
> > > > 2008/5/28 Felix Meschberger <fm...@gmail.com>:
> > > >
> > > > > Hi Richard,
> > > > >
> > > > > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> > > > > > Felix,
> > > > > >
> > > > > > I don't have a problem with this approach (or any approach for
> > that
> > > > > matter).
> > > > > >
> > > > > > My only request is that we devise a method that is easy for us
> > to
> > > > update
> > > > > > any time we have a new release.
> > > > >
> > > > > That would be mine, too. Clement seems to be working on a maven
> > > > plugin
> > > > > to update repository.xml files, with entries of deployed
> > artifacts
> > > > with
> > > > > absolute URIs such that the repository.xml need not be located at
> > the
> > > > > maven repository root.
> > > > >
> > > >
> > > > note that this is already possible, just use the bundle:deploy-file
> > > > goal...
> > > >
> > > >
> > > > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> > > > bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
> > > >
> > > > you can set the bundle URL separately from the repository location.
> > >
> > >
> > > I agree, the goal that I'm developing is very close of the deploy-
> > file
> > > goal.
> > > In fact it's a mix between the deploy and the deploy-file goals.
> > Instead of
> > > giving the absolute bundle URL (required in the deploy-file if you
> > want
> > > absolute URL), the goal computes the URL from a given prefix
> > > (http://repo1.maven.org or can be specified by the user) and from the
> > > artifact. You don't have to specify the pom file to use, as it uses
> > the
> > > project pom file. The repository file access is given by following
> > the
> > > "maven way" (name::default::url).
> > >
> > > In fact, it's just a specific kind of deploy-file goal. Right now,
> > it's a
> > > separate goal, but it is easily "mergeable" with the deploy-file
> > goal.
> >
> >
> > sounds like a useful addition, if it reduces configuration :)
> >
> > Clement
> > >
> >
> > --
> > Cheers, Stuart
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Cheers, Stuart
Re: obr for felix bundles?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
Am Dienstag, den 27.05.2008, 22:56 +1200 schrieb Mark Derricutt:
> Just noticed this post - this is one of things that really annoyed the hell
> out of me when I first started using Ivy as a dependency manager 2-3 years
> ago - Ivy kept its ivy.xml files in its own repository that pointed to the
> ibiblio based maven repository. The problem I found with this is that
> either ibiblio would go down, or the ivy repository would be down, or one or
> the other would delete or move artifacts around.
Nowadays the central maven repository - repo1.maven.org - is not run by
ibiblio any more but by Apache itself, AFAIK. And to me repo1.maven.org
seems far more reliable than the former ibiblio repo.
The repository.xml is just an XML file whish is provided through a
normal HTTP server (from felix.apache.org in my proposal). See
http://oscar-osgi.sourceforge.net/obr2/repository.xml. This file lists
the bundles available as well as their capabilities and requirements.
The actual bundles are referred to by the repository.uri attribute.
So I think, this is not so much of a problem.
Regards
Felix
> I found this soon led to inconsistencies in the repositories - and
> dependencies on multiple upstream providers - chasing down either ivy
> maintainers, maven maintainers, plus the project maintainers seemed like a
> recipe for disaster which led to maintaining an internal private repository
> for everything.
>
> Hopefully the OBR repository could avoid possible issues like this.
>
> Mark
>
> On Tue, May 27, 2008 at 10:43 PM, Felix Meschberger <fm...@gmail.com>
> wrote:
>
> > But my point is that we do NOT replicate the actual bundle files but
> > keep the in the Maven Repository, where they already are. We just create
> > repository.xml files that refer to the existing bundles in the Maven
> > Repository.
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Mark Derricutt <ma...@talios.com>.
Just noticed this post - this is one of things that really annoyed the hell
out of me when I first started using Ivy as a dependency manager 2-3 years
ago - Ivy kept its ivy.xml files in its own repository that pointed to the
ibiblio based maven repository. The problem I found with this is that
either ibiblio would go down, or the ivy repository would be down, or one or
the other would delete or move artifacts around.
I found this soon led to inconsistencies in the repositories - and
dependencies on multiple upstream providers - chasing down either ivy
maintainers, maven maintainers, plus the project maintainers seemed like a
recipe for disaster which led to maintaining an internal private repository
for everything.
Hopefully the OBR repository could avoid possible issues like this.
Mark
On Tue, May 27, 2008 at 10:43 PM, Felix Meschberger <fm...@gmail.com>
wrote:
> But my point is that we do NOT replicate the actual bundle files but
> keep the in the Maven Repository, where they already are. We just create
> repository.xml files that refer to the existing bundles in the Maven
> Repository.
>
--
"It is easier to optimize correct code than to correct optimized code." --
Bill Harlan
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
> -----Message d'origine-----
> De : Felix Meschberger [mailto:fmeschbe@gmail.com]
> Envoyé : vendredi 30 mai 2008 02:08
> À : users@felix.apache.org
> Objet : RE: obr for felix bundles?
>
> Hi,
>
> Sounds very good ! Let's go ;-)
>
> One question, though: You said the remote OBR deployment would just
> leave a single version of the bundle in the repository.xml file. While
> this may be usefull in general, it would pose problems in some use
> cases.
>
> For example at our company we might provide an application consisting
> of
> multiple bundles. Over time we generate releases of the bundles but
> some
> customers will still be working with older versions of the bundles. To
> be able to support such customers, it would probably be required to
> have
> the older versions also available in the repository.
>
> So, could there be a switch to enable/disable this replacement
> functionality ? This might not be needed right now - having the OBR
> available in the first place is IMHO more important.
Hi,
I mention that as a possible extension (in fact it's more an extension of the obr-checker than the maven-bundle-plugin).
In fact, if your OBR contains thousands of bundles, it could be a pain to find to understand possible deployment, so filters to create views could be useful.
Of course, the generated OBR file contains all versions. The OBR that I generated contains only one as the pom file that I used contains only one version of each artifact (maven-restriction), but you can see now two versions of the configuration admin.
Once this OBR is set, it should be possible to generate a consistent subset of this repository with only "latest" versions (if possible), or with a different filter. The naïve algorithm to generate this view (as it is not a real repository) could be :
Select every bundles and check the consistency
For each bundles with several versions try to remove the oldest version and check the consistency.
Loop while you found an un-consistency or there is only one version of the bundle.
But, it's just an idea. While the repository is not huge, this kind of mechanisms isn't worthwhile.
Regards,
Clement
>
> Am Donnerstag, den 29.05.2008, 13:34 -0400 schrieb Clement Escoffier:
> > I finally merge the goal that I created with the deploy AND the
> deploy-file
> > goals. In fact, I add to merge with both because the deploy-file goal
> does
> > not support multi-module projects (and it's normal, just I don't
> expect to
> > have this issue yesterday).
> >
> > Finally, the resulting plug-in is very similar to the actual one:
> >
> > The deploy goal can take an prefix attribute used to compute absolute
> URLs.
> > This allows deploying an OBR file with pointing on bundles located on
> > another server (the configured deployment repository and the
> > altDeploymentRepository attribute are generally used to deploy the
> OBR file,
> > but I add an url attribute to differentiate the two potential
> locations). If
> > the prefix is not specified, the process is executed normally and the
> url
> > attribute is ignored.
> >
> > The deploy-file goal checks if a project is attached to the build. If
> it is,
> > it uses this project. This allows simplifying the usage (no more need
> to
> > specify the pom file and the obr.xml file). The url attribute (giving
> > information to upload the repository file) supports the maven syntax
> too.
> > Absolute URLs are computed if the bundleURL (that can be an absolute
> url)
> > attribute and file attribute are not specified. In this case, the
> prefix
> > attribute is used to computes the URL. This attribute has a default
> value
> > pointing on repo1.maven.org/maven2.
> >
> > The repository file http://oscar-osgi.sf.net/obr-repo/releases.xml
> was
> > generated with the plugin.
> >
> > I commit the modifications in my sandbox :
> > https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-
> utils/maven-bundl
> > e-plugin.
> >
> > WDYT?
> >
> > Clement
> >
> >
> > > -----Message d'origine-----
> > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> Stuart
> > > McCulloch
> > > Envoyé : mercredi 28 mai 2008 09:10
> > > À : users@felix.apache.org
> > > Objet : Re: obr for felix bundles?
> > >
> > > On 28/05/2008, Clement Escoffier <cl...@gmail.com>
> wrote:
> > > >
> > > > > -----Message d'origine-----
> > > > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> > > Stuart
> > > > > McCulloch
> > > > > Envoyé : mercredi 28 mai 2008 08:15
> > > >
> > > > > À : users@felix.apache.org
> > > > > Objet : Re: obr for felix bundles?
> > > > >
> > > >
> > > > > 2008/5/28 Felix Meschberger <fm...@gmail.com>:
> > > > >
> > > > > > Hi Richard,
> > > > > >
> > > > > > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S.
> Hall:
> > > > > > > Felix,
> > > > > > >
> > > > > > > I don't have a problem with this approach (or any approach
> for
> > > that
> > > > > > matter).
> > > > > > >
> > > > > > > My only request is that we devise a method that is easy for
> us
> > > to
> > > > > update
> > > > > > > any time we have a new release.
> > > > > >
> > > > > > That would be mine, too. Clement seems to be working on a
> maven
> > > > > plugin
> > > > > > to update repository.xml files, with entries of deployed
> > > artifacts
> > > > > with
> > > > > > absolute URIs such that the repository.xml need not be
> located at
> > > the
> > > > > > maven repository root.
> > > > > >
> > > > >
> > > > > note that this is already possible, just use the bundle:deploy-
> file
> > > > > goal...
> > > > >
> > > > >
> > > > > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> > > > > bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
> > > > >
> > > > > you can set the bundle URL separately from the repository
> location.
> > > >
> > > >
> > > > I agree, the goal that I'm developing is very close of the
> deploy-
> > > file
> > > > goal.
> > > > In fact it's a mix between the deploy and the deploy-file goals.
> > > Instead of
> > > > giving the absolute bundle URL (required in the deploy-file if
> you
> > > want
> > > > absolute URL), the goal computes the URL from a given prefix
> > > > (http://repo1.maven.org or can be specified by the user) and from
> the
> > > > artifact. You don't have to specify the pom file to use, as it
> uses
> > > the
> > > > project pom file. The repository file access is given by
> following
> > > the
> > > > "maven way" (name::default::url).
> > > >
> > > > In fact, it's just a specific kind of deploy-file goal. Right
> now,
> > > it's a
> > > > separate goal, but it is easily "mergeable" with the deploy-file
> > > goal.
> > >
> > >
> > > sounds like a useful addition, if it reduces configuration :)
> > >
> > > Clement
> > > >
> > >
> > > --
> > > Cheers, Stuart
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: obr for felix bundles?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
Sounds very good ! Let's go ;-)
One question, though: You said the remote OBR deployment would just
leave a single version of the bundle in the repository.xml file. While
this may be usefull in general, it would pose problems in some use
cases.
For example at our company we might provide an application consisting of
multiple bundles. Over time we generate releases of the bundles but some
customers will still be working with older versions of the bundles. To
be able to support such customers, it would probably be required to have
the older versions also available in the repository.
So, could there be a switch to enable/disable this replacement
functionality ? This might not be needed right now - having the OBR
available in the first place is IMHO more important.
Thanks and Regards
Felix
Am Donnerstag, den 29.05.2008, 13:34 -0400 schrieb Clement Escoffier:
> I finally merge the goal that I created with the deploy AND the deploy-file
> goals. In fact, I add to merge with both because the deploy-file goal does
> not support multi-module projects (and it's normal, just I don't expect to
> have this issue yesterday).
>
> Finally, the resulting plug-in is very similar to the actual one:
>
> The deploy goal can take an prefix attribute used to compute absolute URLs.
> This allows deploying an OBR file with pointing on bundles located on
> another server (the configured deployment repository and the
> altDeploymentRepository attribute are generally used to deploy the OBR file,
> but I add an url attribute to differentiate the two potential locations). If
> the prefix is not specified, the process is executed normally and the url
> attribute is ignored.
>
> The deploy-file goal checks if a project is attached to the build. If it is,
> it uses this project. This allows simplifying the usage (no more need to
> specify the pom file and the obr.xml file). The url attribute (giving
> information to upload the repository file) supports the maven syntax too.
> Absolute URLs are computed if the bundleURL (that can be an absolute url)
> attribute and file attribute are not specified. In this case, the prefix
> attribute is used to computes the URL. This attribute has a default value
> pointing on repo1.maven.org/maven2.
>
> The repository file http://oscar-osgi.sf.net/obr-repo/releases.xml was
> generated with the plugin.
>
> I commit the modifications in my sandbox :
> https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-utils/maven-bundl
> e-plugin.
>
> WDYT?
>
> Clement
>
>
> > -----Message d'origine-----
> > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de Stuart
> > McCulloch
> > Envoyé : mercredi 28 mai 2008 09:10
> > À : users@felix.apache.org
> > Objet : Re: obr for felix bundles?
> >
> > On 28/05/2008, Clement Escoffier <cl...@gmail.com> wrote:
> > >
> > > > -----Message d'origine-----
> > > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> > Stuart
> > > > McCulloch
> > > > Envoyé : mercredi 28 mai 2008 08:15
> > >
> > > > À : users@felix.apache.org
> > > > Objet : Re: obr for felix bundles?
> > > >
> > >
> > > > 2008/5/28 Felix Meschberger <fm...@gmail.com>:
> > > >
> > > > > Hi Richard,
> > > > >
> > > > > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> > > > > > Felix,
> > > > > >
> > > > > > I don't have a problem with this approach (or any approach for
> > that
> > > > > matter).
> > > > > >
> > > > > > My only request is that we devise a method that is easy for us
> > to
> > > > update
> > > > > > any time we have a new release.
> > > > >
> > > > > That would be mine, too. Clement seems to be working on a maven
> > > > plugin
> > > > > to update repository.xml files, with entries of deployed
> > artifacts
> > > > with
> > > > > absolute URIs such that the repository.xml need not be located at
> > the
> > > > > maven repository root.
> > > > >
> > > >
> > > > note that this is already possible, just use the bundle:deploy-file
> > > > goal...
> > > >
> > > >
> > > > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> > > > bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
> > > >
> > > > you can set the bundle URL separately from the repository location.
> > >
> > >
> > > I agree, the goal that I'm developing is very close of the deploy-
> > file
> > > goal.
> > > In fact it's a mix between the deploy and the deploy-file goals.
> > Instead of
> > > giving the absolute bundle URL (required in the deploy-file if you
> > want
> > > absolute URL), the goal computes the URL from a given prefix
> > > (http://repo1.maven.org or can be specified by the user) and from the
> > > artifact. You don't have to specify the pom file to use, as it uses
> > the
> > > project pom file. The repository file access is given by following
> > the
> > > "maven way" (name::default::url).
> > >
> > > In fact, it's just a specific kind of deploy-file goal. Right now,
> > it's a
> > > separate goal, but it is easily "mergeable" with the deploy-file
> > goal.
> >
> >
> > sounds like a useful addition, if it reduces configuration :)
> >
> > Clement
> > >
> >
> > --
> > Cheers, Stuart
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
Hi,
I finally merge the goal that I created with the deploy AND the deploy-file
goals. In fact, I add to merge with both because the deploy-file goal does
not support multi-module projects (and it's normal, just I don't expect to
have this issue yesterday).
Finally, the resulting plug-in is very similar to the actual one:
The deploy goal can take an prefix attribute used to compute absolute URLs.
This allows deploying an OBR file with pointing on bundles located on
another server (the configured deployment repository and the
altDeploymentRepository attribute are generally used to deploy the OBR file,
but I add an url attribute to differentiate the two potential locations). If
the prefix is not specified, the process is executed normally and the url
attribute is ignored.
The deploy-file goal checks if a project is attached to the build. If it is,
it uses this project. This allows simplifying the usage (no more need to
specify the pom file and the obr.xml file). The url attribute (giving
information to upload the repository file) supports the maven syntax too.
Absolute URLs are computed if the bundleURL (that can be an absolute url)
attribute and file attribute are not specified. In this case, the prefix
attribute is used to computes the URL. This attribute has a default value
pointing on repo1.maven.org/maven2.
The repository file http://oscar-osgi.sf.net/obr-repo/releases.xml was
generated with the plugin.
I commit the modifications in my sandbox :
https://svn.apache.org/repos/asf/felix/sandbox/clement/obr-utils/maven-bundl
e-plugin.
WDYT?
Clement
> -----Message d'origine-----
> De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de Stuart
> McCulloch
> Envoyé : mercredi 28 mai 2008 09:10
> À : users@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> On 28/05/2008, Clement Escoffier <cl...@gmail.com> wrote:
> >
> > > -----Message d'origine-----
> > > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de
> Stuart
> > > McCulloch
> > > Envoyé : mercredi 28 mai 2008 08:15
> >
> > > À : users@felix.apache.org
> > > Objet : Re: obr for felix bundles?
> > >
> >
> > > 2008/5/28 Felix Meschberger <fm...@gmail.com>:
> > >
> > > > Hi Richard,
> > > >
> > > > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> > > > > Felix,
> > > > >
> > > > > I don't have a problem with this approach (or any approach for
> that
> > > > matter).
> > > > >
> > > > > My only request is that we devise a method that is easy for us
> to
> > > update
> > > > > any time we have a new release.
> > > >
> > > > That would be mine, too. Clement seems to be working on a maven
> > > plugin
> > > > to update repository.xml files, with entries of deployed
> artifacts
> > > with
> > > > absolute URIs such that the repository.xml need not be located at
> the
> > > > maven repository root.
> > > >
> > >
> > > note that this is already possible, just use the bundle:deploy-file
> > > goal...
> > >
> > >
> > > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> > > bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
> > >
> > > you can set the bundle URL separately from the repository location.
> >
> >
> > I agree, the goal that I'm developing is very close of the deploy-
> file
> > goal.
> > In fact it's a mix between the deploy and the deploy-file goals.
> Instead of
> > giving the absolute bundle URL (required in the deploy-file if you
> want
> > absolute URL), the goal computes the URL from a given prefix
> > (http://repo1.maven.org or can be specified by the user) and from the
> > artifact. You don't have to specify the pom file to use, as it uses
> the
> > project pom file. The repository file access is given by following
> the
> > "maven way" (name::default::url).
> >
> > In fact, it's just a specific kind of deploy-file goal. Right now,
> it's a
> > separate goal, but it is easily "mergeable" with the deploy-file
> goal.
>
>
> sounds like a useful addition, if it reduces configuration :)
>
> Clement
> >
>
> --
> Cheers, Stuart
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Stuart McCulloch <st...@jayway.net>.
On 28/05/2008, Clement Escoffier <cl...@gmail.com> wrote:
>
> > -----Message d'origine-----
> > De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de Stuart
> > McCulloch
> > Envoyé : mercredi 28 mai 2008 08:15
>
> > À : users@felix.apache.org
> > Objet : Re: obr for felix bundles?
> >
>
> > 2008/5/28 Felix Meschberger <fm...@gmail.com>:
> >
> > > Hi Richard,
> > >
> > > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> > > > Felix,
> > > >
> > > > I don't have a problem with this approach (or any approach for that
> > > matter).
> > > >
> > > > My only request is that we devise a method that is easy for us to
> > update
> > > > any time we have a new release.
> > >
> > > That would be mine, too. Clement seems to be working on a maven
> > plugin
> > > to update repository.xml files, with entries of deployed artifacts
> > with
> > > absolute URIs such that the repository.xml need not be located at the
> > > maven repository root.
> > >
> >
> > note that this is already possible, just use the bundle:deploy-file
> > goal...
> >
> >
> > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> > bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
> >
> > you can set the bundle URL separately from the repository location.
>
>
> I agree, the goal that I'm developing is very close of the deploy-file
> goal.
> In fact it's a mix between the deploy and the deploy-file goals. Instead of
> giving the absolute bundle URL (required in the deploy-file if you want
> absolute URL), the goal computes the URL from a given prefix
> (http://repo1.maven.org or can be specified by the user) and from the
> artifact. You don't have to specify the pom file to use, as it uses the
> project pom file. The repository file access is given by following the
> "maven way" (name::default::url).
>
> In fact, it's just a specific kind of deploy-file goal. Right now, it's a
> separate goal, but it is easily "mergeable" with the deploy-file goal.
sounds like a useful addition, if it reduces configuration :)
Clement
>
--
Cheers, Stuart
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
> -----Message d'origine-----
> De : mcculls@gmail.com [mailto:mcculls@gmail.com] De la part de Stuart
> McCulloch
> Envoyé : mercredi 28 mai 2008 08:15
> À : users@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> 2008/5/28 Felix Meschberger <fm...@gmail.com>:
>
> > Hi Richard,
> >
> > Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> > > Felix,
> > >
> > > I don't have a problem with this approach (or any approach for that
> > matter).
> > >
> > > My only request is that we devise a method that is easy for us to
> update
> > > any time we have a new release.
> >
> > That would be mine, too. Clement seems to be working on a maven
> plugin
> > to update repository.xml files, with entries of deployed artifacts
> with
> > absolute URIs such that the repository.xml need not be located at the
> > maven repository root.
> >
>
> note that this is already possible, just use the bundle:deploy-file
> goal...
>
>
> http://felix.apache.org/site/apache-felix-maven-bundle-plugin-
> bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
>
> you can set the bundle URL separately from the repository location.
I agree, the goal that I'm developing is very close of the deploy-file goal.
In fact its a mix between the deploy and the deploy-file goals. Instead of
giving the absolute bundle URL (required in the deploy-file if you want
absolute URL), the goal computes the URL from a given prefix
(http://repo1.maven.org or can be specified by the user) and from the
artifact. You don't have to specify the pom file to use, as it uses the
project pom file. The repository file access is given by following the
"maven way" (name::default::url).
In fact, it's just a specific kind of deploy-file goal. Right now, it's a
separate goal, but it is easily "mergeable" with the deploy-file goal.
Clement
>
>
> > Regards
> > Felix
> >
> > >
> > > -> richard
> > >
> > > Felix Meschberger wrote:
> > > > Hi,
> > > >
> > > > I have been thinking about this issue and been discussing it with
> > > > Carsten. And we came up with a very simple solution: The main
> point is,
> > > > that the repository.xml file and the artifacts referred to need
> not be
> > > > in the same location, right ?
> > > >
> > > > Starting from this, the solution would be that we might provide
> the
> > > > repository.xml file from the Felix site and have the bundles
> where they
> > > > already are: in the maven repository.
> > > >
> > > > So upon the release of one of the Felix bundles, we just add a
> record
> > > > for the bundle into the repository.xml pointing to the maven
> > repository.
> > > > That's it, I would say.
> > > >
> > > > So far so good. But there will be other projects -- just talking
> of
> > > > Apache for the moment, but OPS4J also comes to mind -- which have
> > > > bundles to distribute. Here comes the <referral> element of the
> > > > repository.xml file (section 5.5.4 in OSGi RFC 112): We create a
> > central
> > > > repository.xml file, into which referrals to other projects may
> be
> > > > entered. Each project thus maintains its own repository.xml.
> > > >
> > > > For example:
> > > >
> > > > global-repository.xml
> > > > ---> referral to Apache Felix repository.xml
> > > > ---> referral to Apache Sling repository.xml
> > > > ---> referral to Apache Commons repository.xml
> > > >
> > > > I think, this solution can be easily and quickly implemented and
> does
> > > > not need too much additional network traffic.
> > > >
> > > > A further development step could be to have separate
> repository.xml
> > > > files for releases and SNAPSHOTs. We could arrange to update the
> > > > SNAPSHOT repository.xml file by means of the maven-bundle-plugin
> (would
> > > > require to be able to specify the actual location repository.xml
> file)
> > > > upon deplyoment of the SNAPSHOTs...
> > > >
> > > >
> > > > WDYT ?
> > > >
> > > > Regards
> > > > Felix
> > > >
> > > >
> > > > Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
> > > >
> > > >> If I understand correctly, Clement is proposing something like
> this:
> > > >>
> > > >> releases/
> > > >> bundleA-v1/
> > > >> bundleA-v2/
> > > >> bundleB-v1/
> > > >> bundleC-v1/
> > > >> bundleC-v2/
> > > >> pom.xml
> > > >>
> > > >> The above represents the structure of our releases directory.
> The
> > > >> pom.xml will refer to the most recent version of each release
> bundle,
> > e.g.:
> > > >>
> > > >> pom.xml
> > > >> artifactId=bundleA,version=2
> > > >> artifactId=bundleB,version=1
> > > >> artifactId=bundleC,version=2
> > > >>
> > > >> The purpose of this pom file is largely to document which
> subprojects
> > > >> should be made available in our repo. However, if you use it to
> issue
> > > >> the mvn deploy command on this pom, then it will deploy the set
> of all
> > > >> current releases to the repo.
> > > >>
> > > >> This is obviously inefficient if only one bundle has been
> updated
> > since
> > > >> it will deploy all bundles. To avoid this, though, you can
> simply 'cd'
> > > >> into the precise subproject release directory and issue that mvn
> > deploy
> > > >> command from there, then only the newly released bundle will be
> > deployed.
> > > >>
> > > >> Clearly, this process is simplistic, but it is probably better
> than
> > > >> nothing, which is the current approach. The idea here is that we
> could
> > > >> just incorporate it as part of our normal release process, where
> after
> > > >> we tag a released bundle in the releases directory, then we
> update the
> > > >> version in the pom.xml and then deploy it to the repo.
> > > >>
> > > >> What do you think?
> > > >>
> > > >> -> richard
> > > >>
> > > >> anne.gerodolle@orange-ftgroup.com wrote:
> > > >>
> > > >>> If I understand well, Clement's proposal supposes that somebody
> > deploys the whole set of felix bundles in a centralized manner.
> > > >>>
> > > >>> Another possibility is to incrementally evolve the remote
> > repository.xml file, in a similar manner to the local repository.xml
> file.
> > Using this method for the official felix site would allow the person
> > responsable for deploying some felix subproject on the maven
> repository to
> > deploy the same bundles on the obr.
> > > >>>
> > > >>> This means using the same kind of command line as Clement, but
> at a
> > subproject level (not at the root):
> > > >>> mvn deploy -DremoteOBR
> > -DaltDeploymentRepository=plop-
> plop.felix.releases::default::scp://deploymentmachine/mypath
> > deploys the artifacts on the remote obr AND updates the remote
> > repository.xml file .
> > > >>>
> > > >>> I'm not involved in felix development, so I don't know what the
> > policy is concerning deployment on the maven repository. If one
> considers
> > that felix contains some subprojects (sets of bundles) that evolve
> rather
> > independently from eachother, this incremental method can be
> relevant.
> > > >>>
> > > >>> Regards,
> > > >>>
> > > >>> Anne
> > > >>>
> > > >>> -----Message d'origine-----
> > > >>> De : Richard S. Hall [mailto:heavy@ungoverned.org]
> > > >>> Envoyé : jeudi 15 mai 2008 15:43
> > > >>> À : users@felix.apache.org; dev@felix.apache.org
> > > >>> Objet : Re: obr for felix bundles?
> > > >>>
> > > >>> I think the stylesheet can be figured out one way or the
> other...what
> > we really need to do is decide if we like the approach that Clement
> has
> > proposed and, if so, where should physically generate the
> repository...
> > > >>>
> > > >>> -> richard
> > > >>>
> > > >>> Clement Escoffier wrote:
> > > >>>
> > > >>>
> > > >>>> Hi,
> > > >>>>
> > > >>>> I change the XSLT file, now there is colors :-)
> > > >>>>
> > > >>>> Clement
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>> -----Message d'origine-----
> > > >>>>> De : anne.gerodolle@orange-ftgroup.com [mailto:
> > anne.gerodolle@orange-
> > > >>>>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
> > > >>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> > > >>>>>
> > > >>>>> Hi Clement !
> > > >>>>> I have personally a slight preference for the stylesheet
> coming
> > from
> > > >>>>> the OSGi Web site (attached file) .
> > > >>>>> Apart from the style itself (better for presbyopian eyes), it
> sorts
> > > >>>>> the bundles alphabetically. I see you have commented this
> feature
> > in
> > > >>>>> yuor xsl file.
> > > >>>>> Of course that's a matter of personal preference, and that's
> not
> > the
> > > >>>>> main point !
> > > >>>>> Best regards,
> > > >>>>> Anne
> > > >>>>> -----Message d'origine-----
> > > >>>>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
> > > >>>>> Envoyé : jeudi 15 mai 2008 03:42
> > > >>>>> À : users@felix.apache.org
> > > >>>>> Objet : RE: obr for felix bundles?
> > > >>>>>
> > > >>>>> Hello,
> > > >>>>>
> > > >>>>> I attach the Didier's XSLT stylesheet to the generated XML
> file.
> > > >>>>> The result is available here :
> > > >>>>> http://plop-plop.net/obr/repository.xml
> > > >>>>>
> > > >>>>> Clement
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>> -----Message d'origine-----
> > > >>>>>> De : anne.gerodolle@orange-ftgroup.com
> > > >>>>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi
> 13 mai
> > 2008 06:25 À :
> > > >>>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> > > >>>>>>
> > > >>>>>> Great idea !
> > > >>>>>>
> > > >>>>>> Not only it will ease people getting started with felix, but
> it
> > can
> > > >>>>>> help convince people giving a try :
> > > >>>>>> if your repository.xml refers to an obr2html.xsl file, and
> you
> > show
> > > >>>>>> people the repository in a browser, you will have the same
> "waw"
> > > >>>>>> effect as with the old Oscar repository. You see a nice list
> of
> > > >>>>>> already existing bundles, and if you follow the "doc" link
> it goes
> > > >>>>>> to the doc etc..
> > > >>>>>>
> > > >>>>>> Regards,
> > > >>>>>> Anne
> > > >>>>>>
> > > >>>>>> -----Message d'origine-----
> > > >>>>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> > > >>>>>> Envoyé : samedi 10 mai 2008 11:43
> > > >>>>>> À : users@felix.apache.org
> > > >>>>>> Objet : Re: obr for felix bundles?
> > > >>>>>>
> > > >>>>>> Hi Richard,
> > > >>>>>>
> > > >>>>>> I think it would be great if you can arrange this. I think
> that
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>> people
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>> that are new to OSGi can have a hard time to get started
> with
> > felix
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>> (i
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>> noticed this a few times) and i think that being able to
> install
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>> felix
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>> bundles in a simple and convenient way might help.
> > > >>>>>>
> > > >>>>>> Regards,
> > > >>>>>> Peer
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>> There currently is not. We definitely need this. It
> basically
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>> involves
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>> determining at least two things:
> > > >>>>>>>
> > > >>>>>>> 1. How should we go about generating the repo?
> > > >>>>>>> * We have the capability to generate OBR repository
> > files,
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>> but
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>> how do we get one generated for our current set
> of
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>> released
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>>> bundle versions?
> > > >>>>>>> 2. Where do we put the repository?
> > > >>>>>>>
> > > >>>>>>> I don't really know the best way to do (1). As for (2), I
> am not
> > > >>>>>>> sure if it matters, I don't think it needs to be hosted on
> our
> > > >>>>>>> Apache
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>> site.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>> I could put the repo on my own personal web site or we
> could just
> > > >>>>>>> put them on the Source Forge web site.
> > > >>>>>>>
> > > >>>>>>> -> richard
> > > >>>>>>>
> > > >>>>>>> p.s. Sorry to cross post, it is not necessary to cross post
> > > >>>>>>> replies...I just want to make sure that this discussion is
> seen
> > on
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>> the
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>> dev list.
> > > >>>>>>>
> > > >>>>>>> peter.doornbosch wrote:
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>> Hi,
> > > >>>>>>>>
> > > >>>>>>>> I wonder if there is an obr repository for the (current
> versions
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>> of
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>>>> the) felix bundles. When i start felix (1.0.4), obr is
> > configured
> > > >>>>>>>> with the url http://oscar-
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>> osgi.sourceforge.net/obr2/repository.xml,
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>>>> which contains only a few really old bundles....
> > > >>>>>>>>
> > > >>>>>>>> Regards,
> > > >>>>>>>> Peter
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > ------------------------------------------------------------------
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>> -
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>>>> -
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>> -
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>>>>>>> For additional commands, e-mail: users-
> help@felix.apache.org
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > -------------------------------------------------------------------
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>> -
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>>> - To unsubscribe, e-mail: users-
> unsubscribe@felix.apache.org
> > > >>>>>>> For additional commands, e-mail: users-
> help@felix.apache.org
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > --------------------------------------------------------------------
> > > >>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > --------------------------------------------------------------------
> > > >>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > ---------------------------------------------------------------------
> > > >>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>>>> For additional commands, e-mail: users-help@felix.apache.org
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>>> For additional commands, e-mail: users-help@felix.apache.org
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>> ---------------------------------------------------------------
> ------
> > > >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>> For additional commands, e-mail: users-help@felix.apache.org
> > > >>>
> > > >>>
> > > >>> ---------------------------------------------------------------
> ------
> > > >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >>> For additional commands, e-mail: users-help@felix.apache.org
> > > >>>
> > > >>>
> > > >>>
> > > >> ----------------------------------------------------------------
> -----
> > > >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > >> For additional commands, e-mail: users-help@felix.apache.org
> > > >>
> > > >>
> > > >
> > > >
> > > > -----------------------------------------------------------------
> ----
> > > > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > > For additional commands, e-mail: users-help@felix.apache.org
> > > >
> > > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > For additional commands, e-mail: users-help@felix.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
>
> --
> Cheers, Stuart
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Stuart McCulloch <st...@jayway.net>.
2008/5/28 Felix Meschberger <fm...@gmail.com>:
> Hi Richard,
>
> Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> > Felix,
> >
> > I don't have a problem with this approach (or any approach for that
> matter).
> >
> > My only request is that we devise a method that is easy for us to update
> > any time we have a new release.
>
> That would be mine, too. Clement seems to be working on a maven plugin
> to update repository.xml files, with entries of deployed artifacts with
> absolute URIs such that the repository.xml need not be located at the
> maven repository root.
>
note that this is already possible, just use the bundle:deploy-file goal...
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html#ApacheFelixMavenBundlePlugin(BND)-bundle%3Adeployfile
you can set the bundle URL separately from the repository location.
> Regards
> Felix
>
> >
> > -> richard
> >
> > Felix Meschberger wrote:
> > > Hi,
> > >
> > > I have been thinking about this issue and been discussing it with
> > > Carsten. And we came up with a very simple solution: The main point is,
> > > that the repository.xml file and the artifacts referred to need not be
> > > in the same location, right ?
> > >
> > > Starting from this, the solution would be that we might provide the
> > > repository.xml file from the Felix site and have the bundles where they
> > > already are: in the maven repository.
> > >
> > > So upon the release of one of the Felix bundles, we just add a record
> > > for the bundle into the repository.xml pointing to the maven
> repository.
> > > That's it, I would say.
> > >
> > > So far so good. But there will be other projects -- just talking of
> > > Apache for the moment, but OPS4J also comes to mind -- which have
> > > bundles to distribute. Here comes the <referral> element of the
> > > repository.xml file (section 5.5.4 in OSGi RFC 112): We create a
> central
> > > repository.xml file, into which referrals to other projects may be
> > > entered. Each project thus maintains its own repository.xml.
> > >
> > > For example:
> > >
> > > global-repository.xml
> > > ---> referral to Apache Felix repository.xml
> > > ---> referral to Apache Sling repository.xml
> > > ---> referral to Apache Commons repository.xml
> > >
> > > I think, this solution can be easily and quickly implemented and does
> > > not need too much additional network traffic.
> > >
> > > A further development step could be to have separate repository.xml
> > > files for releases and SNAPSHOTs. We could arrange to update the
> > > SNAPSHOT repository.xml file by means of the maven-bundle-plugin (would
> > > require to be able to specify the actual location repository.xml file)
> > > upon deplyoment of the SNAPSHOTs...
> > >
> > >
> > > WDYT ?
> > >
> > > Regards
> > > Felix
> > >
> > >
> > > Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
> > >
> > >> If I understand correctly, Clement is proposing something like this:
> > >>
> > >> releases/
> > >> bundleA-v1/
> > >> bundleA-v2/
> > >> bundleB-v1/
> > >> bundleC-v1/
> > >> bundleC-v2/
> > >> pom.xml
> > >>
> > >> The above represents the structure of our releases directory. The
> > >> pom.xml will refer to the most recent version of each release bundle,
> e.g.:
> > >>
> > >> pom.xml
> > >> artifactId=bundleA,version=2
> > >> artifactId=bundleB,version=1
> > >> artifactId=bundleC,version=2
> > >>
> > >> The purpose of this pom file is largely to document which subprojects
> > >> should be made available in our repo. However, if you use it to issue
> > >> the mvn deploy command on this pom, then it will deploy the set of all
> > >> current releases to the repo.
> > >>
> > >> This is obviously inefficient if only one bundle has been updated
> since
> > >> it will deploy all bundles. To avoid this, though, you can simply 'cd'
> > >> into the precise subproject release directory and issue that mvn
> deploy
> > >> command from there, then only the newly released bundle will be
> deployed.
> > >>
> > >> Clearly, this process is simplistic, but it is probably better than
> > >> nothing, which is the current approach. The idea here is that we could
> > >> just incorporate it as part of our normal release process, where after
> > >> we tag a released bundle in the releases directory, then we update the
> > >> version in the pom.xml and then deploy it to the repo.
> > >>
> > >> What do you think?
> > >>
> > >> -> richard
> > >>
> > >> anne.gerodolle@orange-ftgroup.com wrote:
> > >>
> > >>> If I understand well, Clement's proposal supposes that somebody
> deploys the whole set of felix bundles in a centralized manner.
> > >>>
> > >>> Another possibility is to incrementally evolve the remote
> repository.xml file, in a similar manner to the local repository.xml file.
> Using this method for the official felix site would allow the person
> responsable for deploying some felix subproject on the maven repository to
> deploy the same bundles on the obr.
> > >>>
> > >>> This means using the same kind of command line as Clement, but at a
> subproject level (not at the root):
> > >>> mvn deploy -DremoteOBR
> -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath
> deploys the artifacts on the remote obr AND updates the remote
> repository.xml file .
> > >>>
> > >>> I'm not involved in felix development, so I don't know what the
> policy is concerning deployment on the maven repository. If one considers
> that felix contains some subprojects (sets of bundles) that evolve rather
> independently from eachother, this incremental method can be relevant.
> > >>>
> > >>> Regards,
> > >>>
> > >>> Anne
> > >>>
> > >>> -----Message d'origine-----
> > >>> De : Richard S. Hall [mailto:heavy@ungoverned.org]
> > >>> Envoyé : jeudi 15 mai 2008 15:43
> > >>> À : users@felix.apache.org; dev@felix.apache.org
> > >>> Objet : Re: obr for felix bundles?
> > >>>
> > >>> I think the stylesheet can be figured out one way or the other...what
> we really need to do is decide if we like the approach that Clement has
> proposed and, if so, where should physically generate the repository...
> > >>>
> > >>> -> richard
> > >>>
> > >>> Clement Escoffier wrote:
> > >>>
> > >>>
> > >>>> Hi,
> > >>>>
> > >>>> I change the XSLT file, now there is colors :-)
> > >>>>
> > >>>> Clement
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>> -----Message d'origine-----
> > >>>>> De : anne.gerodolle@orange-ftgroup.com [mailto:
> anne.gerodolle@orange-
> > >>>>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
> > >>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> > >>>>>
> > >>>>> Hi Clement !
> > >>>>> I have personally a slight preference for the stylesheet coming
> from
> > >>>>> the OSGi Web site (attached file) .
> > >>>>> Apart from the style itself (better for presbyopian eyes), it sorts
> > >>>>> the bundles alphabetically. I see you have commented this feature
> in
> > >>>>> yuor xsl file.
> > >>>>> Of course that's a matter of personal preference, and that's not
> the
> > >>>>> main point !
> > >>>>> Best regards,
> > >>>>> Anne
> > >>>>> -----Message d'origine-----
> > >>>>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
> > >>>>> Envoyé : jeudi 15 mai 2008 03:42
> > >>>>> À : users@felix.apache.org
> > >>>>> Objet : RE: obr for felix bundles?
> > >>>>>
> > >>>>> Hello,
> > >>>>>
> > >>>>> I attach the Didier's XSLT stylesheet to the generated XML file.
> > >>>>> The result is available here :
> > >>>>> http://plop-plop.net/obr/repository.xml
> > >>>>>
> > >>>>> Clement
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> -----Message d'origine-----
> > >>>>>> De : anne.gerodolle@orange-ftgroup.com
> > >>>>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai
> 2008 06:25 À :
> > >>>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> > >>>>>>
> > >>>>>> Great idea !
> > >>>>>>
> > >>>>>> Not only it will ease people getting started with felix, but it
> can
> > >>>>>> help convince people giving a try :
> > >>>>>> if your repository.xml refers to an obr2html.xsl file, and you
> show
> > >>>>>> people the repository in a browser, you will have the same "waw"
> > >>>>>> effect as with the old Oscar repository. You see a nice list of
> > >>>>>> already existing bundles, and if you follow the "doc" link it goes
> > >>>>>> to the doc etc..
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> Anne
> > >>>>>>
> > >>>>>> -----Message d'origine-----
> > >>>>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> > >>>>>> Envoyé : samedi 10 mai 2008 11:43
> > >>>>>> À : users@felix.apache.org
> > >>>>>> Objet : Re: obr for felix bundles?
> > >>>>>>
> > >>>>>> Hi Richard,
> > >>>>>>
> > >>>>>> I think it would be great if you can arrange this. I think that
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>> people
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> that are new to OSGi can have a hard time to get started with
> felix
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>> (i
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> noticed this a few times) and i think that being able to install
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>> felix
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> bundles in a simple and convenient way might help.
> > >>>>>>
> > >>>>>> Regards,
> > >>>>>> Peer
> > >>>>>>
> > >>>>>>
> > >>>>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> There currently is not. We definitely need this. It basically
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>> involves
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> determining at least two things:
> > >>>>>>>
> > >>>>>>> 1. How should we go about generating the repo?
> > >>>>>>> * We have the capability to generate OBR repository
> files,
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>> but
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> how do we get one generated for our current set of
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>> released
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>> bundle versions?
> > >>>>>>> 2. Where do we put the repository?
> > >>>>>>>
> > >>>>>>> I don't really know the best way to do (1). As for (2), I am not
> > >>>>>>> sure if it matters, I don't think it needs to be hosted on our
> > >>>>>>> Apache
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>> site.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> I could put the repo on my own personal web site or we could just
> > >>>>>>> put them on the Source Forge web site.
> > >>>>>>>
> > >>>>>>> -> richard
> > >>>>>>>
> > >>>>>>> p.s. Sorry to cross post, it is not necessary to cross post
> > >>>>>>> replies...I just want to make sure that this discussion is seen
> on
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>> the
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>> dev list.
> > >>>>>>>
> > >>>>>>> peter.doornbosch wrote:
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>> Hi,
> > >>>>>>>>
> > >>>>>>>> I wonder if there is an obr repository for the (current versions
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>> of
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>>> the) felix bundles. When i start felix (1.0.4), obr is
> configured
> > >>>>>>>> with the url http://oscar-
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>> osgi.sourceforge.net/obr2/repository.xml,
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>>> which contains only a few really old bundles....
> > >>>>>>>>
> > >>>>>>>> Regards,
> > >>>>>>>> Peter
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> ------------------------------------------------------------------
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>> -
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>>> -
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>> -
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> -------------------------------------------------------------------
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>> -
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>>>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>
> --------------------------------------------------------------------
> > >>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>>
> --------------------------------------------------------------------
> > >>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> ---------------------------------------------------------------------
> > >>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>
> > >>>
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >> For additional commands, e-mail: users-help@felix.apache.org
> > >>
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > For additional commands, e-mail: users-help@felix.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Cheers, Stuart
Re: obr for felix bundles?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
Am Dienstag, den 27.05.2008, 11:25 +0200 schrieb Julien Vermillard:
> Hi,
>
> A lot of Apache project ship OSGi bundles now.
> For the one I know the best, for MINA everything is packaged as bundle
> even AsyncWeb,
> using bnd plugin for maven. So if this kind of OBR appear I'm sure a
> lot of Apache project will
> want to push ther bundles.
>
> Now if we need one repository for everything like maven or repository
> links, well I leave the
> answer to the specialists :) Perhaps infra could help here ?
Sure.
But my point is that we do NOT replicate the actual bundle files but
keep the in the Maven Repository, where they already are. We just create
repository.xml files that refer to the existing bundles in the Maven
Repository.
The repository.xml file is used by the OSGi Bundle Repository (Client if
you wish) to find available and required bundles. It only contains
descriptions of the available bundles in terms of bundle names,
versions, capabilities (Export-Package mostly) and requirements
(Import-Package mostly) and some more attributes. These files tend to be
small compared to the actual bundle files.
Regards
Felix
>
> Julien
>
> 2008/5/26 Felix Meschberger <fm...@gmail.com>:
> > Hi,
> >
> > I have been thinking about this issue and been discussing it with
> > Carsten. And we came up with a very simple solution: The main point is,
> > that the repository.xml file and the artifacts referred to need not be
> > in the same location, right ?
> >
> > Starting from this, the solution would be that we might provide the
> > repository.xml file from the Felix site and have the bundles where they
> > already are: in the maven repository.
> >
> > So upon the release of one of the Felix bundles, we just add a record
> > for the bundle into the repository.xml pointing to the maven repository.
> > That's it, I would say.
> >
> > So far so good. But there will be other projects -- just talking of
> > Apache for the moment, but OPS4J also comes to mind -- which have
> > bundles to distribute. Here comes the <referral> element of the
> > repository.xml file (section 5.5.4 in OSGi RFC 112): We create a central
> > repository.xml file, into which referrals to other projects may be
> > entered. Each project thus maintains its own repository.xml.
> >
> > For example:
> >
> > global-repository.xml
> > ---> referral to Apache Felix repository.xml
> > ---> referral to Apache Sling repository.xml
> > ---> referral to Apache Commons repository.xml
> >
> > I think, this solution can be easily and quickly implemented and does
> > not need too much additional network traffic.
> >
> > A further development step could be to have separate repository.xml
> > files for releases and SNAPSHOTs. We could arrange to update the
> > SNAPSHOT repository.xml file by means of the maven-bundle-plugin (would
> > require to be able to specify the actual location repository.xml file)
> > upon deplyoment of the SNAPSHOTs...
> >
> >
> > WDYT ?
> >
> > Regards
> > Felix
> >
> >
> > Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
> >> If I understand correctly, Clement is proposing something like this:
> >>
> >> releases/
> >> bundleA-v1/
> >> bundleA-v2/
> >> bundleB-v1/
> >> bundleC-v1/
> >> bundleC-v2/
> >> pom.xml
> >>
> >> The above represents the structure of our releases directory. The
> >> pom.xml will refer to the most recent version of each release bundle, e.g.:
> >>
> >> pom.xml
> >> artifactId=bundleA,version=2
> >> artifactId=bundleB,version=1
> >> artifactId=bundleC,version=2
> >>
> >> The purpose of this pom file is largely to document which subprojects
> >> should be made available in our repo. However, if you use it to issue
> >> the mvn deploy command on this pom, then it will deploy the set of all
> >> current releases to the repo.
> >>
> >> This is obviously inefficient if only one bundle has been updated since
> >> it will deploy all bundles. To avoid this, though, you can simply 'cd'
> >> into the precise subproject release directory and issue that mvn deploy
> >> command from there, then only the newly released bundle will be deployed.
> >>
> >> Clearly, this process is simplistic, but it is probably better than
> >> nothing, which is the current approach. The idea here is that we could
> >> just incorporate it as part of our normal release process, where after
> >> we tag a released bundle in the releases directory, then we update the
> >> version in the pom.xml and then deploy it to the repo.
> >>
> >> What do you think?
> >>
> >> -> richard
> >>
> >> anne.gerodolle@orange-ftgroup.com wrote:
> >> > If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
> >> >
> >> > Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
> >> >
> >> > This means using the same kind of command line as Clement, but at a subproject level (not at the root):
> >> > mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
> >> >
> >> > I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
> >> >
> >> > Regards,
> >> >
> >> > Anne
> >> >
> >> > -----Message d'origine-----
> >> > De : Richard S. Hall [mailto:heavy@ungoverned.org]
> >> > Envoyé : jeudi 15 mai 2008 15:43
> >> > À : users@felix.apache.org; dev@felix.apache.org
> >> > Objet : Re: obr for felix bundles?
> >> >
> >> > I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
> >> >
> >> > -> richard
> >> >
> >> > Clement Escoffier wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I change the XSLT file, now there is colors :-)
> >> >>
> >> >> Clement
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>> -----Message d'origine-----
> >> >>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> >> >>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
> >> >>> users@felix.apache.org Objet : RE: obr for felix bundles?
> >> >>>
> >> >>> Hi Clement !
> >> >>> I have personally a slight preference for the stylesheet coming from
> >> >>> the OSGi Web site (attached file) .
> >> >>> Apart from the style itself (better for presbyopian eyes), it sorts
> >> >>> the bundles alphabetically. I see you have commented this feature in
> >> >>> yuor xsl file.
> >> >>> Of course that's a matter of personal preference, and that's not the
> >> >>> main point !
> >> >>> Best regards,
> >> >>> Anne
> >> >>> -----Message d'origine-----
> >> >>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
> >> >>> Envoyé : jeudi 15 mai 2008 03:42
> >> >>> À : users@felix.apache.org
> >> >>> Objet : RE: obr for felix bundles?
> >> >>>
> >> >>> Hello,
> >> >>>
> >> >>> I attach the Didier's XSLT stylesheet to the generated XML file.
> >> >>> The result is available here :
> >> >>> http://plop-plop.net/obr/repository.xml
> >> >>>
> >> >>> Clement
> >> >>>
> >> >>>
> >> >>>
> >> >>>> -----Message d'origine-----
> >> >>>> De : anne.gerodolle@orange-ftgroup.com
> >> >>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
> >> >>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> >> >>>>
> >> >>>> Great idea !
> >> >>>>
> >> >>>> Not only it will ease people getting started with felix, but it can
> >> >>>> help convince people giving a try :
> >> >>>> if your repository.xml refers to an obr2html.xsl file, and you show
> >> >>>> people the repository in a browser, you will have the same "waw"
> >> >>>> effect as with the old Oscar repository. You see a nice list of
> >> >>>> already existing bundles, and if you follow the "doc" link it goes
> >> >>>> to the doc etc..
> >> >>>>
> >> >>>> Regards,
> >> >>>> Anne
> >> >>>>
> >> >>>> -----Message d'origine-----
> >> >>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> >> >>>> Envoyé : samedi 10 mai 2008 11:43
> >> >>>> À : users@felix.apache.org
> >> >>>> Objet : Re: obr for felix bundles?
> >> >>>>
> >> >>>> Hi Richard,
> >> >>>>
> >> >>>> I think it would be great if you can arrange this. I think that
> >> >>>>
> >> >>>>
> >> >>> people
> >> >>>
> >> >>>
> >> >>>> that are new to OSGi can have a hard time to get started with felix
> >> >>>>
> >> >>>>
> >> >>> (i
> >> >>>
> >> >>>
> >> >>>> noticed this a few times) and i think that being able to install
> >> >>>>
> >> >>>>
> >> >>> felix
> >> >>>
> >> >>>
> >> >>>> bundles in a simple and convenient way might help.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Peer
> >> >>>>
> >> >>>>
> >> >>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> >> >>>>
> >> >>>>
> >> >>>>> There currently is not. We definitely need this. It basically
> >> >>>>>
> >> >>>>>
> >> >>>> involves
> >> >>>>
> >> >>>>
> >> >>>>> determining at least two things:
> >> >>>>>
> >> >>>>> 1. How should we go about generating the repo?
> >> >>>>> * We have the capability to generate OBR repository files,
> >> >>>>>
> >> >>>>>
> >> >>>> but
> >> >>>>
> >> >>>>
> >> >>>>> how do we get one generated for our current set of
> >> >>>>>
> >> >>>>>
> >> >>> released
> >> >>>
> >> >>>
> >> >>>>> bundle versions?
> >> >>>>> 2. Where do we put the repository?
> >> >>>>>
> >> >>>>> I don't really know the best way to do (1). As for (2), I am not
> >> >>>>> sure if it matters, I don't think it needs to be hosted on our
> >> >>>>> Apache
> >> >>>>>
> >> >>>>>
> >> >>>> site.
> >> >>>>
> >> >>>>
> >> >>>>> I could put the repo on my own personal web site or we could just
> >> >>>>> put them on the Source Forge web site.
> >> >>>>>
> >> >>>>> -> richard
> >> >>>>>
> >> >>>>> p.s. Sorry to cross post, it is not necessary to cross post
> >> >>>>> replies...I just want to make sure that this discussion is seen on
> >> >>>>>
> >> >>>>>
> >> >>>> the
> >> >>>>
> >> >>>>
> >> >>>>> dev list.
> >> >>>>>
> >> >>>>> peter.doornbosch wrote:
> >> >>>>>
> >> >>>>>
> >> >>>>>> Hi,
> >> >>>>>>
> >> >>>>>> I wonder if there is an obr repository for the (current versions
> >> >>>>>>
> >> >>>>>>
> >> >>> of
> >> >>>
> >> >>>
> >> >>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
> >> >>>>>> with the url http://oscar-
> >> >>>>>>
> >> >>>>>>
> >> >>> osgi.sourceforge.net/obr2/repository.xml,
> >> >>>
> >> >>>
> >> >>>>>> which contains only a few really old bundles....
> >> >>>>>>
> >> >>>>>> Regards,
> >> >>>>>> Peter
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> ------------------------------------------------------------------
> >> >>>>>>
> >> >>>>>>
> >> >>> -
> >> >>>
> >> >>>
> >> >>>>>> -
> >> >>>>>>
> >> >>>>>>
> >> >>>> -
> >> >>>>
> >> >>>>
> >> >>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> >> >>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>> -------------------------------------------------------------------
> >> >>>>>
> >> >>>>>
> >> >>> -
> >> >>>
> >> >>>
> >> >>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> >>>>> For additional commands, e-mail: users-help@felix.apache.org
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>> --------------------------------------------------------------------
> >> >>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >> >>>>
> >> >>>>
> >> >>>> --------------------------------------------------------------------
> >> >>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >> >>>>
> >> >>>>
> >> >>> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> >>> For additional commands, e-mail: users-help@felix.apache.org
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> >> For additional commands, e-mail: users-help@felix.apache.org
> >> >>
> >> >>
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> > For additional commands, e-mail: users-help@felix.apache.org
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> > For additional commands, e-mail: users-help@felix.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Julien Vermillard <jv...@apache.org>.
Hi,
A lot of Apache project ship OSGi bundles now.
For the one I know the best, for MINA everything is packaged as bundle
even AsyncWeb,
using bnd plugin for maven. So if this kind of OBR appear I'm sure a
lot of Apache project will
want to push ther bundles.
Now if we need one repository for everything like maven or repository
links, well I leave the
answer to the specialists :) Perhaps infra could help here ?
Julien
2008/5/26 Felix Meschberger <fm...@gmail.com>:
> Hi,
>
> I have been thinking about this issue and been discussing it with
> Carsten. And we came up with a very simple solution: The main point is,
> that the repository.xml file and the artifacts referred to need not be
> in the same location, right ?
>
> Starting from this, the solution would be that we might provide the
> repository.xml file from the Felix site and have the bundles where they
> already are: in the maven repository.
>
> So upon the release of one of the Felix bundles, we just add a record
> for the bundle into the repository.xml pointing to the maven repository.
> That's it, I would say.
>
> So far so good. But there will be other projects -- just talking of
> Apache for the moment, but OPS4J also comes to mind -- which have
> bundles to distribute. Here comes the <referral> element of the
> repository.xml file (section 5.5.4 in OSGi RFC 112): We create a central
> repository.xml file, into which referrals to other projects may be
> entered. Each project thus maintains its own repository.xml.
>
> For example:
>
> global-repository.xml
> ---> referral to Apache Felix repository.xml
> ---> referral to Apache Sling repository.xml
> ---> referral to Apache Commons repository.xml
>
> I think, this solution can be easily and quickly implemented and does
> not need too much additional network traffic.
>
> A further development step could be to have separate repository.xml
> files for releases and SNAPSHOTs. We could arrange to update the
> SNAPSHOT repository.xml file by means of the maven-bundle-plugin (would
> require to be able to specify the actual location repository.xml file)
> upon deplyoment of the SNAPSHOTs...
>
>
> WDYT ?
>
> Regards
> Felix
>
>
> Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
>> If I understand correctly, Clement is proposing something like this:
>>
>> releases/
>> bundleA-v1/
>> bundleA-v2/
>> bundleB-v1/
>> bundleC-v1/
>> bundleC-v2/
>> pom.xml
>>
>> The above represents the structure of our releases directory. The
>> pom.xml will refer to the most recent version of each release bundle, e.g.:
>>
>> pom.xml
>> artifactId=bundleA,version=2
>> artifactId=bundleB,version=1
>> artifactId=bundleC,version=2
>>
>> The purpose of this pom file is largely to document which subprojects
>> should be made available in our repo. However, if you use it to issue
>> the mvn deploy command on this pom, then it will deploy the set of all
>> current releases to the repo.
>>
>> This is obviously inefficient if only one bundle has been updated since
>> it will deploy all bundles. To avoid this, though, you can simply 'cd'
>> into the precise subproject release directory and issue that mvn deploy
>> command from there, then only the newly released bundle will be deployed.
>>
>> Clearly, this process is simplistic, but it is probably better than
>> nothing, which is the current approach. The idea here is that we could
>> just incorporate it as part of our normal release process, where after
>> we tag a released bundle in the releases directory, then we update the
>> version in the pom.xml and then deploy it to the repo.
>>
>> What do you think?
>>
>> -> richard
>>
>> anne.gerodolle@orange-ftgroup.com wrote:
>> > If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
>> >
>> > Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
>> >
>> > This means using the same kind of command line as Clement, but at a subproject level (not at the root):
>> > mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
>> >
>> > I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
>> >
>> > Regards,
>> >
>> > Anne
>> >
>> > -----Message d'origine-----
>> > De : Richard S. Hall [mailto:heavy@ungoverned.org]
>> > Envoyé : jeudi 15 mai 2008 15:43
>> > À : users@felix.apache.org; dev@felix.apache.org
>> > Objet : Re: obr for felix bundles?
>> >
>> > I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
>> >
>> > -> richard
>> >
>> > Clement Escoffier wrote:
>> >
>> >> Hi,
>> >>
>> >> I change the XSLT file, now there is colors :-)
>> >>
>> >> Clement
>> >>
>> >>
>> >>
>> >>
>> >>> -----Message d'origine-----
>> >>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>> >>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
>> >>> users@felix.apache.org Objet : RE: obr for felix bundles?
>> >>>
>> >>> Hi Clement !
>> >>> I have personally a slight preference for the stylesheet coming from
>> >>> the OSGi Web site (attached file) .
>> >>> Apart from the style itself (better for presbyopian eyes), it sorts
>> >>> the bundles alphabetically. I see you have commented this feature in
>> >>> yuor xsl file.
>> >>> Of course that's a matter of personal preference, and that's not the
>> >>> main point !
>> >>> Best regards,
>> >>> Anne
>> >>> -----Message d'origine-----
>> >>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
>> >>> Envoyé : jeudi 15 mai 2008 03:42
>> >>> À : users@felix.apache.org
>> >>> Objet : RE: obr for felix bundles?
>> >>>
>> >>> Hello,
>> >>>
>> >>> I attach the Didier's XSLT stylesheet to the generated XML file.
>> >>> The result is available here :
>> >>> http://plop-plop.net/obr/repository.xml
>> >>>
>> >>> Clement
>> >>>
>> >>>
>> >>>
>> >>>> -----Message d'origine-----
>> >>>> De : anne.gerodolle@orange-ftgroup.com
>> >>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
>> >>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>> >>>>
>> >>>> Great idea !
>> >>>>
>> >>>> Not only it will ease people getting started with felix, but it can
>> >>>> help convince people giving a try :
>> >>>> if your repository.xml refers to an obr2html.xsl file, and you show
>> >>>> people the repository in a browser, you will have the same "waw"
>> >>>> effect as with the old Oscar repository. You see a nice list of
>> >>>> already existing bundles, and if you follow the "doc" link it goes
>> >>>> to the doc etc..
>> >>>>
>> >>>> Regards,
>> >>>> Anne
>> >>>>
>> >>>> -----Message d'origine-----
>> >>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
>> >>>> Envoyé : samedi 10 mai 2008 11:43
>> >>>> À : users@felix.apache.org
>> >>>> Objet : Re: obr for felix bundles?
>> >>>>
>> >>>> Hi Richard,
>> >>>>
>> >>>> I think it would be great if you can arrange this. I think that
>> >>>>
>> >>>>
>> >>> people
>> >>>
>> >>>
>> >>>> that are new to OSGi can have a hard time to get started with felix
>> >>>>
>> >>>>
>> >>> (i
>> >>>
>> >>>
>> >>>> noticed this a few times) and i think that being able to install
>> >>>>
>> >>>>
>> >>> felix
>> >>>
>> >>>
>> >>>> bundles in a simple and convenient way might help.
>> >>>>
>> >>>> Regards,
>> >>>> Peer
>> >>>>
>> >>>>
>> >>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
>> >>>>
>> >>>>
>> >>>>> There currently is not. We definitely need this. It basically
>> >>>>>
>> >>>>>
>> >>>> involves
>> >>>>
>> >>>>
>> >>>>> determining at least two things:
>> >>>>>
>> >>>>> 1. How should we go about generating the repo?
>> >>>>> * We have the capability to generate OBR repository files,
>> >>>>>
>> >>>>>
>> >>>> but
>> >>>>
>> >>>>
>> >>>>> how do we get one generated for our current set of
>> >>>>>
>> >>>>>
>> >>> released
>> >>>
>> >>>
>> >>>>> bundle versions?
>> >>>>> 2. Where do we put the repository?
>> >>>>>
>> >>>>> I don't really know the best way to do (1). As for (2), I am not
>> >>>>> sure if it matters, I don't think it needs to be hosted on our
>> >>>>> Apache
>> >>>>>
>> >>>>>
>> >>>> site.
>> >>>>
>> >>>>
>> >>>>> I could put the repo on my own personal web site or we could just
>> >>>>> put them on the Source Forge web site.
>> >>>>>
>> >>>>> -> richard
>> >>>>>
>> >>>>> p.s. Sorry to cross post, it is not necessary to cross post
>> >>>>> replies...I just want to make sure that this discussion is seen on
>> >>>>>
>> >>>>>
>> >>>> the
>> >>>>
>> >>>>
>> >>>>> dev list.
>> >>>>>
>> >>>>> peter.doornbosch wrote:
>> >>>>>
>> >>>>>
>> >>>>>> Hi,
>> >>>>>>
>> >>>>>> I wonder if there is an obr repository for the (current versions
>> >>>>>>
>> >>>>>>
>> >>> of
>> >>>
>> >>>
>> >>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>> >>>>>> with the url http://oscar-
>> >>>>>>
>> >>>>>>
>> >>> osgi.sourceforge.net/obr2/repository.xml,
>> >>>
>> >>>
>> >>>>>> which contains only a few really old bundles....
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>> Peter
>> >>>>>>
>> >>>>>>
>> >>>>>> ------------------------------------------------------------------
>> >>>>>>
>> >>>>>>
>> >>> -
>> >>>
>> >>>
>> >>>>>> -
>> >>>>>>
>> >>>>>>
>> >>>> -
>> >>>>
>> >>>>
>> >>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> >>>>>> For additional commands, e-mail: users-help@felix.apache.org
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>> -------------------------------------------------------------------
>> >>>>>
>> >>>>>
>> >>> -
>> >>>
>> >>>
>> >>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> >>>>> For additional commands, e-mail: users-help@felix.apache.org
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>> --------------------------------------------------------------------
>> >>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> >>>> For additional commands, e-mail: users-help@felix.apache.org
>> >>>>
>> >>>>
>> >>>> --------------------------------------------------------------------
>> >>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> >>>> For additional commands, e-mail: users-help@felix.apache.org
>> >>>>
>> >>>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> >>> For additional commands, e-mail: users-help@felix.apache.org
>> >>>
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> >> For additional commands, e-mail: users-help@felix.apache.org
>> >>
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> > For additional commands, e-mail: users-help@felix.apache.org
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> > For additional commands, e-mail: users-help@felix.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Richard,
Am Dienstag, den 27.05.2008, 21:55 -0400 schrieb Richard S. Hall:
> Felix,
>
> I don't have a problem with this approach (or any approach for that matter).
>
> My only request is that we devise a method that is easy for us to update
> any time we have a new release.
That would be mine, too. Clement seems to be working on a maven plugin
to update repository.xml files, with entries of deployed artifacts with
absolute URIs such that the repository.xml need not be located at the
maven repository root.
Regards
Felix
>
> -> richard
>
> Felix Meschberger wrote:
> > Hi,
> >
> > I have been thinking about this issue and been discussing it with
> > Carsten. And we came up with a very simple solution: The main point is,
> > that the repository.xml file and the artifacts referred to need not be
> > in the same location, right ?
> >
> > Starting from this, the solution would be that we might provide the
> > repository.xml file from the Felix site and have the bundles where they
> > already are: in the maven repository.
> >
> > So upon the release of one of the Felix bundles, we just add a record
> > for the bundle into the repository.xml pointing to the maven repository.
> > That's it, I would say.
> >
> > So far so good. But there will be other projects -- just talking of
> > Apache for the moment, but OPS4J also comes to mind -- which have
> > bundles to distribute. Here comes the <referral> element of the
> > repository.xml file (section 5.5.4 in OSGi RFC 112): We create a central
> > repository.xml file, into which referrals to other projects may be
> > entered. Each project thus maintains its own repository.xml.
> >
> > For example:
> >
> > global-repository.xml
> > ---> referral to Apache Felix repository.xml
> > ---> referral to Apache Sling repository.xml
> > ---> referral to Apache Commons repository.xml
> >
> > I think, this solution can be easily and quickly implemented and does
> > not need too much additional network traffic.
> >
> > A further development step could be to have separate repository.xml
> > files for releases and SNAPSHOTs. We could arrange to update the
> > SNAPSHOT repository.xml file by means of the maven-bundle-plugin (would
> > require to be able to specify the actual location repository.xml file)
> > upon deplyoment of the SNAPSHOTs...
> >
> >
> > WDYT ?
> >
> > Regards
> > Felix
> >
> >
> > Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
> >
> >> If I understand correctly, Clement is proposing something like this:
> >>
> >> releases/
> >> bundleA-v1/
> >> bundleA-v2/
> >> bundleB-v1/
> >> bundleC-v1/
> >> bundleC-v2/
> >> pom.xml
> >>
> >> The above represents the structure of our releases directory. The
> >> pom.xml will refer to the most recent version of each release bundle, e.g.:
> >>
> >> pom.xml
> >> artifactId=bundleA,version=2
> >> artifactId=bundleB,version=1
> >> artifactId=bundleC,version=2
> >>
> >> The purpose of this pom file is largely to document which subprojects
> >> should be made available in our repo. However, if you use it to issue
> >> the mvn deploy command on this pom, then it will deploy the set of all
> >> current releases to the repo.
> >>
> >> This is obviously inefficient if only one bundle has been updated since
> >> it will deploy all bundles. To avoid this, though, you can simply 'cd'
> >> into the precise subproject release directory and issue that mvn deploy
> >> command from there, then only the newly released bundle will be deployed.
> >>
> >> Clearly, this process is simplistic, but it is probably better than
> >> nothing, which is the current approach. The idea here is that we could
> >> just incorporate it as part of our normal release process, where after
> >> we tag a released bundle in the releases directory, then we update the
> >> version in the pom.xml and then deploy it to the repo.
> >>
> >> What do you think?
> >>
> >> -> richard
> >>
> >> anne.gerodolle@orange-ftgroup.com wrote:
> >>
> >>> If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
> >>>
> >>> Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
> >>>
> >>> This means using the same kind of command line as Clement, but at a subproject level (not at the root):
> >>> mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
> >>>
> >>> I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
> >>>
> >>> Regards,
> >>>
> >>> Anne
> >>>
> >>> -----Message d'origine-----
> >>> De : Richard S. Hall [mailto:heavy@ungoverned.org]
> >>> Envoyé : jeudi 15 mai 2008 15:43
> >>> À : users@felix.apache.org; dev@felix.apache.org
> >>> Objet : Re: obr for felix bundles?
> >>>
> >>> I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
> >>>
> >>> -> richard
> >>>
> >>> Clement Escoffier wrote:
> >>>
> >>>
> >>>> Hi,
> >>>>
> >>>> I change the XSLT file, now there is colors :-)
> >>>>
> >>>> Clement
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> -----Message d'origine-----
> >>>>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> >>>>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
> >>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> >>>>>
> >>>>> Hi Clement !
> >>>>> I have personally a slight preference for the stylesheet coming from
> >>>>> the OSGi Web site (attached file) .
> >>>>> Apart from the style itself (better for presbyopian eyes), it sorts
> >>>>> the bundles alphabetically. I see you have commented this feature in
> >>>>> yuor xsl file.
> >>>>> Of course that's a matter of personal preference, and that's not the
> >>>>> main point !
> >>>>> Best regards,
> >>>>> Anne
> >>>>> -----Message d'origine-----
> >>>>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
> >>>>> Envoyé : jeudi 15 mai 2008 03:42
> >>>>> À : users@felix.apache.org
> >>>>> Objet : RE: obr for felix bundles?
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> I attach the Didier's XSLT stylesheet to the generated XML file.
> >>>>> The result is available here :
> >>>>> http://plop-plop.net/obr/repository.xml
> >>>>>
> >>>>> Clement
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> -----Message d'origine-----
> >>>>>> De : anne.gerodolle@orange-ftgroup.com
> >>>>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
> >>>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> >>>>>>
> >>>>>> Great idea !
> >>>>>>
> >>>>>> Not only it will ease people getting started with felix, but it can
> >>>>>> help convince people giving a try :
> >>>>>> if your repository.xml refers to an obr2html.xsl file, and you show
> >>>>>> people the repository in a browser, you will have the same "waw"
> >>>>>> effect as with the old Oscar repository. You see a nice list of
> >>>>>> already existing bundles, and if you follow the "doc" link it goes
> >>>>>> to the doc etc..
> >>>>>>
> >>>>>> Regards,
> >>>>>> Anne
> >>>>>>
> >>>>>> -----Message d'origine-----
> >>>>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> >>>>>> Envoyé : samedi 10 mai 2008 11:43
> >>>>>> À : users@felix.apache.org
> >>>>>> Objet : Re: obr for felix bundles?
> >>>>>>
> >>>>>> Hi Richard,
> >>>>>>
> >>>>>> I think it would be great if you can arrange this. I think that
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> people
> >>>>>
> >>>>>
> >>>>>
> >>>>>> that are new to OSGi can have a hard time to get started with felix
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> (i
> >>>>>
> >>>>>
> >>>>>
> >>>>>> noticed this a few times) and i think that being able to install
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> felix
> >>>>>
> >>>>>
> >>>>>
> >>>>>> bundles in a simple and convenient way might help.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Peer
> >>>>>>
> >>>>>>
> >>>>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> There currently is not. We definitely need this. It basically
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> involves
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> determining at least two things:
> >>>>>>>
> >>>>>>> 1. How should we go about generating the repo?
> >>>>>>> * We have the capability to generate OBR repository files,
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> but
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> how do we get one generated for our current set of
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>> released
> >>>>>
> >>>>>
> >>>>>
> >>>>>>> bundle versions?
> >>>>>>> 2. Where do we put the repository?
> >>>>>>>
> >>>>>>> I don't really know the best way to do (1). As for (2), I am not
> >>>>>>> sure if it matters, I don't think it needs to be hosted on our
> >>>>>>> Apache
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> site.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> I could put the repo on my own personal web site or we could just
> >>>>>>> put them on the Source Forge web site.
> >>>>>>>
> >>>>>>> -> richard
> >>>>>>>
> >>>>>>> p.s. Sorry to cross post, it is not necessary to cross post
> >>>>>>> replies...I just want to make sure that this discussion is seen on
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> the
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> dev list.
> >>>>>>>
> >>>>>>> peter.doornbosch wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> I wonder if there is an obr repository for the (current versions
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>> of
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
> >>>>>>>> with the url http://oscar-
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>> osgi.sourceforge.net/obr2/repository.xml,
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>> which contains only a few really old bundles....
> >>>>>>>>
> >>>>>>>> Regards,
> >>>>>>>> Peter
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ------------------------------------------------------------------
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>> -
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>> -
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>> -
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>> -------------------------------------------------------------------
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>> -
> >>>>>
> >>>>>
> >>>>>
> >>>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> --------------------------------------------------------------------
> >>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>>
> >>>>>>
> >>>>>> --------------------------------------------------------------------
> >>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>
> >>>>
> >>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Felix,
I don't have a problem with this approach (or any approach for that matter).
My only request is that we devise a method that is easy for us to update
any time we have a new release.
-> richard
Felix Meschberger wrote:
> Hi,
>
> I have been thinking about this issue and been discussing it with
> Carsten. And we came up with a very simple solution: The main point is,
> that the repository.xml file and the artifacts referred to need not be
> in the same location, right ?
>
> Starting from this, the solution would be that we might provide the
> repository.xml file from the Felix site and have the bundles where they
> already are: in the maven repository.
>
> So upon the release of one of the Felix bundles, we just add a record
> for the bundle into the repository.xml pointing to the maven repository.
> That's it, I would say.
>
> So far so good. But there will be other projects -- just talking of
> Apache for the moment, but OPS4J also comes to mind -- which have
> bundles to distribute. Here comes the <referral> element of the
> repository.xml file (section 5.5.4 in OSGi RFC 112): We create a central
> repository.xml file, into which referrals to other projects may be
> entered. Each project thus maintains its own repository.xml.
>
> For example:
>
> global-repository.xml
> ---> referral to Apache Felix repository.xml
> ---> referral to Apache Sling repository.xml
> ---> referral to Apache Commons repository.xml
>
> I think, this solution can be easily and quickly implemented and does
> not need too much additional network traffic.
>
> A further development step could be to have separate repository.xml
> files for releases and SNAPSHOTs. We could arrange to update the
> SNAPSHOT repository.xml file by means of the maven-bundle-plugin (would
> require to be able to specify the actual location repository.xml file)
> upon deplyoment of the SNAPSHOTs...
>
>
> WDYT ?
>
> Regards
> Felix
>
>
> Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
>
>> If I understand correctly, Clement is proposing something like this:
>>
>> releases/
>> bundleA-v1/
>> bundleA-v2/
>> bundleB-v1/
>> bundleC-v1/
>> bundleC-v2/
>> pom.xml
>>
>> The above represents the structure of our releases directory. The
>> pom.xml will refer to the most recent version of each release bundle, e.g.:
>>
>> pom.xml
>> artifactId=bundleA,version=2
>> artifactId=bundleB,version=1
>> artifactId=bundleC,version=2
>>
>> The purpose of this pom file is largely to document which subprojects
>> should be made available in our repo. However, if you use it to issue
>> the mvn deploy command on this pom, then it will deploy the set of all
>> current releases to the repo.
>>
>> This is obviously inefficient if only one bundle has been updated since
>> it will deploy all bundles. To avoid this, though, you can simply 'cd'
>> into the precise subproject release directory and issue that mvn deploy
>> command from there, then only the newly released bundle will be deployed.
>>
>> Clearly, this process is simplistic, but it is probably better than
>> nothing, which is the current approach. The idea here is that we could
>> just incorporate it as part of our normal release process, where after
>> we tag a released bundle in the releases directory, then we update the
>> version in the pom.xml and then deploy it to the repo.
>>
>> What do you think?
>>
>> -> richard
>>
>> anne.gerodolle@orange-ftgroup.com wrote:
>>
>>> If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
>>>
>>> Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
>>>
>>> This means using the same kind of command line as Clement, but at a subproject level (not at the root):
>>> mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
>>>
>>> I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
>>>
>>> Regards,
>>>
>>> Anne
>>>
>>> -----Message d'origine-----
>>> De : Richard S. Hall [mailto:heavy@ungoverned.org]
>>> Envoyé : jeudi 15 mai 2008 15:43
>>> À : users@felix.apache.org; dev@felix.apache.org
>>> Objet : Re: obr for felix bundles?
>>>
>>> I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
>>>
>>> -> richard
>>>
>>> Clement Escoffier wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> I change the XSLT file, now there is colors :-)
>>>>
>>>> Clement
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> -----Message d'origine-----
>>>>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>>>>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
>>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>>>
>>>>> Hi Clement !
>>>>> I have personally a slight preference for the stylesheet coming from
>>>>> the OSGi Web site (attached file) .
>>>>> Apart from the style itself (better for presbyopian eyes), it sorts
>>>>> the bundles alphabetically. I see you have commented this feature in
>>>>> yuor xsl file.
>>>>> Of course that's a matter of personal preference, and that's not the
>>>>> main point !
>>>>> Best regards,
>>>>> Anne
>>>>> -----Message d'origine-----
>>>>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
>>>>> Envoyé : jeudi 15 mai 2008 03:42
>>>>> À : users@felix.apache.org
>>>>> Objet : RE: obr for felix bundles?
>>>>>
>>>>> Hello,
>>>>>
>>>>> I attach the Didier's XSLT stylesheet to the generated XML file.
>>>>> The result is available here :
>>>>> http://plop-plop.net/obr/repository.xml
>>>>>
>>>>> Clement
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : anne.gerodolle@orange-ftgroup.com
>>>>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
>>>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>>>>
>>>>>> Great idea !
>>>>>>
>>>>>> Not only it will ease people getting started with felix, but it can
>>>>>> help convince people giving a try :
>>>>>> if your repository.xml refers to an obr2html.xsl file, and you show
>>>>>> people the repository in a browser, you will have the same "waw"
>>>>>> effect as with the old Oscar repository. You see a nice list of
>>>>>> already existing bundles, and if you follow the "doc" link it goes
>>>>>> to the doc etc..
>>>>>>
>>>>>> Regards,
>>>>>> Anne
>>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
>>>>>> Envoyé : samedi 10 mai 2008 11:43
>>>>>> À : users@felix.apache.org
>>>>>> Objet : Re: obr for felix bundles?
>>>>>>
>>>>>> Hi Richard,
>>>>>>
>>>>>> I think it would be great if you can arrange this. I think that
>>>>>>
>>>>>>
>>>>>>
>>>>> people
>>>>>
>>>>>
>>>>>
>>>>>> that are new to OSGi can have a hard time to get started with felix
>>>>>>
>>>>>>
>>>>>>
>>>>> (i
>>>>>
>>>>>
>>>>>
>>>>>> noticed this a few times) and i think that being able to install
>>>>>>
>>>>>>
>>>>>>
>>>>> felix
>>>>>
>>>>>
>>>>>
>>>>>> bundles in a simple and convenient way might help.
>>>>>>
>>>>>> Regards,
>>>>>> Peer
>>>>>>
>>>>>>
>>>>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> There currently is not. We definitely need this. It basically
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> involves
>>>>>>
>>>>>>
>>>>>>
>>>>>>> determining at least two things:
>>>>>>>
>>>>>>> 1. How should we go about generating the repo?
>>>>>>> * We have the capability to generate OBR repository files,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> but
>>>>>>
>>>>>>
>>>>>>
>>>>>>> how do we get one generated for our current set of
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> released
>>>>>
>>>>>
>>>>>
>>>>>>> bundle versions?
>>>>>>> 2. Where do we put the repository?
>>>>>>>
>>>>>>> I don't really know the best way to do (1). As for (2), I am not
>>>>>>> sure if it matters, I don't think it needs to be hosted on our
>>>>>>> Apache
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> site.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I could put the repo on my own personal web site or we could just
>>>>>>> put them on the Source Forge web site.
>>>>>>>
>>>>>>> -> richard
>>>>>>>
>>>>>>> p.s. Sorry to cross post, it is not necessary to cross post
>>>>>>> replies...I just want to make sure that this discussion is seen on
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> the
>>>>>>
>>>>>>
>>>>>>
>>>>>>> dev list.
>>>>>>>
>>>>>>> peter.doornbosch wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I wonder if there is an obr repository for the (current versions
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> of
>>>>>
>>>>>
>>>>>
>>>>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>>>>>>>> with the url http://oscar-
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> osgi.sourceforge.net/obr2/repository.xml,
>>>>>
>>>>>
>>>>>
>>>>>>>> which contains only a few really old bundles....
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Peter
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>> -
>>>>>
>>>>>
>>>>>
>>>>>>>> -
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> -
>>>>>>
>>>>>>
>>>>>>
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> -------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> -
>>>>>
>>>>>
>>>>>
>>>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi,
I have been thinking about this issue and been discussing it with
Carsten. And we came up with a very simple solution: The main point is,
that the repository.xml file and the artifacts referred to need not be
in the same location, right ?
Starting from this, the solution would be that we might provide the
repository.xml file from the Felix site and have the bundles where they
already are: in the maven repository.
So upon the release of one of the Felix bundles, we just add a record
for the bundle into the repository.xml pointing to the maven repository.
That's it, I would say.
So far so good. But there will be other projects -- just talking of
Apache for the moment, but OPS4J also comes to mind -- which have
bundles to distribute. Here comes the <referral> element of the
repository.xml file (section 5.5.4 in OSGi RFC 112): We create a central
repository.xml file, into which referrals to other projects may be
entered. Each project thus maintains its own repository.xml.
For example:
global-repository.xml
---> referral to Apache Felix repository.xml
---> referral to Apache Sling repository.xml
---> referral to Apache Commons repository.xml
I think, this solution can be easily and quickly implemented and does
not need too much additional network traffic.
A further development step could be to have separate repository.xml
files for releases and SNAPSHOTs. We could arrange to update the
SNAPSHOT repository.xml file by means of the maven-bundle-plugin (would
require to be able to specify the actual location repository.xml file)
upon deplyoment of the SNAPSHOTs...
WDYT ?
Regards
Felix
Am Freitag, den 16.05.2008, 10:40 -0400 schrieb Richard S. Hall:
> If I understand correctly, Clement is proposing something like this:
>
> releases/
> bundleA-v1/
> bundleA-v2/
> bundleB-v1/
> bundleC-v1/
> bundleC-v2/
> pom.xml
>
> The above represents the structure of our releases directory. The
> pom.xml will refer to the most recent version of each release bundle, e.g.:
>
> pom.xml
> artifactId=bundleA,version=2
> artifactId=bundleB,version=1
> artifactId=bundleC,version=2
>
> The purpose of this pom file is largely to document which subprojects
> should be made available in our repo. However, if you use it to issue
> the mvn deploy command on this pom, then it will deploy the set of all
> current releases to the repo.
>
> This is obviously inefficient if only one bundle has been updated since
> it will deploy all bundles. To avoid this, though, you can simply 'cd'
> into the precise subproject release directory and issue that mvn deploy
> command from there, then only the newly released bundle will be deployed.
>
> Clearly, this process is simplistic, but it is probably better than
> nothing, which is the current approach. The idea here is that we could
> just incorporate it as part of our normal release process, where after
> we tag a released bundle in the releases directory, then we update the
> version in the pom.xml and then deploy it to the repo.
>
> What do you think?
>
> -> richard
>
> anne.gerodolle@orange-ftgroup.com wrote:
> > If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
> >
> > Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
> >
> > This means using the same kind of command line as Clement, but at a subproject level (not at the root):
> > mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
> >
> > I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
> >
> > Regards,
> >
> > Anne
> >
> > -----Message d'origine-----
> > De : Richard S. Hall [mailto:heavy@ungoverned.org]
> > Envoyé : jeudi 15 mai 2008 15:43
> > À : users@felix.apache.org; dev@felix.apache.org
> > Objet : Re: obr for felix bundles?
> >
> > I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
> >
> > -> richard
> >
> > Clement Escoffier wrote:
> >
> >> Hi,
> >>
> >> I change the XSLT file, now there is colors :-)
> >>
> >> Clement
> >>
> >>
> >>
> >>
> >>> -----Message d'origine-----
> >>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> >>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
> >>> users@felix.apache.org Objet : RE: obr for felix bundles?
> >>>
> >>> Hi Clement !
> >>> I have personally a slight preference for the stylesheet coming from
> >>> the OSGi Web site (attached file) .
> >>> Apart from the style itself (better for presbyopian eyes), it sorts
> >>> the bundles alphabetically. I see you have commented this feature in
> >>> yuor xsl file.
> >>> Of course that's a matter of personal preference, and that's not the
> >>> main point !
> >>> Best regards,
> >>> Anne
> >>> -----Message d'origine-----
> >>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
> >>> Envoyé : jeudi 15 mai 2008 03:42
> >>> À : users@felix.apache.org
> >>> Objet : RE: obr for felix bundles?
> >>>
> >>> Hello,
> >>>
> >>> I attach the Didier's XSLT stylesheet to the generated XML file.
> >>> The result is available here :
> >>> http://plop-plop.net/obr/repository.xml
> >>>
> >>> Clement
> >>>
> >>>
> >>>
> >>>> -----Message d'origine-----
> >>>> De : anne.gerodolle@orange-ftgroup.com
> >>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
> >>>> users@felix.apache.org Objet : RE: obr for felix bundles?
> >>>>
> >>>> Great idea !
> >>>>
> >>>> Not only it will ease people getting started with felix, but it can
> >>>> help convince people giving a try :
> >>>> if your repository.xml refers to an obr2html.xsl file, and you show
> >>>> people the repository in a browser, you will have the same "waw"
> >>>> effect as with the old Oscar repository. You see a nice list of
> >>>> already existing bundles, and if you follow the "doc" link it goes
> >>>> to the doc etc..
> >>>>
> >>>> Regards,
> >>>> Anne
> >>>>
> >>>> -----Message d'origine-----
> >>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> >>>> Envoyé : samedi 10 mai 2008 11:43
> >>>> À : users@felix.apache.org
> >>>> Objet : Re: obr for felix bundles?
> >>>>
> >>>> Hi Richard,
> >>>>
> >>>> I think it would be great if you can arrange this. I think that
> >>>>
> >>>>
> >>> people
> >>>
> >>>
> >>>> that are new to OSGi can have a hard time to get started with felix
> >>>>
> >>>>
> >>> (i
> >>>
> >>>
> >>>> noticed this a few times) and i think that being able to install
> >>>>
> >>>>
> >>> felix
> >>>
> >>>
> >>>> bundles in a simple and convenient way might help.
> >>>>
> >>>> Regards,
> >>>> Peer
> >>>>
> >>>>
> >>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> >>>>
> >>>>
> >>>>> There currently is not. We definitely need this. It basically
> >>>>>
> >>>>>
> >>>> involves
> >>>>
> >>>>
> >>>>> determining at least two things:
> >>>>>
> >>>>> 1. How should we go about generating the repo?
> >>>>> * We have the capability to generate OBR repository files,
> >>>>>
> >>>>>
> >>>> but
> >>>>
> >>>>
> >>>>> how do we get one generated for our current set of
> >>>>>
> >>>>>
> >>> released
> >>>
> >>>
> >>>>> bundle versions?
> >>>>> 2. Where do we put the repository?
> >>>>>
> >>>>> I don't really know the best way to do (1). As for (2), I am not
> >>>>> sure if it matters, I don't think it needs to be hosted on our
> >>>>> Apache
> >>>>>
> >>>>>
> >>>> site.
> >>>>
> >>>>
> >>>>> I could put the repo on my own personal web site or we could just
> >>>>> put them on the Source Forge web site.
> >>>>>
> >>>>> -> richard
> >>>>>
> >>>>> p.s. Sorry to cross post, it is not necessary to cross post
> >>>>> replies...I just want to make sure that this discussion is seen on
> >>>>>
> >>>>>
> >>>> the
> >>>>
> >>>>
> >>>>> dev list.
> >>>>>
> >>>>> peter.doornbosch wrote:
> >>>>>
> >>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I wonder if there is an obr repository for the (current versions
> >>>>>>
> >>>>>>
> >>> of
> >>>
> >>>
> >>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
> >>>>>> with the url http://oscar-
> >>>>>>
> >>>>>>
> >>> osgi.sourceforge.net/obr2/repository.xml,
> >>>
> >>>
> >>>>>> which contains only a few really old bundles....
> >>>>>>
> >>>>>> Regards,
> >>>>>> Peter
> >>>>>>
> >>>>>>
> >>>>>> ------------------------------------------------------------------
> >>>>>>
> >>>>>>
> >>> -
> >>>
> >>>
> >>>>>> -
> >>>>>>
> >>>>>>
> >>>> -
> >>>>
> >>>>
> >>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>> -------------------------------------------------------------------
> >>>>>
> >>>>>
> >>> -
> >>>
> >>>
> >>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>>> --------------------------------------------------------------------
> >>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>
> >>>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
If I understand correctly, Clement is proposing something like this:
releases/
bundleA-v1/
bundleA-v2/
bundleB-v1/
bundleC-v1/
bundleC-v2/
pom.xml
The above represents the structure of our releases directory. The
pom.xml will refer to the most recent version of each release bundle, e.g.:
pom.xml
artifactId=bundleA,version=2
artifactId=bundleB,version=1
artifactId=bundleC,version=2
The purpose of this pom file is largely to document which subprojects
should be made available in our repo. However, if you use it to issue
the mvn deploy command on this pom, then it will deploy the set of all
current releases to the repo.
This is obviously inefficient if only one bundle has been updated since
it will deploy all bundles. To avoid this, though, you can simply 'cd'
into the precise subproject release directory and issue that mvn deploy
command from there, then only the newly released bundle will be deployed.
Clearly, this process is simplistic, but it is probably better than
nothing, which is the current approach. The idea here is that we could
just incorporate it as part of our normal release process, where after
we tag a released bundle in the releases directory, then we update the
version in the pom.xml and then deploy it to the repo.
What do you think?
-> richard
anne.gerodolle@orange-ftgroup.com wrote:
> If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
>
> Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
>
> This means using the same kind of command line as Clement, but at a subproject level (not at the root):
> mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
>
> I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
>
> Regards,
>
> Anne
>
> -----Message d'origine-----
> De : Richard S. Hall [mailto:heavy@ungoverned.org]
> Envoyé : jeudi 15 mai 2008 15:43
> À : users@felix.apache.org; dev@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
>
> -> richard
>
> Clement Escoffier wrote:
>
>> Hi,
>>
>> I change the XSLT file, now there is colors :-)
>>
>> Clement
>>
>>
>>
>>
>>> -----Message d'origine-----
>>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>
>>> Hi Clement !
>>> I have personally a slight preference for the stylesheet coming from
>>> the OSGi Web site (attached file) .
>>> Apart from the style itself (better for presbyopian eyes), it sorts
>>> the bundles alphabetically. I see you have commented this feature in
>>> yuor xsl file.
>>> Of course that's a matter of personal preference, and that's not the
>>> main point !
>>> Best regards,
>>> Anne
>>> -----Message d'origine-----
>>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
>>> Envoyé : jeudi 15 mai 2008 03:42
>>> À : users@felix.apache.org
>>> Objet : RE: obr for felix bundles?
>>>
>>> Hello,
>>>
>>> I attach the Didier's XSLT stylesheet to the generated XML file.
>>> The result is available here :
>>> http://plop-plop.net/obr/repository.xml
>>>
>>> Clement
>>>
>>>
>>>
>>>> -----Message d'origine-----
>>>> De : anne.gerodolle@orange-ftgroup.com
>>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
>>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>>
>>>> Great idea !
>>>>
>>>> Not only it will ease people getting started with felix, but it can
>>>> help convince people giving a try :
>>>> if your repository.xml refers to an obr2html.xsl file, and you show
>>>> people the repository in a browser, you will have the same "waw"
>>>> effect as with the old Oscar repository. You see a nice list of
>>>> already existing bundles, and if you follow the "doc" link it goes
>>>> to the doc etc..
>>>>
>>>> Regards,
>>>> Anne
>>>>
>>>> -----Message d'origine-----
>>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
>>>> Envoyé : samedi 10 mai 2008 11:43
>>>> À : users@felix.apache.org
>>>> Objet : Re: obr for felix bundles?
>>>>
>>>> Hi Richard,
>>>>
>>>> I think it would be great if you can arrange this. I think that
>>>>
>>>>
>>> people
>>>
>>>
>>>> that are new to OSGi can have a hard time to get started with felix
>>>>
>>>>
>>> (i
>>>
>>>
>>>> noticed this a few times) and i think that being able to install
>>>>
>>>>
>>> felix
>>>
>>>
>>>> bundles in a simple and convenient way might help.
>>>>
>>>> Regards,
>>>> Peer
>>>>
>>>>
>>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
>>>>
>>>>
>>>>> There currently is not. We definitely need this. It basically
>>>>>
>>>>>
>>>> involves
>>>>
>>>>
>>>>> determining at least two things:
>>>>>
>>>>> 1. How should we go about generating the repo?
>>>>> * We have the capability to generate OBR repository files,
>>>>>
>>>>>
>>>> but
>>>>
>>>>
>>>>> how do we get one generated for our current set of
>>>>>
>>>>>
>>> released
>>>
>>>
>>>>> bundle versions?
>>>>> 2. Where do we put the repository?
>>>>>
>>>>> I don't really know the best way to do (1). As for (2), I am not
>>>>> sure if it matters, I don't think it needs to be hosted on our
>>>>> Apache
>>>>>
>>>>>
>>>> site.
>>>>
>>>>
>>>>> I could put the repo on my own personal web site or we could just
>>>>> put them on the Source Forge web site.
>>>>>
>>>>> -> richard
>>>>>
>>>>> p.s. Sorry to cross post, it is not necessary to cross post
>>>>> replies...I just want to make sure that this discussion is seen on
>>>>>
>>>>>
>>>> the
>>>>
>>>>
>>>>> dev list.
>>>>>
>>>>> peter.doornbosch wrote:
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I wonder if there is an obr repository for the (current versions
>>>>>>
>>>>>>
>>> of
>>>
>>>
>>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>>>>>> with the url http://oscar-
>>>>>>
>>>>>>
>>> osgi.sourceforge.net/obr2/repository.xml,
>>>
>>>
>>>>>> which contains only a few really old bundles....
>>>>>>
>>>>>> Regards,
>>>>>> Peter
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------
>>>>>>
>>>>>>
>>> -
>>>
>>>
>>>>>> -
>>>>>>
>>>>>>
>>>> -
>>>>
>>>>
>>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>> -------------------------------------------------------------------
>>>>>
>>>>>
>>> -
>>>
>>>
>>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: obr for felix bundles?
Posted by an...@orange-ftgroup.com.
Agreed.
If I understand well, Clement's proposal supposes that somebody deploys the whole set of felix bundles in a centralized manner.
Another possibility is to incrementally evolve the remote repository.xml file, in a similar manner to the local repository.xml file. Using this method for the official felix site would allow the person responsable for deploying some felix subproject on the maven repository to deploy the same bundles on the obr.
This means using the same kind of command line as Clement, but at a subproject level (not at the root):
mvn deploy -DremoteOBR -DaltDeploymentRepository=plop-plop.felix.releases::default::scp://deploymentmachine/mypath deploys the artifacts on the remote obr AND updates the remote repository.xml file .
I'm not involved in felix development, so I don't know what the policy is concerning deployment on the maven repository. If one considers that felix contains some subprojects (sets of bundles) that evolve rather independently from eachother, this incremental method can be relevant.
Regards,
Anne
-----Message d'origine-----
De : Richard S. Hall [mailto:heavy@ungoverned.org]
Envoyé : jeudi 15 mai 2008 15:43
À : users@felix.apache.org; dev@felix.apache.org
Objet : Re: obr for felix bundles?
I think the stylesheet can be figured out one way or the other...what we really need to do is decide if we like the approach that Clement has proposed and, if so, where should physically generate the repository...
-> richard
Clement Escoffier wrote:
> Hi,
>
> I change the XSLT file, now there is colors :-)
>
> Clement
>
>
>
>> -----Message d'origine-----
>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>> ftgroup.com] Envoyé : jeudi 15 mai 2008 03:37 À :
>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>
>> Hi Clement !
>> I have personally a slight preference for the stylesheet coming from
>> the OSGi Web site (attached file) .
>> Apart from the style itself (better for presbyopian eyes), it sorts
>> the bundles alphabetically. I see you have commented this feature in
>> yuor xsl file.
>> Of course that's a matter of personal preference, and that's not the
>> main point !
>> Best regards,
>> Anne
>> -----Message d'origine-----
>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
>> Envoyé : jeudi 15 mai 2008 03:42
>> À : users@felix.apache.org
>> Objet : RE: obr for felix bundles?
>>
>> Hello,
>>
>> I attach the Didier's XSLT stylesheet to the generated XML file.
>> The result is available here :
>> http://plop-plop.net/obr/repository.xml
>>
>> Clement
>>
>>
>>> -----Message d'origine-----
>>> De : anne.gerodolle@orange-ftgroup.com
>>> [mailto:anne.gerodolle@orange- ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>
>>> Great idea !
>>>
>>> Not only it will ease people getting started with felix, but it can
>>> help convince people giving a try :
>>> if your repository.xml refers to an obr2html.xsl file, and you show
>>> people the repository in a browser, you will have the same "waw"
>>> effect as with the old Oscar repository. You see a nice list of
>>> already existing bundles, and if you follow the "doc" link it goes
>>> to the doc etc..
>>>
>>> Regards,
>>> Anne
>>>
>>> -----Message d'origine-----
>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
>>> Envoyé : samedi 10 mai 2008 11:43
>>> À : users@felix.apache.org
>>> Objet : Re: obr for felix bundles?
>>>
>>> Hi Richard,
>>>
>>> I think it would be great if you can arrange this. I think that
>>>
>> people
>>
>>> that are new to OSGi can have a hard time to get started with felix
>>>
>> (i
>>
>>> noticed this a few times) and i think that being able to install
>>>
>> felix
>>
>>> bundles in a simple and convenient way might help.
>>>
>>> Regards,
>>> Peer
>>>
>>>
>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
>>>
>>>> There currently is not. We definitely need this. It basically
>>>>
>>> involves
>>>
>>>> determining at least two things:
>>>>
>>>> 1. How should we go about generating the repo?
>>>> * We have the capability to generate OBR repository files,
>>>>
>>> but
>>>
>>>> how do we get one generated for our current set of
>>>>
>> released
>>
>>>> bundle versions?
>>>> 2. Where do we put the repository?
>>>>
>>>> I don't really know the best way to do (1). As for (2), I am not
>>>> sure if it matters, I don't think it needs to be hosted on our
>>>> Apache
>>>>
>>> site.
>>>
>>>> I could put the repo on my own personal web site or we could just
>>>> put them on the Source Forge web site.
>>>>
>>>> -> richard
>>>>
>>>> p.s. Sorry to cross post, it is not necessary to cross post
>>>> replies...I just want to make sure that this discussion is seen on
>>>>
>>> the
>>>
>>>> dev list.
>>>>
>>>> peter.doornbosch wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I wonder if there is an obr repository for the (current versions
>>>>>
>> of
>>
>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>>>>> with the url http://oscar-
>>>>>
>> osgi.sourceforge.net/obr2/repository.xml,
>>
>>>>> which contains only a few really old bundles....
>>>>>
>>>>> Regards,
>>>>> Peter
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>>
>> -
>>
>>>>> -
>>>>>
>>> -
>>>
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>> -------------------------------------------------------------------
>>>>
>> -
>>
>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
I think the stylesheet can be figured out one way or the other...what we
really need to do is decide if we like the approach that Clement has
proposed and, if so, where should physically generate the repository...
-> richard
Clement Escoffier wrote:
> Hi,
>
> I change the XSLT file, now there is colors :-)
>
> Clement
>
>
>
>> -----Message d'origine-----
>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>> ftgroup.com]
>> Envoyé : jeudi 15 mai 2008 03:37
>> À : users@felix.apache.org
>> Objet : RE: obr for felix bundles?
>>
>> Hi Clement !
>> I have personally a slight preference for the stylesheet coming from
>> the OSGi Web site (attached file) .
>> Apart from the style itself (better for presbyopian eyes), it sorts the
>> bundles alphabetically. I see you have commented this feature in yuor
>> xsl file.
>> Of course that's a matter of personal preference, and that's not the
>> main point !
>> Best regards,
>> Anne
>> -----Message d'origine-----
>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
>> Envoyé : jeudi 15 mai 2008 03:42
>> À : users@felix.apache.org
>> Objet : RE: obr for felix bundles?
>>
>> Hello,
>>
>> I attach the Didier's XSLT stylesheet to the generated XML file.
>> The result is available here :
>> http://plop-plop.net/obr/repository.xml
>>
>> Clement
>>
>>
>>> -----Message d'origine-----
>>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>>> ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>
>>> Great idea !
>>>
>>> Not only it will ease people getting started with felix, but it can
>>> help convince people giving a try :
>>> if your repository.xml refers to an obr2html.xsl file, and you show
>>> people the repository in a browser, you will have the same "waw"
>>> effect as with the old Oscar repository. You see a nice list of
>>> already existing bundles, and if you follow the "doc" link it goes to
>>> the doc etc..
>>>
>>> Regards,
>>> Anne
>>>
>>> -----Message d'origine-----
>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
>>> Envoyé : samedi 10 mai 2008 11:43
>>> À : users@felix.apache.org
>>> Objet : Re: obr for felix bundles?
>>>
>>> Hi Richard,
>>>
>>> I think it would be great if you can arrange this. I think that
>>>
>> people
>>
>>> that are new to OSGi can have a hard time to get started with felix
>>>
>> (i
>>
>>> noticed this a few times) and i think that being able to install
>>>
>> felix
>>
>>> bundles in a simple and convenient way might help.
>>>
>>> Regards,
>>> Peer
>>>
>>>
>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
>>>
>>>> There currently is not. We definitely need this. It basically
>>>>
>>> involves
>>>
>>>> determining at least two things:
>>>>
>>>> 1. How should we go about generating the repo?
>>>> * We have the capability to generate OBR repository files,
>>>>
>>> but
>>>
>>>> how do we get one generated for our current set of
>>>>
>> released
>>
>>>> bundle versions?
>>>> 2. Where do we put the repository?
>>>>
>>>> I don't really know the best way to do (1). As for (2), I am not
>>>> sure if it matters, I don't think it needs to be hosted on our
>>>> Apache
>>>>
>>> site.
>>>
>>>> I could put the repo on my own personal web site or we could just
>>>> put them on the Source Forge web site.
>>>>
>>>> -> richard
>>>>
>>>> p.s. Sorry to cross post, it is not necessary to cross post
>>>> replies...I just want to make sure that this discussion is seen on
>>>>
>>> the
>>>
>>>> dev list.
>>>>
>>>> peter.doornbosch wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I wonder if there is an obr repository for the (current versions
>>>>>
>> of
>>
>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>>>>> with the url http://oscar-
>>>>>
>> osgi.sourceforge.net/obr2/repository.xml,
>>
>>>>> which contains only a few really old bundles....
>>>>>
>>>>> Regards,
>>>>> Peter
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>>
>> -
>>
>>>>> -
>>>>>
>>> -
>>>
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>> -------------------------------------------------------------------
>>>>
>> -
>>
>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
I think the stylesheet can be figured out one way or the other...what we
really need to do is decide if we like the approach that Clement has
proposed and, if so, where should physically generate the repository...
-> richard
Clement Escoffier wrote:
> Hi,
>
> I change the XSLT file, now there is colors :-)
>
> Clement
>
>
>
>> -----Message d'origine-----
>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>> ftgroup.com]
>> Envoyé : jeudi 15 mai 2008 03:37
>> À : users@felix.apache.org
>> Objet : RE: obr for felix bundles?
>>
>> Hi Clement !
>> I have personally a slight preference for the stylesheet coming from
>> the OSGi Web site (attached file) .
>> Apart from the style itself (better for presbyopian eyes), it sorts the
>> bundles alphabetically. I see you have commented this feature in yuor
>> xsl file.
>> Of course that's a matter of personal preference, and that's not the
>> main point !
>> Best regards,
>> Anne
>> -----Message d'origine-----
>> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
>> Envoyé : jeudi 15 mai 2008 03:42
>> À : users@felix.apache.org
>> Objet : RE: obr for felix bundles?
>>
>> Hello,
>>
>> I attach the Didier's XSLT stylesheet to the generated XML file.
>> The result is available here :
>> http://plop-plop.net/obr/repository.xml
>>
>> Clement
>>
>>
>>> -----Message d'origine-----
>>> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
>>> ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
>>> users@felix.apache.org Objet : RE: obr for felix bundles?
>>>
>>> Great idea !
>>>
>>> Not only it will ease people getting started with felix, but it can
>>> help convince people giving a try :
>>> if your repository.xml refers to an obr2html.xsl file, and you show
>>> people the repository in a browser, you will have the same "waw"
>>> effect as with the old Oscar repository. You see a nice list of
>>> already existing bundles, and if you follow the "doc" link it goes to
>>> the doc etc..
>>>
>>> Regards,
>>> Anne
>>>
>>> -----Message d'origine-----
>>> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
>>> Envoyé : samedi 10 mai 2008 11:43
>>> À : users@felix.apache.org
>>> Objet : Re: obr for felix bundles?
>>>
>>> Hi Richard,
>>>
>>> I think it would be great if you can arrange this. I think that
>>>
>> people
>>
>>> that are new to OSGi can have a hard time to get started with felix
>>>
>> (i
>>
>>> noticed this a few times) and i think that being able to install
>>>
>> felix
>>
>>> bundles in a simple and convenient way might help.
>>>
>>> Regards,
>>> Peer
>>>
>>>
>>> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
>>>
>>>> There currently is not. We definitely need this. It basically
>>>>
>>> involves
>>>
>>>> determining at least two things:
>>>>
>>>> 1. How should we go about generating the repo?
>>>> * We have the capability to generate OBR repository files,
>>>>
>>> but
>>>
>>>> how do we get one generated for our current set of
>>>>
>> released
>>
>>>> bundle versions?
>>>> 2. Where do we put the repository?
>>>>
>>>> I don't really know the best way to do (1). As for (2), I am not
>>>> sure if it matters, I don't think it needs to be hosted on our
>>>> Apache
>>>>
>>> site.
>>>
>>>> I could put the repo on my own personal web site or we could just
>>>> put them on the Source Forge web site.
>>>>
>>>> -> richard
>>>>
>>>> p.s. Sorry to cross post, it is not necessary to cross post
>>>> replies...I just want to make sure that this discussion is seen on
>>>>
>>> the
>>>
>>>> dev list.
>>>>
>>>> peter.doornbosch wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I wonder if there is an obr repository for the (current versions
>>>>>
>> of
>>
>>>>> the) felix bundles. When i start felix (1.0.4), obr is configured
>>>>> with the url http://oscar-
>>>>>
>> osgi.sourceforge.net/obr2/repository.xml,
>>
>>>>> which contains only a few really old bundles....
>>>>>
>>>>> Regards,
>>>>> Peter
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>>
>> -
>>
>>>>> -
>>>>>
>>> -
>>>
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>>
>>>>>
>>>> -------------------------------------------------------------------
>>>>
>> -
>>
>>>> - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
Hi,
I change the XSLT file, now there is colors :-)
Clement
> -----Message d'origine-----
> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> ftgroup.com]
> Envoyé : jeudi 15 mai 2008 03:37
> À : users@felix.apache.org
> Objet : RE: obr for felix bundles?
>
> Hi Clement !
> I have personally a slight preference for the stylesheet coming from
> the OSGi Web site (attached file) .
> Apart from the style itself (better for presbyopian eyes), it sorts the
> bundles alphabetically. I see you have commented this feature in yuor
> xsl file.
> Of course that's a matter of personal preference, and that's not the
> main point !
> Best regards,
> Anne
> -----Message d'origine-----
> De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
> Envoyé : jeudi 15 mai 2008 03:42
> À : users@felix.apache.org
> Objet : RE: obr for felix bundles?
>
> Hello,
>
> I attach the Didier's XSLT stylesheet to the generated XML file.
> The result is available here :
> http://plop-plop.net/obr/repository.xml
>
> Clement
>
> > -----Message d'origine-----
> > De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> > ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
> > users@felix.apache.org Objet : RE: obr for felix bundles?
> >
> > Great idea !
> >
> > Not only it will ease people getting started with felix, but it can
> > help convince people giving a try :
> > if your repository.xml refers to an obr2html.xsl file, and you show
> > people the repository in a browser, you will have the same "waw"
> > effect as with the old Oscar repository. You see a nice list of
> > already existing bundles, and if you follow the "doc" link it goes to
> > the doc etc..
> >
> > Regards,
> > Anne
> >
> > -----Message d'origine-----
> > De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> > Envoyé : samedi 10 mai 2008 11:43
> > À : users@felix.apache.org
> > Objet : Re: obr for felix bundles?
> >
> > Hi Richard,
> >
> > I think it would be great if you can arrange this. I think that
> people
> > that are new to OSGi can have a hard time to get started with felix
> (i
> > noticed this a few times) and i think that being able to install
> felix
> > bundles in a simple and convenient way might help.
> >
> > Regards,
> > Peer
> >
> >
> > On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> > > There currently is not. We definitely need this. It basically
> > involves
> > > determining at least two things:
> > >
> > > 1. How should we go about generating the repo?
> > > * We have the capability to generate OBR repository files,
> > but
> > > how do we get one generated for our current set of
> released
> > > bundle versions?
> > > 2. Where do we put the repository?
> > >
> > > I don't really know the best way to do (1). As for (2), I am not
> > > sure if it matters, I don't think it needs to be hosted on our
> > > Apache
> > site.
> > > I could put the repo on my own personal web site or we could just
> > > put them on the Source Forge web site.
> > >
> > > -> richard
> > >
> > > p.s. Sorry to cross post, it is not necessary to cross post
> > > replies...I just want to make sure that this discussion is seen on
> > the
> > > dev list.
> > >
> > > peter.doornbosch wrote:
> > >> Hi,
> > >>
> > >> I wonder if there is an obr repository for the (current versions
> of
> > >> the) felix bundles. When i start felix (1.0.4), obr is configured
> > >> with the url http://oscar-
> osgi.sourceforge.net/obr2/repository.xml,
> > >> which contains only a few really old bundles....
> > >>
> > >> Regards,
> > >> Peter
> > >>
> > >>
> > >> ------------------------------------------------------------------
> -
> > >> -
> > -
> > >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >> For additional commands, e-mail: users-help@felix.apache.org
> > >>
> > >
> > > -------------------------------------------------------------------
> -
> > > - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > For additional commands, e-mail: users-help@felix.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: obr for felix bundles?
Posted by an...@orange-ftgroup.com.
Hi Clement !
I have personally a slight preference for the stylesheet coming from the OSGi Web site (attached file) .
Apart from the style itself (better for presbyopian eyes), it sorts the bundles alphabetically. I see you have commented this feature in yuor xsl file.
Of course that's a matter of personal preference, and that's not the main point !
Best regards,
Anne
-----Message d'origine-----
De : Clement Escoffier [mailto:clement.escoffier@gmail.com]
Envoyé : jeudi 15 mai 2008 03:42
À : users@felix.apache.org
Objet : RE: obr for felix bundles?
Hello,
I attach the Didier's XSLT stylesheet to the generated XML file.
The result is available here :
http://plop-plop.net/obr/repository.xml
Clement
> -----Message d'origine-----
> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> ftgroup.com] Envoyé : mardi 13 mai 2008 06:25 À :
> users@felix.apache.org Objet : RE: obr for felix bundles?
>
> Great idea !
>
> Not only it will ease people getting started with felix, but it can
> help convince people giving a try :
> if your repository.xml refers to an obr2html.xsl file, and you show
> people the repository in a browser, you will have the same "waw"
> effect as with the old Oscar repository. You see a nice list of
> already existing bundles, and if you follow the "doc" link it goes to
> the doc etc..
>
> Regards,
> Anne
>
> -----Message d'origine-----
> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> Envoyé : samedi 10 mai 2008 11:43
> À : users@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> Hi Richard,
>
> I think it would be great if you can arrange this. I think that people
> that are new to OSGi can have a hard time to get started with felix (i
> noticed this a few times) and i think that being able to install felix
> bundles in a simple and convenient way might help.
>
> Regards,
> Peer
>
>
> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> > There currently is not. We definitely need this. It basically
> involves
> > determining at least two things:
> >
> > 1. How should we go about generating the repo?
> > * We have the capability to generate OBR repository files,
> but
> > how do we get one generated for our current set of released
> > bundle versions?
> > 2. Where do we put the repository?
> >
> > I don't really know the best way to do (1). As for (2), I am not
> > sure if it matters, I don't think it needs to be hosted on our
> > Apache
> site.
> > I could put the repo on my own personal web site or we could just
> > put them on the Source Forge web site.
> >
> > -> richard
> >
> > p.s. Sorry to cross post, it is not necessary to cross post
> > replies...I just want to make sure that this discussion is seen on
> the
> > dev list.
> >
> > peter.doornbosch wrote:
> >> Hi,
> >>
> >> I wonder if there is an obr repository for the (current versions of
> >> the) felix bundles. When i start felix (1.0.4), obr is configured
> >> with the url http://oscar-osgi.sourceforge.net/obr2/repository.xml,
> >> which contains only a few really old bundles....
> >>
> >> Regards,
> >> Peter
> >>
> >>
> >> -------------------------------------------------------------------
> >> -
> -
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: obr for felix bundles?
Posted by Clement Escoffier <cl...@gmail.com>.
Hello,
I attach the Didier's XSLT stylesheet to the generated XML file.
The result is available here :
http://plop-plop.net/obr/repository.xml
Clement
> -----Message d'origine-----
> De : anne.gerodolle@orange-ftgroup.com [mailto:anne.gerodolle@orange-
> ftgroup.com]
> Envoyé : mardi 13 mai 2008 06:25
> À : users@felix.apache.org
> Objet : RE: obr for felix bundles?
>
> Great idea !
>
> Not only it will ease people getting started with felix, but it can
> help convince people giving a try :
> if your repository.xml refers to an obr2html.xsl file, and you show
> people the repository in a browser, you will have the same "waw" effect
> as with the old Oscar repository. You see a nice list of already
> existing bundles, and if you follow the "doc" link it goes to the doc
> etc..
>
> Regards,
> Anne
>
> -----Message d'origine-----
> De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
> Envoyé : samedi 10 mai 2008 11:43
> À : users@felix.apache.org
> Objet : Re: obr for felix bundles?
>
> Hi Richard,
>
> I think it would be great if you can arrange this. I think that people
> that are new to OSGi can have a hard time to get started with felix (i
> noticed this a few times) and i think that being able to install felix
> bundles in a simple and convenient way might help.
>
> Regards,
> Peer
>
>
> On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> > There currently is not. We definitely need this. It basically
> involves
> > determining at least two things:
> >
> > 1. How should we go about generating the repo?
> > * We have the capability to generate OBR repository files,
> but
> > how do we get one generated for our current set of released
> > bundle versions?
> > 2. Where do we put the repository?
> >
> > I don't really know the best way to do (1). As for (2), I am not sure
> > if it matters, I don't think it needs to be hosted on our Apache
> site.
> > I could put the repo on my own personal web site or we could just put
> > them on the Source Forge web site.
> >
> > -> richard
> >
> > p.s. Sorry to cross post, it is not necessary to cross post
> > replies...I just want to make sure that this discussion is seen on
> the
> > dev list.
> >
> > peter.doornbosch wrote:
> >> Hi,
> >>
> >> I wonder if there is an obr repository for the (current versions of
> >> the) felix bundles. When i start felix (1.0.4), obr is configured
> >> with the url http://oscar-osgi.sourceforge.net/obr2/repository.xml,
> >> which contains only a few really old bundles....
> >>
> >> Regards,
> >> Peter
> >>
> >>
> >> --------------------------------------------------------------------
> -
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
RE: obr for felix bundles?
Posted by an...@orange-ftgroup.com.
Great idea !
Not only it will ease people getting started with felix, but it can help convince people giving a try :
if your repository.xml refers to an obr2html.xsl file, and you show people the repository in a browser, you will have the same "waw" effect as with the old Oscar repository. You see a nice list of already existing bundles, and if you follow the "doc" link it goes to the doc etc..
Regards,
Anne
-----Message d'origine-----
De : peter.doornbosch [mailto:peter.doornbosch@gmail.com]
Envoyé : samedi 10 mai 2008 11:43
À : users@felix.apache.org
Objet : Re: obr for felix bundles?
Hi Richard,
I think it would be great if you can arrange this. I think that people that are new to OSGi can have a hard time to get started with felix (i noticed this a few times) and i think that being able to install felix bundles in a simple and convenient way might help.
Regards,
Peer
On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> There currently is not. We definitely need this. It basically involves
> determining at least two things:
>
> 1. How should we go about generating the repo?
> * We have the capability to generate OBR repository files, but
> how do we get one generated for our current set of released
> bundle versions?
> 2. Where do we put the repository?
>
> I don't really know the best way to do (1). As for (2), I am not sure
> if it matters, I don't think it needs to be hosted on our Apache site.
> I could put the repo on my own personal web site or we could just put
> them on the Source Forge web site.
>
> -> richard
>
> p.s. Sorry to cross post, it is not necessary to cross post
> replies...I just want to make sure that this discussion is seen on the
> dev list.
>
> peter.doornbosch wrote:
>> Hi,
>>
>> I wonder if there is an obr repository for the (current versions of
>> the) felix bundles. When i start felix (1.0.4), obr is configured
>> with the url http://oscar-osgi.sourceforge.net/obr2/repository.xml,
>> which contains only a few really old bundles....
>>
>> Regards,
>> Peter
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "peter.doornbosch" <pe...@gmail.com>.
Hi Richard,
I think it would be great if you can arrange this. I think that people
that are new to OSGi can have a hard time to get started with felix (i
noticed this a few times) and i think that being able to install felix
bundles in a simple and convenient way might help.
Regards,
Peer
On 9 May , 2008, at 16:11 , Richard S. Hall wrote:
> There currently is not. We definitely need this. It basically
> involves determining at least two things:
>
> 1. How should we go about generating the repo?
> * We have the capability to generate OBR repository files, but
> how do we get one generated for our current set of released
> bundle versions?
> 2. Where do we put the repository?
>
> I don't really know the best way to do (1). As for (2), I am not
> sure if it matters, I don't think it needs to be hosted on our
> Apache site. I could put the repo on my own personal web site or we
> could just put them on the Source Forge web site.
>
> -> richard
>
> p.s. Sorry to cross post, it is not necessary to cross post
> replies...I just want to make sure that this discussion is seen on
> the dev list.
>
> peter.doornbosch wrote:
>> Hi,
>>
>> I wonder if there is an obr repository for the (current versions of
>> the) felix bundles. When i start felix (1.0.4), obr is configured
>> with the url http://oscar-osgi.sourceforge.net/obr2/repository.xml,
>> which contains only a few really old bundles....
>>
>> Regards,
>> Peter
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
There currently is not. We definitely need this. It basically involves
determining at least two things:
1. How should we go about generating the repo?
* We have the capability to generate OBR repository files, but
how do we get one generated for our current set of released
bundle versions?
2. Where do we put the repository?
I don't really know the best way to do (1). As for (2), I am not sure if
it matters, I don't think it needs to be hosted on our Apache site. I
could put the repo on my own personal web site or we could just put them
on the Source Forge web site.
-> richard
p.s. Sorry to cross post, it is not necessary to cross post replies...I
just want to make sure that this discussion is seen on the dev list.
peter.doornbosch wrote:
> Hi,
>
> I wonder if there is an obr repository for the (current versions of
> the) felix bundles. When i start felix (1.0.4), obr is configured with
> the url http://oscar-osgi.sourceforge.net/obr2/repository.xml, which
> contains only a few really old bundles....
>
> Regards,
> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
Re: obr for felix bundles?
Posted by "Richard S. Hall" <he...@ungoverned.org>.
There currently is not. We definitely need this. It basically involves
determining at least two things:
1. How should we go about generating the repo?
* We have the capability to generate OBR repository files, but
how do we get one generated for our current set of released
bundle versions?
2. Where do we put the repository?
I don't really know the best way to do (1). As for (2), I am not sure if
it matters, I don't think it needs to be hosted on our Apache site. I
could put the repo on my own personal web site or we could just put them
on the Source Forge web site.
-> richard
p.s. Sorry to cross post, it is not necessary to cross post replies...I
just want to make sure that this discussion is seen on the dev list.
peter.doornbosch wrote:
> Hi,
>
> I wonder if there is an obr repository for the (current versions of
> the) felix bundles. When i start felix (1.0.4), obr is configured with
> the url http://oscar-osgi.sourceforge.net/obr2/repository.xml, which
> contains only a few really old bundles....
>
> Regards,
> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org