On 05/24/2012 12:58 PM, Dennis Hübner wrote:
So it's a "Use the new publisher" thing… Is it obligatory for all eclipse
projects? Or is it just a good practice.
Adopters can still decide if an optional dependency should be installed or not, by filtering it from the build target
platform and Eclipse user can filter/deactivate the corresponding repository and so use a subset of project p2
repositories.
However, I don't want to convince you, that optional greedy make sense or not (by the way it was a default for years),
I'd like that people accept, that this is a valid combination and don't nag on projects, who use it. :p
One could very well argue that an optional non-greedy dependency is completely useless and doesn't fulfill any other
purpose but documentation. The dependency will not be installed, it is not required, and if it's already there and
conflicting, the conflict will be suppressed by the optional status. So why is the dependency there in the first place?
- thomas
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
