[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [equinox-dev] [prov] Optional Fragments
|
There may be 2 types of optional
- install when available. ( We have found that language fragments are in this category)
- user optional (user's choice)
> One problem, how do we provision a fully functional SWT on someone's
> machine when it just installed "org.eclipse.swt", or installed another IU
> that required org.eclipse.swt?
If an IU requires org.eclipse.swt then it should only be installed if the requirements are met. Of course we can install as long as we don't attempt to configure until all requirements are met.
Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
09/04/2007 08:04 PM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx> |
|
|
Having a dependency on the necessary fragment is not always possible for
two reasons:
- fragment may become available at a later date (for example language
packs, or new SWT ports once you shipped)
- you don't provision from a "group" that refers to everything (for example
some people just want to install one installable unit)
One problem, how do we provision a fully functional SWT on someone's
machine when it just installed "org.eclipse.swt", or installed another IU
that required org.eclipse.swt?
From: James D Miles <jdmiles@xxxxxxxxxx>
To: equinox-dev@xxxxxxxxxxx
Date: 09/04/2007 05:17 PM
Subject: [equinox-dev] [prov] Optional Fragments
For the discussion tomorrow I miss the point. Isn't a fragment only
optional if an installable unit does not require it? Do we need more than
the IsOptional() in RequiredCapability class?
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev