Capella Addon Build

Capella Studio & Kitalpha
1

Hello everyone,
I am currently in charge of maintaining an addon for Capella. So I got the sources. The addon is normally compilable with Maven but one of the repository is http://mirror.update.eclipse.obeo.fr/capella-1.4.2/ and maven indicates that this repository does not exist. Could you give me a new equivalent address?

2

After quite some time I finally managed to rebuild most of the necessary dependencies. I only have the category that concerns a dependency on the ViewPoint Requirement addon. By searching a bit I managed to identify the address of the following update site: https://download.eclipse.org/capella/addons/requirements/updates/releases/0.11.1/
However, it contains a zip archive of this Update Site. Two questions: why is the site update in this format?
Is there a particular syntax allowing Maven or more specifically TPD (Target Platform Definition) to understand that the target is a zipped update site? (for example: location="https://download.eclipse.org/capella/addons/requirements/updates/releases/0.11.1/ Requirements-updateSite-0.11.1.202011041032.zip!/)

Thank you for your answers.

3

Hi Ludovic,

http://mirror.update.eclipse.obeo.fr/capella-1.4.2 is a composite update site we have built internally from Capella product content and several add-ons (including Requirement) to avoid to (re)download identical data from releases of Capella, its third parties, the platform and the add-ons on every builds of several internal projects and/or products. It also workarounds the availability of some add-ons as zipped dropins or update sites.

You might try the following locations:


location Requirements-0.11.1-url-to-zip "jar:https://download.eclipse.org/capella/addons/requirements/updates/releases/0.11.1/Requirements-updateSite-0.11.1.202011041032.zip!/" {
		org.polarsys.capella.vp.requirements.feature.feature.group lazy
	//Very slow to get completion
}


location Requirements-0.11.1-folder-win "file:/D:/your/local/path/Requirements-updateSite-0.11.1.202011041032/" {
	org.polarsys.capella.vp.requirements.feature.feature.group lazy
	//...
}

location Requirements-0.11.1-zip-win "jar:file:/D:/your/local/path/Requirements-updateSite-0.11.1.202011041032.zip!/" {
	org.polarsys.capella.vp.requirements.feature.feature.group lazy
	//...
}

location Requirements-0.11.1-folder-macOS "file:/Users/YourProfile/Downloads/Requirements-updateSite-0.11.1.202011041032/" {
	org.polarsys.capella.vp.requirements.feature.feature.group lazy
	//...
}

location Requirements-0.11.1-zip-macOS "jar:file:/Users/YourProfile/Downloads/Requirements-updateSite-0.11.1.202011041032.zip!/" {
	org.polarsys.capella.vp.requirements.feature.feature.group lazy
	//...
}

It seems that the jar:https://xxxxx/xx.zip!/ approach is working at least from the .tpd.
The .target generation and resolution should work but might be slow, very slow.
I would recommend to download the zip and put it somewhere close to your build.

Regards

4

Hello Maxime,

Thank you for that answer. I was able to confirm two points:

  1. the jar:https://xxxxx/xx.zip! syntax is indeed and fortunately compatible with targetplatform-dsl.
  2. Indeed it takes a little longer but only during the first generation of the target file. After time is a relative thing :slight_smile:
    Thanks again for your help.