Difference between revisions of "Virgo/Design/ResolutionFailureDetective"

From Eclipsepedia

< Virgo‎ | Design
Jump to: navigation, search
(New page: The <tt>ResolutionFailureDetective</tt> interface is used by the deployment pipeline to provide improved diagnostics beyond those generated by Equinox. The single implementation of this in...)
 
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
The <tt>ResolutionFailureDetective</tt> interface is used by the deployment pipeline to provide improved diagnostics beyond those generated by Equinox. The single implementation of this interface, <tt>StandardQuasiFrameworkDetective>/tt>, uses various classes from the <tt>org.eclipse.osgi.service.resolver</tt> package to analyse resolver errors.
+
{{Virgo}} [[Category:Virgo]] [[Category:EclipseRT]]
 +
 
 +
The <tt>ResolutionFailureDetective</tt> interface is used by the deployment pipeline to provide improved diagnostics beyond those generated by Equinox. The single implementation of this interface, <tt>StandardQuasiFrameworkDetective</tt>, uses various classes from the <tt>org.eclipse.osgi.service.resolver</tt> package to analyse resolver errors.
 +
 
 +
In addition to mapping Equinox resolver errors to explanatory messages, the resolution failure detective analyses uses constraint failures and attempts to produce compact diagnostics which identify the root cause of the failure.

Latest revision as of 05:55, 15 April 2013

The ResolutionFailureDetective interface is used by the deployment pipeline to provide improved diagnostics beyond those generated by Equinox. The single implementation of this interface, StandardQuasiFrameworkDetective, uses various classes from the org.eclipse.osgi.service.resolver package to analyse resolver errors.

In addition to mapping Equinox resolver errors to explanatory messages, the resolution failure detective analyses uses constraint failures and attempts to produce compact diagnostics which identify the root cause of the failure.