Community
Participate
Working Groups
Build Identifier: I20100406-1034 All scenarios that try to create an instance of class org.eclipse.equinox.internal.p2.metadata.ProvidedCapabilty (e.g. for defining a capability which an installable unit declares to provide in the metadata repository) by passing a null value for the namespace and/or name parameters ends up with an AssertionFailedException with a meaningless message that gives no hint which argument is null and which is the concerned capability. Reproducible: Always Steps to Reproduce: 1. In Eclipse IDE 3.6, run P2 product publisher application with configured standard parameters but omitting the “flavor” parameter, e.g.: -metadataRepository file:///D:/tools (url to an existing repository) -artifactRepository file:///D:/tools (url to an existing repository) -productFile d:/file.product (file path to a standard product file) -append 2. Observe the output which contains the AssertionFailedException with an unclear message: Status ERROR: org.eclipse.equinox.p2.artifact.repository code=0 null argument: org.eclipse.core.runtime.AssertionFailedException: null argument:
Created attachment 176039 [details] It is clearly shown which of the arguments is null and which is the provided capability by its namespace, if not null. Old message: org.eclipse.core.runtime.AssertionFailedException: null argument: the namespace of the provided capabilty is not defined New message: org.eclipse.core.runtime.AssertionFailedException: null argument:the name of provided capability org.eclipse.equinox.p2.flavor is not defined
thx for the patch.
