Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] complete or composite?

Hi Tony,

In the hope of providing you a quick answer (but possibly incomplete) I refer you to the announcement email ( that says:

 this is a composite repository combining a newer
build (R20191115185527) that is based on the last good build from CVS
(20160520211859, Neon) and the same bundles from the 2020-03 RC1
contribution to orbit-recipes [3].

Does that answer your question?


On Thu., Apr. 9, 2020, 19:15 Homer, Tony, <tony.homer@xxxxxxxxx> wrote:

I just noticed that org.apache.lucene.queryparser_8.0.0 is available in 2019-12 and disappeared from 2020-03

This seems a little different from the differences I noted below.

Was this an intentional change?


From: "Homer, Tony" <tony.homer@xxxxxxxxx>
Date: Thursday, April 9, 2020 at 3:41 PM
To: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Subject: complete or composite?


I know that we should use the composite here

But we use a Nexus proxy p2 site and have run into trouble with pointing to composites, so our current practice is to point directly to the final build repo instead.


I was reviewing the list of dependencies available in the latest 2020-03 Orbit p2 repo at


I noticed that there are some bundles missing from there that are present here


For example:





I imagine if I were using the 2020-03 composite repo they would resolve, but I am wondering if this is expected?

Another way to put it is, if you review the list of bundles available in Orbit 2020-03 by looking through all the links:


Is it expected that some would only be available via build repos from previous Orbit releases?




orbit-dev mailing list
To unsubscribe from this list, visit

Back to the top