| Re: [mdt-papyrus.dev] [NEON] Papyrus version dependency issue |
|
Hi Celine, You can of course do this but rewinding the versions while keeping the changes that ended up in the upgrade seem a terrible idea to me. Plus generating a possibly completely different behavior from
the papyrus’s release. A solution would be to point to a specific build of the developper tools on Hudson but that would be no different than putting them on a specific folder accessible as an update site linked to the
papyrus version. RC4 is spinning and Neon.1 is releasing in 1week and a half so this seems to be as good a time as any to do it. (Plus as the components point to the release you will then be pointing to the 2.1.0 views plugins so you won’t have this problem
but if any changes occur later the same problem wil be faced by every component). Another temporary solution would be to add the zip/jar of a previous developer build to build against it instead of fetching the latest from Hudson. Quentin De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Céline JANSSENS Hi everyone,
Again, I’m facing trouble with eop.junit.feature that is not released because into Developper ; Certainly due to this contribution [2].
While computing Target platform for Papyrus RT, I got the following issue based on the oep.junit.feature
It seems that the released version of
oep.views.modelexplorer in the release repository [1] is
2.0.0 , but oep.junit.utils bundle in the Hudson Papyrus-Neon-Developper repo depends on the
2.1.0 version of this plugin. So the best solution would be to downgrade the dependency version of
oep.views.modelexplorer
into the oep.junit.utils
Manifest.
Do you agree ? Or do you have a better solution ?
Regards Céline [1] :
http://download.eclipse.org/modeling/mdt/papyrus/updates/releases/neon [2] : https://git.eclipse.org/r/#/c/78612/
|
