Eclipse Community Forums: Plugin Development Environment (PDE) » Publishing update site with Eclipse Tycho

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » Publishing update site with Eclipse Tycho

Show: Today's Messages :: Show Polls :: Message Navigator

Publishing update site with Eclipse Tycho [message #1844856]

Tue, 28 September 2021 07:12

Daomephsta -

Messages: 4
Registered: September 2021

Junior Member

Initially I used PDE Build for my plugin, but I wanted an automated solution. After some research I found that Maven + Eclipse Tycho is the modern build system for Eclipse plugins.
So I migrated my plugin using this tutorial. I also added the tycho-versions plugin to easily synchronise version numbers. mvn clean package succeeds, but the built update site only contains the latest versions of its plugins and features.
As I understand them, update sites should contain all versions, so that users can use older releases if necessary. How can I append to an existing update site instead of building one from scratch?
The whole project is available as a Git repository.

I found this StackOverflow answer, but had to use absolute paths to get the goal to succeed. Even then it doesn't work correctly. Based on it I added this as the last plugin in project.build.plugins, but that results in this log full of warnings like

[WARNING] Mirror tool: Problems resolving provisioning plan.: [Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.core.resources 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.core.runtime 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.ui 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; com.google.gson 2.8.6.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; com.google.guava 30.1.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.jdt.core 3.26.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.ui.workbench.texteditor 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.jface.text 3.18.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.core.expressions 3.7.100.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.jdt.ui 3.23.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280656 to osgi.bundle; org.eclipse.ui.editors 3.14.100.]
Mirroring: org.eclipse.update.feature,daomephsta.fabriclipse.feature,0.0.1.202109280656 (Descriptor: canonical: org.eclipse.update.feature,daomephsta.fabriclipse.feature,0.0.1.202109280656)
Mirroring: osgi.bundle,daomephsta.fabriclipse,0.0.1.202109280656 (Descriptor: canonical: osgi.bundle,daomephsta.fabriclipse,0.0.1.202109280656)

and the update site at the destination isn't updated

[Updated on: Tue, 28 September 2021 07:24]

Report message to a moderator

Re: Publishing update site with Eclipse Tycho [message #1844857 is a reply to message #1844856]

Tue, 28 September 2021 07:22

Daomephsta -

Messages: 4
Registered: September 2021

Junior Member

It just occurred to me to check if the update site was updated rather than relying on the timestamp. It is updated, but there are two versions of the feature and plugin created with every build, one with a qualifier 2 minutes older than the other, but the creation times are the same.

Report message to a moderator

Re: Publishing update site with Eclipse Tycho [message #1844860 is a reply to message #1844857]

Tue, 28 September 2021 09:08

Daomephsta -

Messages: 4
Registered: September 2021

Junior Member

I realised that the mirror goal was causing duplicates because it was running for multiple subprojects. Created a POM for the update-site and moved it in there, only one copy per build now!
Still getting a big warning

[WARNING] Mirror tool: Problems resolving provisioning plan.: [Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.core.resources 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.core.runtime 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.ui 0.0.0.; 
Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; com.google.gson 2.8.6.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; com.google.guava 30.1.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.jdt.core 3.26.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.ui.workbench.texteditor 0.0.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.jface.text 3.18.0.; Unable to satisfy dependency 
from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.core.expressions 3.7.100.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.jdt.ui 3.23.0.; Unable to satisfy dependency from daomephsta.fabriclipse 0.0.1.202109280846 to osgi.bundle; org.eclipse.ui.editors 3.14.100.]

Report message to a moderator

Previous Topic:	Unable to generate resolutions for marker
Next Topic:	How to resolve the dependency on pdebuild.jar

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 10:17:43 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter