The ee4j folder is for staged artifacts, and should in theory be deleted by the project after the TCK is signed and published by the specification committee.
It sounds like going forward we should do that as an after (publishing) step then. At one point I though we wanted to keep the snapshots around for validation reasons but I do not recall ever really needing to go back in time to do such validations.
Scott
Anyway, none of these go away by these changes. As long as we have linked directly to the artifacts in the folder, we are fine. It is only in the cases where we use the download.php for the download, like:
I think that most, if not all, the specification pages use the direct link and not the download.php version, but we should probably go through them to make sure.
I am curious especially in relation to TCK packages, which were
not distributed anywhere else, for example
jakarta-jakartaeetck-10.0.7.zip at
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/
. All links on this page use download.php. I have no rights on
this page, what exactly we should do with that? Is this content
just lost by the middle of March? Or somebody just resolves
that?
On Wed, 2026-02-25 at 16:18 -0500, Eclipse Infrastructure via
eclipse.org-committers wrote:
Hi Everyone,
I wanted to remind everyone of 2 upcoming service changes.
First: we are rapidly approaching[1] the removal of PHP
support on both download.eclipse.org and archive.eclipse.org
. If you haven't already moved to HTML on those sites, using
a tool like wget to 'convert' your existing PHP content is a
quick option in the remaining time.
Second: wiki.eclipse.org will be
replaced by 'service shutdown' page in Q2 2026[2]. If your
project has moved it's content elsewhere and you'd like a
'top level'(ie: wiki.eclipse.org/ocl) redirect
that will remain active even after the shutdown, now is a
great time to request it via the helpdesk[3].
There will also be one more wiki service brown out running
from March 10-13 2026.
If you have any questions please feel free to ask the Infra
team.
This list is mandatory for all committers and cannot be
unsubscribed. Questions: privacy@xxxxxxxxxxx
_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
This list is mandatory for all committers and cannot be unsubscribed. Questions: privacy@xxxxxxxxxxx
_______________________________________________
eclipse.org-committers mailing list eclipse.org-committers@xxxxxxxxxxx
This list is mandatory for all committers and cannot be unsubscribed. Questions: privacy@xxxxxxxxxxx
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation
Eclipse Foundation - Community. Code. Collaboration.
_______________________________________________
eclipse.org-committers mailing list eclipse.org-committers@xxxxxxxxxxx
This list is mandatory for all committers and cannot be unsubscribed. Questions: privacy@xxxxxxxxxxx