You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by mi...@telvent.com on 2009/07/16 11:23:53 UTC

Bundle repository conflict with artifacts when deploying


Hi guys,

we are experiencing the following situation when using the bundle
repository 1.4.0 over felix framework 1.8.0.

The scenario is the following:

1) In the remote repository has been published one bundle (
org.eclipse.osgi/3.4.0.v20080605-1900  -- Equinox) that provide the
capability (org.osgi.framework; version 1.4.0)
2) When you try to install a bundle X from the bundles repository that has
got a <require> clause to org.osgi.framework; version 1.4.0. The dependency
tree is being resolve including a dependency to the Equinox bundle that
provides the required capability
3) During the deployment phase, the Equinox bundle is being installed in
the Felix framework and a conflict appears due to the that the System
Bundle (Felix framework) exports the same package with the same version

In my opinion, I think that a wrong behaviuor is appearing due to the fact
that the bundle repository is not checking if the org.osgi.framework;
version 1.4.0 is exposed and is taking the information from the
repository.xml file in order to solve the bundles dependency tree.

Have you checked this behaviour with the bundle repository? Is this
experienced behaviour correct according to the dependencies resolution
algorithm implemented by the bundle repository?

Regards,
Miguel A.

***********Internet Email Confidentiality Footer*************
This email and any files transmitted with it are confidential and intended
solely for the use of the organization or individual to whom they are
addressed.  It is expressly forbidden to retransmit or copy email and/or
this  attached files without our permission .  If you are not the
addressee indicated in this message (or responsible for delivery of the
message to such person), you may not copy or deliver this message
to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or
your employer does not consent to Internet email for messages of this
kind.  Opinions, conclusions and other information in this message that
do not relate to the official business of my firm shall be understood as
neither given nor endorsed by it.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: Bundle repository conflict with artifacts when deploying

Posted by mi...@telvent.com.

"Richard S. Hall" <he...@ungoverned.org> escribió el 16/07/2009 15:07:53:

> I believe OBR should favor already deployed providers over ones that
> have not been deployed. Since framework 1.4.0 should already be
> available from Felix' system bundle, it doesn't seem like this should
> happen. Are you sure this is the dependency causing Equinox to be pulled
in?

It seems to be what is happening.

>
> You could probably test this by creating an empty bundle with only a
> dependency on framework 1.4.0. If it is an issue, create a JIRA issue
> attach the example and we will look into it.

I will provide the test case on the JIRA issue with the example (bundles
and repository.xml file)
>
> -> richard
>
> On 7/16/09 5:23 AM, miguel.oltra@telvent.com wrote:
> > Hi guys,
> >
> > we are experiencing the following situation when using the bundle
> > repository 1.4.0 over felix framework 1.8.0.
> >
> > The scenario is the following:
> >
> > 1) In the remote repository has been published one bundle (
> > org.eclipse.osgi/3.4.0.v20080605-1900  -- Equinox) that provide the
> > capability (org.osgi.framework; version 1.4.0)
> > 2) When you try to install a bundle X from the bundles repository that
has
> > got a<require>  clause to org.osgi.framework; version 1.4.0. The
dependency
> > tree is being resolve including a dependency to the Equinox bundle that
> > provides the required capability
> > 3) During the deployment phase, the Equinox bundle is being installed
in
> > the Felix framework and a conflict appears due to the that the System
> > Bundle (Felix framework) exports the same package with the same version
> >
> > In my opinion, I think that a wrong behaviuor is appearing due to the
fact
> > that the bundle repository is not checking if the org.osgi.framework;
> > version 1.4.0 is exposed and is taking the information from the
> > repository.xml file in order to solve the bundles dependency tree.
> >
> > Have you checked this behaviour with the bundle repository? Is this
> > experienced behaviour correct according to the dependencies resolution
> > algorithm implemented by the bundle repository?
> >
> > Regards,
> > Miguel A.
> >
> > ***********Internet Email Confidentiality Footer*************
> > This email and any files transmitted with it are confidential and
intended
> > solely for the use of the organization or individual to whom they are
> > addressed.  It is expressly forbidden to retransmit or copy email
and/or
> > this  attached files without our permission .  If you are not the
> > addressee indicated in this message (or responsible for delivery of the
> > message to such person), you may not copy or deliver this message
> > to anyone. In such case, you should destroy this message and kindly
> > notify the sender by reply email. Please advise immediately if you or
> > your employer does not consent to Internet email for messages of this
> > kind.  Opinions, conclusions and other information in this message that
> > do not relate to the official business of my firm shall be understood
as
> > neither given nor endorsed by it.
> >
> >
> > ---------------------------------------------------------------------
> > 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: Bundle repository conflict with artifacts when deploying

Posted by "Richard S. Hall" <he...@ungoverned.org>.
I believe OBR should favor already deployed providers over ones that 
have not been deployed. Since framework 1.4.0 should already be 
available from Felix' system bundle, it doesn't seem like this should 
happen. Are you sure this is the dependency causing Equinox to be pulled in?

You could probably test this by creating an empty bundle with only a 
dependency on framework 1.4.0. If it is an issue, create a JIRA issue 
attach the example and we will look into it.

-> richard

On 7/16/09 5:23 AM, miguel.oltra@telvent.com wrote:
> Hi guys,
>
> we are experiencing the following situation when using the bundle
> repository 1.4.0 over felix framework 1.8.0.
>
> The scenario is the following:
>
> 1) In the remote repository has been published one bundle (
> org.eclipse.osgi/3.4.0.v20080605-1900  -- Equinox) that provide the
> capability (org.osgi.framework; version 1.4.0)
> 2) When you try to install a bundle X from the bundles repository that has
> got a<require>  clause to org.osgi.framework; version 1.4.0. The dependency
> tree is being resolve including a dependency to the Equinox bundle that
> provides the required capability
> 3) During the deployment phase, the Equinox bundle is being installed in
> the Felix framework and a conflict appears due to the that the System
> Bundle (Felix framework) exports the same package with the same version
>
> In my opinion, I think that a wrong behaviuor is appearing due to the fact
> that the bundle repository is not checking if the org.osgi.framework;
> version 1.4.0 is exposed and is taking the information from the
> repository.xml file in order to solve the bundles dependency tree.
>
> Have you checked this behaviour with the bundle repository? Is this
> experienced behaviour correct according to the dependencies resolution
> algorithm implemented by the bundle repository?
>
> Regards,
> Miguel A.
>
> ***********Internet Email Confidentiality Footer*************
> This email and any files transmitted with it are confidential and intended
> solely for the use of the organization or individual to whom they are
> addressed.  It is expressly forbidden to retransmit or copy email and/or
> this  attached files without our permission .  If you are not the
> addressee indicated in this message (or responsible for delivery of the
> message to such person), you may not copy or deliver this message
> to anyone. In such case, you should destroy this message and kindly
> notify the sender by reply email. Please advise immediately if you or
> your employer does not consent to Internet email for messages of this
> kind.  Opinions, conclusions and other information in this message that
> do not relate to the official business of my firm shall be understood as
> neither given nor endorsed by it.
>
>
> ---------------------------------------------------------------------
> 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