> > I have a very general OSGi related question. What happens if someone
> > writes an OSGi bundle under [a licence] and registers a service from
> > that bundle in the framework?
> These are just my opinions, all disclaimers apply.
As implied by "all disclaimers apply", unfortunately, the correc
My interpretation of this would be that Felix is not linking with it, because
Felix knows nothing about it. Felix only knows about OSGi api, which is
licensed under ASL.
As far as other bundles looking up the service, from my point of view that will
depend on the license of the service interfac
David Lindelöf wrote:
Dear all,
I have a very general OSGi related question. What happens if someone
writes an OSGi bundle under the GPL licence and registers a service from
that bundle in the framework?
My understanding is that the framework cannot really be said to "link"
to the bundle and ca
Stuart McCulloch wrote:
> Hi Costin,
>
> Is it possible to get access to your modified branch of the build?
> would make it easier to find and test possible solutions, instead
> of trying to suggest things based on a couple of poms.
I hope to commit today my changes to Spring/OSGi trunk. I'll let
Hi Costin,
Is it possible to get access to your modified branch of the build?
would make it easier to find and test possible solutions, instead
of trying to suggest things based on a couple of poms.
I usually end up exploding wrapped libraries under target/classes
as it makes Eclipse happy - tha
Alin Dreghiciu wrote:
> A solution will be indeed to separate the build of spring-modules,
> including
> required libraries from building of the rest. As with spring 2.1 anyway the
> artifacts will be osgi bundles anyway.
Until they will, we have to deal with this.
>
> P.S. if you are doing this
A solution will be indeed to separate the build of spring-modules, including
required libraries from building of the rest. As with spring 2.1 anyway the
artifacts will be osgi bundles anyway.
P.S. if you are doing this refactoring isn't now also the moment to get rid
of some of the required libra
Alin Dreghiciu wrote:
> Hi Costin,
>
> Here are my empirical observations about maven behavior.
>
> First of all the problem you have is not related to the the new plugin. It
> was the same also with the old plugin but the difference then was that
> before packaging as a bundle the content of spr
Hi Costin,
Here are my empirical observations about maven behavior.
First of all the problem you have is not related to the the new plugin. It
was the same also with the old plugin but the difference then was that
before packaging as a bundle the content of spring-core was extracted first
in the
