| Help with debugging update mechanism [message #1830017] |
Wed, 15 July 2020 16:59  |
Eclipse User |
|
|
|
Hello,
I'm trying to figure out, why my feature-based product is not updating to the newer version. The product is installed with setup file which only contains the product itself. The problem is that in the end of the Oomph's "perform setup tasks" operation, it just says that no updates are available.
After some debugging, I discovered that the product sees the new version in the specified p2 update site, but during operation of p2 mechanisms, the choice is made in favor of the old version. I also found out that dependency conflicts are resolved using SAT4j library, which I also tried to debug in order to understand what the problem is. So far, I have discovered that both versions of the product are passed to DependencyHelper (entity of SAT4j library) and that the choice is made in favor of the old one (the coefficient list is returned, where the coefficient of the new version of the product is marked with a minus sign).
Since debugging of the library internal work is quite painstaking work, the question is - is there any mechanisms which can ease troubleshooting (e.g. enabling debug logging which can show dependency conflicts or some place in the code where you can find information about conflicts, etc)?
|
|
|
|
Powered by
FUDForum. Page generated in 0.03667 seconds
Home