'Perform Setup Tasks..' P2 task doing more than I'd expect [message #1857706] |
Tue, 21 February 2023 23:59 |
Mark Lawrence Messages: 28 Registered: February 2023 |
Junior Member |
|
|
A large number of requirements are installed from a range of different repositories for an Oomph product & project combination I've been working on. This is an old product based on Photon.
My intention was for everything to be installed at BOOTSTRAP. Then after BOOTSTRAP it is only a few requirements I would like to ever be considered for update. So most of my P2 repos are only set up to trigger on BOOTSTRAP only, then I have a select few set to BOOTSTRAP STARTUP MANUAL.
This doesn't appear to be honoured though. If I run 'Perform Setup Tasks' I will see the P2 task with only the P2 Repos I'm expecting, but in nested elements I can see its trying to get a brand new eGit, Mylyn, & oomph, which I believed I had set to only install at BOOTSTRAP. To add to that, if I run the Tasks, I will get 'missing requirement' errors for features that are part of other P2 repos I've set for BOOTSTRAP only.
To combat some of this, I've put redirections on the eGit/Mylyn/Oomph update site URLs its using so its not using latest but rather a fixed version URL site (the version of the one installed), so updates aren't found, and I've also tried making all my previously BOOTSTRAP only repos to BOOTSTRAP STARTUP MANUAL, however that then seems to take ages fetching every single requirement that is already installed and eventually fails with a 'Error reading signed content' error.
Does the behaviour I'm seeing make sense? Is there any way to just get it to update just a small selection of plugins? If not, is there anyway to disable the P2 task in 'perform setup tasks...' because at the moment, I cannot get a successful 'Perform Setup Tasks...' run, it always fails for any of the reasons above.
|
|
|
|
|
|
Re: 'Perform Setup Tasks..' P2 task doing more than I'd expect [message #1857750 is a reply to message #1857728] |
Fri, 24 February 2023 00:05 |
Mark Lawrence Messages: 28 Registered: February 2023 |
Junior Member |
|
|
Thanks for replying Ed. I don't really have much movement on the JDK. I have to use Photon, & it must point to an IBM Java 8 due to certain plugins we use.
Though I have made some progress. I had a resource creation task modifying the list of available update sites so most were disabled (for the same reason as above, so only a few plugins would get updated when running 'Check for Updates', I was also getting 'No Remedy Found' errors when running it), as soon as I took out this Resource Creation task and I made all my P2 repos trigger on all events, the 'Perform Setup Tasks' P2 tasks runs to completion! Looking good....
....but not quite. After restart, I found that the install had been broken. Lots of errors & missing requirements. Turns out that the 'Perform setup tasks' process isn't installing the requirements in the correct place (as if it forgets installation.location), rather than installing to:
/Users/<my user name>/eclipse/<product name>/Eclipse.app/Contents/Eclipse
it's choosing to install missing requirements to:
/Users/Eclipse.app/Contents/Eclipse
This is down to something I mentioned I was going to do in another post. I need the 'configuration' folder to be outside the Eclipse.app bundle so that I can sign the Eclipse.app bundle and the signature not be broken soon after loading Eclipse with a changing internal 'configuration' folder (this is so secure storage plays nicely on Mac with other Eclipse instances). I got that working by adding osgi.configuration.area=${installation.location/}configuration to the config.ini. However, Oomph doesn't do this straight away during install. A few things get written in the 'configuration' folder within the Eclipse.app bundle before the line gets added. One of those folders is 'org.eclipse.oomph.setup'. Anyway, as soon as I disable my config.ini modification task and re-install, everything works great.
Is what I'm doing regarding the move of the configuration folder ok to do? It seems Oomph might expect it in a certain place? Can I change the [b]configuration:[\b] value used in Oomph?
Is there a way I can correct this path being used? How is it calculated? Looks like it might decide where to install requirements based on relative path to the 'configuration' folder, maybe?
[Updated on: Fri, 24 February 2023 00:07] Report message to a moderator
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04275 seconds