Yes Thomas is correct. The p2.inf is *not* read at runtime.
The start level you specify in this file are turned into actions that are part of the p2 metadata, the touchpoint action in the IU for the feature to be precise.
On 2012-06-06, at 11:08 AM, Craig Ching wrote:
Are you sure about that? We include p2.inf in our features all the time. It's the only way that I know of to control start levels for particular bundles.
On Wed, Jun 6, 2012 at 9:54 AM, Thomas Hallgren <thomas@xxxxxxx> wrote:
The p2.inf file is a build artifact recognized by the p2 publisher.
It's not supposed to be included in the p2 repository and to my
knowledge it has no meaning in a runtime configuration. In other
words, in order for p2 to recognize it, the artifact must be rebuilt
and published anew and the user must then update his installation.
On 06/06/2012 04:42 PM, Samuel Wu wrote:
A customer shipped a p2.inf in
a feature. This p2.inf contains a touch-point action for the
unconfigure and it has a syntax error. This feature has been
installed and deployed to the end user. Now this feature needs
to be updated. An error message popped up to complain the
syntax error in the touch point action and didn't allow the
feature to be updated. They tried to correct the syntax error
in the p2.inf of the installed the feature and start with
-clean option, but eclipse still remembered and used the old
command with error.
Is there a way to make P2
recognize the updated p2.inf? Thanks.