[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [orbit-dev] Orbit Versus Maven
|
Wim,
I know you've asked before, but I don't really need help so much,
which is not being ungrateful , it's just that I need a quiet
time. I've already merged EMF and XSD into one repo over
Christimas and migrated it to GitHub right after 2023-03. JustJ
is also migrated. So I know what to do and I know it's not all
that difficult.
What I might do though is ask the IT staff if I can migrate just
the Oomph incubator repo right now and the rest of Oomph later
(after the 2023-06 release). The tricky thing with Oomph is that
there are so many uses of URIs that point at git.eclipse.org for
setup and I'm going to have to come up with a migration strategy
for that. And I can't focus on that challenge while I get pulled
in 5 difference directions on a daily basis...
Thanks for the offer though! It's the thought that counts!!
Cheers,
Ed
On 08.04.2023 12:45, Wim Jongman wrote:
> (Sorry, Oomph is not yet migrated to Github, so I keep this
in my account repo for now.)
Do you need help with that, Ed?
Great work! I hope the Simrel work flow will
become reusable soon, lots of projects would benefit from
the effort.
Cheers,
Hi,
As most of you know, Orbit provides regular builds
scheduled to
coordinate with the SimRel schedule. For 2023-06 M1,
Jonah produced
this build:
https://download.eclipse.org/tools/orbit/downloads/drops/S20230403203110/index.html
and this specific p2 repository:
https://download.eclipse.org/tools/orbit/downloads/drops/S20230403203110/repository
This repository composes the latest such stable build:
https://download.eclipse.org/tools/orbit/downloads/latest-S/
It is currently planned to reduce what's available via
Orbit. In
particular, we plan to stop adding new versions of
libraries to Orbit
for those libraries available at Maven Central with proper
OSGi
metadata. For such libraries one can use the m2e location
in your
project's *.target to fetch those libraries (and ensure
that you PGP
sign them), or use what's described below.
For SimRel I have analyzed those contributing projects
that are pulling
libraries directly from Maven and have implemented
dependabot-like tools
to help keep those projects up-to-date with the latest
version as
described here:
https://github.com/merks/simrel-maven/blob/main/README.md
I've been helping the Platform directly with this
activity; WWD and tm4e
ought to have a look at the reports generated for them...
In any case, starting for 2023-06 M1, I will produce
regular milestone
builds (and eventually release/recommend builds) of all
the
direct-from-maven libraries being contributed by SimRel
projects,
updated to their latest available minor version:
https://download.eclipse.org/oomph/simrel-maven/milestone/S202304041507
This will always reference the latest such milestone:
https://download.eclipse.org/oomph/simrel-maven/milestone/latest
In fact, there are a few additional libraries added
because the build
infrastructure tests that each library's transitive
requirements are
satisfied by other libraries in the repository. Going
forward, we plan
to add libraries to this repository to replace the older
version in
Orbit and also removing the library from Orbit. Of course
these
libraries are all PGP signed.
To complement the Orbit repository and the
direct-from-maven repository,
I will also be producing regular milestone (and eventually
release/recommend builds) of the aggregation of those two
repositories,
e.g., this for M1:
https://download.eclipse.org/oomph/simrel-orbit/milestone/S202304041533
This repository composes the latest such stable build:
https://download.eclipse.org/oomph/simrel-orbit/milestone/latest
While building that repository (using the CBI p2
aggregator), I noticed
that a significant number of the bundles in the latest
Orbit stable
build depend on bundles that are only available in older
Orbit builds.
So the aggregation also pulls in any transitively-required
bundles from
the final older (CVS-driven) Orbit recommended (release)
repository. As
such, the simrel-orbit repository is transitively complete
with respect
to requirements.
The simrel-orbit repository is intended to provide
one-stop-shopping to
cover all your Orbit requirements and to help coordinate
the versions of
all your direct-from-maven requirements. Please try to
use the latest
versions available here, and look at your reports to avoid
duplication
and to avoid problems like the highly-problematic
multiple-gsons problem
we had during the previous release cycle.
If you have questions, please read the details in the
following issue
and ask the questions on that issue to avoid spamming this
mailing list:
https://github.com/merks/simrel-maven/issues/3
(Sorry, Oomph is not yet migrated to Github, so I keep
this in my
account repo for now.)
Regards,
Ed
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/orbit-dev