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.
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
I don't understand the real benefit
of having the complete transitive closure of bundles in the target.
Thomas Hallgren <thomas@xxxxxxx>
2009/10/15 04:50 PM
Re: [pde-dev] Target UI Discussion
Todays targets are associated with one environment. That
is not ideal when your builds produce p2 repositories with support for
many platforms. Would it be possible to say that a target supports a list
of environments? The list would serve two purposes:
1. When using software sites, the p2 planner could be called repeatedly,
once for each environment, in order to build the complete transitive closure
needed to support all of them for the selected root IU's. That closure
would then be maintained by the target. If I add an new environment, I
should be able to update to get the missing parts.
2. A new "Validate Target Platform" button could be added. It
would find conflicts and inconsistencies in the target platform with the
respect to the supported environments.
Unfortunately, I think multi-platform targets contradicts with the wish
to manage the target in a p2 profile. But perhaps that is not what is intended
when you write "Profile backs the target"?
On 10/15/2009 10:34 PM, Curtis Windatt wrote:
A short meeting was held to discuss the target definition
and what changes we might want to see in 3.6. We are happy with the
overall flow of the current UI and don't want to disrupt current
workflows. However, there are changes to the underlying models that
affect the UI, we want to see target definitions better integrated with
p2, and there are a number of bugs we want to see fixed. The discussion
is summarized on the PDE wiki. If anyone else in the community would
to express their thoughts, please add some discussion points to the wiki
page or bring it up on this mailing list.