| Re: [ease-dev] Oxygen TP with EASE |
Hi Alain, Jonah wrote about all solutions I can think of. I will look into the dependency problem with oxygen latest next week. If you can wait that long that would be the simplest solution. The final hint is also something I would highly recommend: nightlies can break API whenever we feel need to. If you want to depend on the nightly builds, have a mirror of your own to have full control on the update cycle. Christian From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Jonah Graham As for using the last release, that is not resolvable in Oxygen without rebuilding the 0.4.0 version. See https://dev.eclipse.org/mhonarc/lists/ease-dev/msg00590.html for more details. As for the MD5, I had a quick go and could not see the problem. Two possibilities: 1) do you have a caching proxy that you connect via? Is it possible that the file cached is bad? 2) There is a bad mirror or slow mirror out there and you are getting a bad snapshot in time. The way to resolve this is to download ease as a zip and see if it works from a local zip file, but at the moment a zip of the P2 site isn't published. Perhaps an EASE committer can start publishing the zip file along with the expanded p2 sites? The final option is to build EASE locally, I would highly recommend this if you are not using official releases so you can control when you collect updates and don't accidentally get transient bad versions of EASE. HTH, Jonah ~~~ On 18 July 2017 at 12:40, BERNARD, Alain <alain.bernard@xxxxxxxxxx> wrote: Hi, I’m currently looking at migrating our target platform to Oxygen, but I’m not able to achieve this. I cannot use the “release” update site of EASE because of a too restricted version range in the dependency to o.e.ui.workbench. In the meantime, I’m not able to use the nightly builds repository too, because I have this error when attempting to load the target platform: “MD5 hash is not as expected…”
Any clue how I can solve that? Alain The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
