Eclipse Community Forums: Oomph » Oomph Customization

Home » Eclipse Projects » Oomph » Oomph Customization

Fri, 09 October 2020 06:09

Eclipse User

Hi,
I have made some changes in the Oomph source code to customize git checkout for workspace setup of installed eclipse product.
I have built an update site from the feature org.eclipse.oomph.setup
and changed the eclipse-inst.ini to have below, so that feature org.eclipse.oomph.setup is installed from my custom update site

-Doomph.update.url=file:///C:/temp/org.eclipse.oomph.setup.update.site

But the installation fails, please check the below image.
Could you please help ? Thank you.
The complete error log is also attached error.log

index.php/fa/39041/0/

Attachment: InstallError.png
(Size: 126.66KB, Downloaded 407 times)
Attachment: error.log
(Size: 31.83KB, Downloaded 115 times)

[Updated on: Fri, 09 October 2020 06:10] by Moderator

Re: Oomph Customization [message #1833328 is a reply to message #1833327]

Fri, 09 October 2020 06:19

Eclipse User

I'm not sure why there are two separate p2 director tasks rather than one merged one. Did you set "Merged Disabled" on the p2 director task? The Oomph repository doesn't contain all the dependencies...

Re: Oomph Customization [message #1833331 is a reply to message #1833328]

Fri, 09 October 2020 06:34

Eclipse User

Hi,
Yes, I have set Merge Disabled to true for the P2 task of org.eclipse.oomph.setup, otherwise this is not installed from my own update site, but instead installing from
http://download.eclipse.org/releases/2020-06/202006171000

The required dependency org.eclipse.core.runtime is available in the first P2 Director task Eclipse Platform (2020-09), and this is installed before.

So then why this dependency could not be resolved ?
or
How can I install org.eclipse.oomph.setup from my own update site with Merge Disabled to false ?

[Updated on: Mon, 12 October 2020 06:44] by Moderator

Re: Oomph Customization [message #1833347 is a reply to message #1833331]

Fri, 09 October 2020 11:12

Eclipse User

I would expect the p2 version to install the stuff with the newest version. I very commonly do a local build to produce a p2 repository and run the installer with the repository, installing what I just build along with whatever is in the release train repository.

In any case, each separate p2 task must be able to resolve all the requirements so this approach is not a good way. Do your customized plugins not have higher version numbers than the one in the train repository?

Previous Topic:	Update issue with product containing fragments
Next Topic:	Stop Eclipse Installer from tampering with Eclipse JRE

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jun 17 07:45:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter