[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-dev] Target UI Discussion (Thomas)
|
On 10/16/2009 04:10 PM, Curtis Windatt wrote:
I don't see a bug for having multiple environment settings. Which is a
bit surprising since the request has come up for discussion before. So
feel free to file one. There is a bug to support target validation bug
268237 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=268237) The target
has always been for a single environment, and I'm not sure how having
multiple environments would work for building plug-ins in the workspace.
However, during export there is certainly a need to support multiple
environments.
Most bundles are not sensitive to the platform settings during a build.
The ones that are must of course be built once for each platform but I
think they are very rare (we certainly try to stay away from those). The
typical scenario is that your bundles are completely platform independent.
I think that with an advanced build system it should be possible to do
the following:
1. Build all bundles that are insensitive to the environment settings.
2. For each environment defined in the target platform, build those
bundles that are targeted to that environment.
3. Export everything to your target repository.
This is one of the scenarios that we will cover with the new b3 model.
I'll file a bugzilla.
We haven't detailed the target model changes we would like to see, but we
would like to use a profile to store the list of IUs in a target. We
already are using a profile if you have 'software site locations' in your
target. Even if a profile can only have a single environment, it should
be possible to have multiple environments and re-resolve the target for
each of them during an export operation.
The export operation used by Buckminster is inherently multi-platform
and normally we only resolve once, using a slicer that doesn't
discriminate based on platform filters.
I don't understand the real benefit of having the complete transitive
closure of bundles in the target.
We always need that to enable a multi-platform export of our features.
We want all launcher fragments, all swt fragments, etc. to be included
in the final p2 repository.
Regards,
Thomas Hallgren
