[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] [prov] Optional Fragments
|
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
