Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [] Neon.3 Update Problems


It is currently necessary to rebundle Orbit bundles because Orbit is not included in the xxx release repo.

I generally install at +2 time from ZIPs, at which point I get from perhaps MWE, from perhaps Mylyn, many good things from the platform etc. When I come to install some third party products I may have to explicitly grab a less common Orbit bundle.

Surely the correct Orbit should be in the Install New Software sites automatically? It would then be really easy to enforce a no rebundling rule and moderately easy to analyze the aggregation to detect multiple versions.


        Ed Willink

On 31/03/2017 08:14, Alexander Nyßen wrote:
Let's enforce that then. Looks like that would solve a lot of problems...


Am 31.03.2017 um 08:30 schrieb Mickael Istria <mistria@xxxxxxxxxx>:

The general rule would be "don't include in your feature what's not your project". It's a rule that works great, but there's nothing in our processes, UI nor build tools that enforces or even recommends it.

Dr. Alexander Nyßen
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743 

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top