Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [embed-cdt-dev] Until and unless a new composite is provided the upgrade feature won't be available

The purpose of those lines is to have those p2 sites listed in the EPP EmbedCPP package as an available site. If you make that URL a composite then the Check for Updates will give users a way to update. The composite just means that it has multiple child p2 sites (e.g. one for 6.0.0 and one for 6.0.1).

CDT does it like - see the compositeArtifacts.xml and compositeContent.xml files - for CDT they are managed in cdt-infra and copied from github to with the CI job which uses this Jenkinsfile and script


Jonah Graham
Kichwa Coders

On Tue, 24 Nov 2020 at 02:12, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:
Hi Jonah,

You made this comment in the org.eclipse.epp.packages.git/packages/org.eclipse.epp.package.embedcpp.feature/p2.inf file, at the end, and commented out two lines:

# org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(location:https${#58}//,type:0,name:EmbedCDT,enabled:true); \
# org.eclipse.equinox.p2.touchpoint.eclipse.addRepository(location:https${#58}//,type:1,name:EmbedCDT,enabled:true);

(there are two more at the very end, I'll comment them too)

Is this something that we should consider for 2020-12, or can be postponed for the next release?

I currently don't know how to make a "new composite", but since in v6.0.0 the update site will be anyway different, perhaps in a further release we can address this too and add the "releases/6.0" site.



embed-cdt-dev mailing list
To unsubscribe from this list, visit

Back to the top