Eclipse Community Forums: Oomph » Finding out why oomph takes an action

Home » Eclipse Projects » Oomph » Finding out why oomph takes an action

Finding out why oomph takes an action [message #1820558]

Wed, 22 January 2020 15:20

Eclipse User

I have an eclipse products setup file based on Eclipse.org's file with a number of additions. When I install eclipse using the setup everything works fine. If I start the newly installed eclipse the last few preferences are applied and eclipse is fine. When I click on Help/Perform setup task, two additional requirements (org.objectweb.asm.*) get's added (see line 2967-2968 in the attached logfile) with a version older than the just freshly installed (line 2615 and 2618).

This did not happen with eclipse 2019-09 and I have not changed anything in creating the 2019-12 setup to cause that. How can I find out WHY oomph decided to install these older version? I know that this is probably a task with a MANUAL only trigger but how can I get oomph to tell me which one in which setup file did that? The problem is further compounded because those plugins do not come from a feature called org.objectweb but rather from org.eclipse.orbit. I would like to know if this is MY problem or if this is a problem in Eclipse.org 2019-12 setup.

Re: Finding out why oomph takes an action [message #1820569 is a reply to message #1820558]

Wed, 22 January 2020 23:38

Eclipse User

I see nothing attached here. The setup file would probably also help to understand what's going on.

Re: Finding out why oomph takes an action [message #1820601 is a reply to message #1820569]

Thu, 23 January 2020 12:04

Eclipse User

My bad, here is the setup log file and the setup file. I had to mangle some data to protect the innocent.

Attachment: setup.log
(Size: 275.51KB, Downloaded 100 times)
Attachment: org.company.products.setup
(Size: 68.96KB, Downloaded 114 times)

[Updated on: Thu, 23 January 2020 12:14] by Moderator

Re: Finding out why oomph takes an action [message #1820634 is a reply to message #1820601]

Fri, 24 January 2020 00:40

Eclipse User

The only difference I can see between your bootstrap and your manual perform is the fact that at boostrap time you checked "offline = true", while the manual perform in your IDE uses "offline = false". In theory that can cause different installations. With offline=true it all depends on what is in actually in your offline cache. Do you still see these two org.objectweb.asm installs if you don't check offline=true at bootstrap time?

Re: Finding out why oomph takes an action [message #1820648 is a reply to message #1820634]

Fri, 24 January 2020 06:23

Eclipse User

I will try that. Is there a way though to find out from oomph why it selected org.objectweb 5.0.1 during the manual run? Is there some trace or debug level?

Re: Finding out why oomph takes an action [message #1820655 is a reply to message #1820648]

Sat, 25 January 2020 00:21

Eclipse User

Unfortunately no. Not Oomph but p2 decides what IUs are needed to make your root requirements happy. Your only chance is to look at the root requirements that Oomph collects from your tasks. You can do that already on the Confirmation page.

Previous Topic:	Oomph version management tool questions
Next Topic:	Oomph generated target vs tycho

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 21 11:00:11 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter