| Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Changes in the elementtypesconfigurationsframework |
Hi Florian Thanks for the documentation. Nevertheless I have several problem in Papyrus components [1] due to the target platform. Do you have any idea if the following problem is or not related to your migration? It is strange the 3.0.0 ? Thanks for the advice. Francois [ERROR] Cannot resolve target definition: [ERROR] Software being installed: org.eclipse.papyrus.dev.feature.feature.group 2.0.0.201608050223 [ERROR] Missing requirement: org.eclipse.papyrus.dev.types 1.2.0.201608050223 requires 'bundle org.eclipse.papyrus.infra.types.core [3.0.0,4.0.0)' but it could not be found [ERROR] Cannot satisfy dependency: org.eclipse.papyrus.dev.feature.feature.group 2.0.0.201608050223 depends on: org.eclipse.papyrus.dev.types [1.2.0.201608050223] [1]: https://hudson.eclipse.org/papyrus/view/Designer/job/papyrus-designer-gerrit/255/console De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de NOYRIT Florian Dear Papyrus contributors, As explained in https://wiki.eclipse.org/Papyrus/Migration_Guide/Oxygen#ElementTypesConfiguration_Framework, there are changes in the elementtypes configuration framework. All known uses in Papyrus have been migrated. External uses will have to migrate. A little developer tool that assists the migration is available in the developer tools (org.eclipse.papyrus.dev.types). Note that advice ordering has to be migrated manually. Best regards. /Florian |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature