[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [orbit-dev] Declaring Orbit Build: S20230403203110 (2023-06 M1)
|
Evgeny,
These three dependencies appear to work fine as direct-from-maven
dependencies:
<dependency>
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.agent</artifactId>
<version>0.8.9</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.core</artifactId>
<version>0.8.9</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.report</artifactId>
<version>0.8.9</version>
<type>jar</type>
</dependency>
I.e., these are already available as
well-formed OSGi bundles. How about if we don't update these in
Orbit but rather provide them here?
I've already tested that this works and
can have these available within a 1/2 hour...
Regards,
Ed
On 25.04.2023 11:19, Evgeny Mandrikov
wrote:
Hello Jonah,
I was about to update JaCoCo in Orbit, but we found a
regression, today we're finishing a bug fix release and I was
about to update to it in Orbit. So I'm wondering if it would
be possible to do Orbit M2 later today? I can notify you once
done with JaCoCo update.
Hello folks,
There have been no updates to Orbit therefore I won't
be making a new build for M2 tomorrow. The Simrel maven
repo* has some updates since M1 and I encourage Orbit
consumers to move off of using Orbit for stuff that can be
consumed from Maven (directly or via simrel maven p2
repo).
Hello folks,
Following the build process on the policies[0]
I'm declaring S20230403203110 [1,2] as our
contribution for SimRel 2023-06 M1 [3].
Ed has been working on providing a p2 update
site that contains all the third-party maven
content in its original form. This p2 site will
also aggregate Orbit bundles, allowing it to be
a one-stop for all third party content,
coordinated across all the projects of SimRel.
Ed's work can be tracked in https://github.com/merks/simrel-maven/issues/3.
While we don't plan to stop producing Orbit builds
as we are doing now, we expect to no longer add
bundles that already have OSGi metadata to Orbit.
This will allow Orbit to focus on the bundles that
don't yet have OSGi metadata.
In addition to the code changes listed below,
Eclipse Orbit is now on GitHub at https://github.com/eclipse/orbit.
All the relevant content from the Eclipse Wiki has
also been migrated to GitHub as markdown files.
The contents of the p2 repository has not changed
since 2023-03 R.
The following changes are new for 2023-06 M1
since 2023-03 R:
712e15ac Force remove
the target directory
6491e6a8 Fix markdown
557c97c6 Add GitHub actions to verify Pull
Requests
2159cc7b Move key content for Orbit from wiki.eclipse.org to
GitHub
71fb7a62 Update URLs for building to new GitHub
location
d4e9da27 Bug 581504: Remove ip_log.xml
use/requirement
9e6a75e5 Update reference repo to 2023-03 R
I've also run a script comparing units (and to
some extent, their metadata) since the last
milestone or release build to be sure about what
we're publishing.
=== CHANGED ===
=== REMOVED ===
=== ADDED ===
_______________________________________________
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