[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] installing bundle fragments

> > This is the expected behaviour in 3.4 and 3.5.
>
> Does this mean you expect this to change in 3.6?

Not right now, but I don't want to make a statement for future releases :)

> > The problem with having the IU for the host bundle expressing a
> > requirement on an IU providing a " "fragment of host" capability" is
> > that at install time this can result in additional things to be
> > installed and that are not necessarily desired since you would pull in
> > thing blindly.
> > That said, in the particular case of SWT, given that the host is useless
> > since it is empty (no API there and all the code being in the fragment)
> > having the IU for the host express a requirement on a
> > "org.eclipse.swt.fragment" capability and have every fragment provide it
> > could do the work. Feel free to open a bug against SWT to that extent.
>
> SWT bundle/fragments apart, what is the recommended way of installing
> desired fragments with P2? Bundle fragments are a common place but the
> only way to install them appears to be explicitly listing them in group
> IUs. How do you include ECF SSL fragments in P2 application, for
> example? Or maybe you can suggest another example I can look at.

The grouping is the only way to go.
We have explored with automatic mechanisms way back in the p2 prototypes and it always ended up being problematic in an open environment (absence of control of repo) and we decided that if a fragment is a must have for a host then the metadata should capture this, otherwise dealing with integration a fragment is of the resort of the product producer.
In the example of ECF SSL, I want to be able to build configuration without SSL support so bringing the bundle automatically would be problematic for some users.
Another case I ran into with
Another problematic case I have encountered is with the SDK where whenever I was installing Ant I was getting CDT because CDT provided an Ant fragment which itself had dependencies on the rest of CDT.

PaScaL

>
> --
> Regards,
> Igor
>
>
> >
> > HTH
> >
> > PaScaL
> >
> >
> > Inactive hide details for Igor Fedorenko ---04/07/2009 03:43:16
> > PM---Hello, I was under impression that P2 is expected to find Igor
> > Fedorenko ---04/07/2009 03:43:16 PM---Hello, I was under impression that
> > P2 is expected to find and install any
> >
> >
> > From:  
> > Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>
> >
> > To:  
> > P2 developer discussions <p2-dev@xxxxxxxxxxx>
> >
> > Date:  
> > 04/07/2009 03:43 PM
> >
> > Subject:  
> > [p2-dev] installing bundle fragments
> >
> > ------------------------------------------------------------------------
> >
> >
> >
> > Hello,
> >
> > I was under impression that P2 is expected to find and install any
> > bundle fragments applicable to the target runtime environment. So if,
> > for example, I tell it to install org.eclipse.swt on linux/gtk/x86_64 it
> > should install applicable swt fragment too. This does not seem to be the
> > case, at least not with director app from 3.5M6. I see that P2 is able
> > to filter out inapplicable fragments that are referenced through
> > features, but does not actively try to "find" additional fragments. Is
> > this expected behaviour?
> >
> > --
> > Regards,
> > Igor
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev