Re: [p2-dev] p2 fails to update without any error

[Vincenzo Caselli <vincenzo.caselli@xxxxxxxxx>]

Hi all,

we've found the issue: we noticed that, among all the plug-ins in our feature project, some were updating while others not.

The ones that were not updating did have a version not respecting the pattern "x.y.z.qualifier", but just "x.y.z" (say: 1.0.0 instead of 1.0.0.qualifier). Simply adjusting to pattern "x.y.z.qualifier" did solve the problem!

Anyway we found regularly messages like the following into the workspace/.metadata/.log file:

!ENTRY org.eclipse.equinox.p2.touchpoint.natives 2 0 2009-08-13 11:00:44.093

!MESSAGE Could not remove temporary backup directory (it is safe to manually delete it and its contents): C:\DOCUME~1\mobile\IMPOST~1\Temp\profile_24625f9ae080_c0a800650cf6

what this stands for?

Thank you in advance.

Vincenzo Caselli

On Thu, Aug 13, 2009 at 8:29 PM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:

I suggest enter a bug report. If there is a small sample application that reproduces the problem it would be a huge help. If you look at the bundle org.eclipse.equinox.p2.core in the file ".options" there are a number of trace options that will cause more details to be printed.

http://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F

#Turn on debugging for p2
org.eclipse.equinox.p2.core/debug=false

#Detailed debugging information while parsing p2 data files
org.eclipse.equinox.p2.core/core/parseproblems=false

#Detailed debugging information when a repository is removed from a repository manager
org.eclipse.equinox.p2.core/core/removeRepo=false

#Detailed debugging information while parsing site.xml and feature.xml files in the generator
org.eclipse.equinox.p2.core/generator/parsing=false

#Detailed debugging information while saving/restoring the engine's install registry
org.eclipse.equinox.p2.core/engine/installregistry=false

#Detailed debugging information while saving/restoring profile preferences
org.eclipse.equinox.p2.core/engine/profilepreferences=false

#Detailed debugging information while saving/restoring metadata repositories
org.eclipse.equinox.p2.core/metadata/parsing=false

#Detailed debugging information about mirror selection
org.eclipse.equinox.p2.core/artifacts/mirrors=false

#Detailed debugging information about automatic update checking
org.eclipse.equinox.p2.core/updatechecker=false

#Detailed debugging information about the operands being generated
org.eclipse.equinox.p2.core/planner/operands=false

#Detailed debugging information about the projector
org.eclipse.equinox.p2.core/planner/projector=false

#Detailed debugging information about the reconciler
org.eclipse.equinox.p2.core/reconciler=false

#Detailed debugging information about the publisher
org.eclipse.equinox.p2.core/publisher=false

Vincenzo Caselli <vincenzo.caselli@xxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx

08/13/2009 09:53 AM

Please respond to
vincenzo.caselli@xxxxxxxxx; Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

To	p2-dev@xxxxxxxxxxx
cc
Subject	[p2-dev] p2 fails to update without any error

Hi all,
we have used successfully p2 to update more some RCP products.
In one case this fails regularly (and without any error).
The steps, in all cases, are:
- create the plugins
- create a feature project to gather the plugins
- create the p2.inf file in the application plugin with the update location
- create a feature-based Product configuration
- export the product
- copy the product folder to the installation location
then we introduce modifications in the plugins and re-export the product after having increased the version of both the feature project and the product.
At this point the installed product is able to perform the update successfully.

In one case however it happens this:
- the installed product recognize that there is an update
- it performs the update (usual update wizard, download, asking for restart) and restarts itself
- after the restart however the updates do not appear
- at this point checking for updates says that there are no update

The whole process happens without an error, even the .log file into the folder
eclipse\workspace\.metadata
does not show any problem.

What we can do? Are there ways to increase the logging details in order to understand what is going wrong during the update?

Thank you very much

Vincenzo Caselli_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

-- 
Vincenzo Caselli
RCP Vision
http://www.rcp-vision.com
E-mail: v.caselli@xxxxxxxxxxxxxx
Mobile: +39 347 1267872
Skype: vincenzocaselli
Gtalk: vincenzo.caselli