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"?
Regards,
Thomas Hallgren
On 10/15/2009 10:34 PM, Curtis Windatt wrote:
A short meeting was held to discuss the target definition user interface
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 will
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 like
to express their thoughts, please add some discussion points to the wiki
page or bring it up on this mailing list.
http://wiki.eclipse.org/PDE/Meetings/20091015
Curtis
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
|