Good Morning everyone,

I didn't notice that earlier, sorry for that.

Yes, we (RAP) didn't contribute an M1 build yet, mostly because it is not
yet ready with the many required Java, Maven, Tycho version changes, and
some of our test cases are still failing.
Therefore I created change 201201
<https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/201201> in
Gerrit that temporarily disables our contribution together with the
dependent single EMF-RAP feature for M1. If a respin is okay I would
proceed and merge that change.

Thanks
Markus



On Thu, 13 Apr 2023 at 08:45, Ed Merks <[email protected]> wrote:

> FYI,
>
> As I was about to send out the note below, but I thought, let me have look
> at the reported duplicates:
>
>
> https://download.eclipse.org/staging/2023-06/buildInfo/archive/download.eclipse.org/staging/2023-06/
>
> Oh my goodness, up to 55!  Worse still, there are two versions of Jetty
> and even two versions of some of the Platform's bundles:
>
> Why is that?
>
> RAP needs the older version because it has not contributed a new build for
> M1.  Nor can I find a more recent build than the 3.24 release here:
>
> https://download.eclipse.org/rt/rap/
>
> I'm not sure the resulting repository is really consumable for EPP.
> Certainly the RAP package is unlikely to work...
>
> So I suspect a respin will be needed...
>
> ______________________________________________
>
> The staging repository content of
>   https://download.eclipse.org/staging/2023-06/
>
> has been promoted to the following repository for 2023-06 M1:
>
>   https://download.eclipse.org/releases/2023-06 /202304141000/
>
> This is ready for consumption by EPP.
>
> Baring a respin, it will become visible in the composite as scheduled
> Friday April, 14th, 2023:
>
>   https://download.eclipse.org/releases/2023-06
>
> Regards,
> Ed
>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to