Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epsilon-dev] 2.2 release

Hi Dimitris,


I’ve updated the Orbit repository reference to the latest R and bumped up the Tycho version to the recently released 2.0.0. It doesn’t seem to have made any difference to the generated content.xml. I’m wondering if we want to duplicate each repository reference with “type=1” in the generated content.xml, what method you would suggest? There are many possibilities but I’m just thinking that maybe this isn’t the best solution; after all, if this was really necessary then Tycho would’ve done it, or at least offer the option. I’ve not found anything on the mailing list, Bugzilla, forums, documentation etc. which suggests that this is a common issue or that a workaround exists. Perhaps the closest is [1], but the documentation is blank.


Also since I have never been able to consistently reproduce installation issues, I’m inclined to suggest leaving things as they are and hope for the best; maybe the issue with mirrors will have sorted itself out with the latest Orbit repo (and given that it is only a few Orbit dependencies that were causing issues, not e.g. Emfatic or GMF), we may not need to do anything.

If you have a suggestion for a relatively trivial “fix” (in quotes since I can’t reproduce the problem, or evaluate the solution) then I suppose there’s no harm in trying it prior to the release. If not, we can continue investigating and fix it for 2.3, now that we have unlimited releases until next May?


Another option would be to manually add some references to the composite update site, but I’m not sure if it will work since composites are treated differently. Actually, since the Orbit repository we refer to is a composite, that might be what’s causing the issue, since Emfatic and GMF are not composites.







From: Dimitris Kolovos
Sent: 01 September 2020 09:45
To: Epislon Project developer discussions
Subject: Re: [epsilon-dev] 2.2 release


Hi Sina,


Releasing 2.2 makes sense to me. It'd be nice to also sort out the

Orbit update site issue for 2.2 now that we know what's going wrong.





On Wed, 26 Aug 2020 at 12:30, Sina Madani <sinadoom@xxxxxxxxxxxxxx> wrote:


> Hi everyone,




> With the addition of the Pinset language, Tuple types, the ?= operator (assign if null), some enhancements to Picto, the removal of Apache POI 3.10.1 from the repo (we now use 4.1.1 from Orbit), using and plantuml from Orbit, tidying up the update site categories, etc. I propose that we release 2.2 as soon as the next LTS (“R”) Orbit repo is available (or shortly after). I think that will be the end of this week. Any objections or suggestions?




> Thanks,


> Sina




> _______________________________________________

> epsilon-dev mailing list

> epsilon-dev@xxxxxxxxxxx

> To unsubscribe from this list, visit





Dimitris Kolovos

Professor of Software Engineering

Department of Computer Science

University of York




epsilon-dev mailing list


To unsubscribe from this list, visit


Back to the top