While the most of the Eclipse sources appear to be oriented to Java 11, I wasn't able to build with Java 11. The patched R4_25 port will require Java 17 or later. rt.amework/bundles/% => equinox/bundles/% rt.equinox.bundles/% => equinox/bundles/% thye, , and sources have been consolidated to the atform repository - respectively, as atform/team, atform/runtime and atform/resources. I've tried to combine patches for the consolidated repositories. Some of the Eclipse repositories have been consolidated between R4_24 and R4_25. If I may be able to spin up a cloud image and submit a pull request from there, then once the pull request goes through, this patch could be updated for normal R4_25 release builds. I'm seeing 461MB of dependencies under work/eclipse-maven-repo-4.25/ after some various builds. My own network connection is fairly limited for upstream data, and it can be fairly spotty for downstream. I'd like to forward a pull request to eclipse-maven-repo though candidly, I'm not sure about the time scale for that. For the update from R4_24 to R4_25, and until a pull request can be forwarded to eclipse-maven-repo the patch will require network access in the build environment, in order to complete the maven dependency resolution for the build. I've developed a patch for R4_25 on amd64, attached.Īlbeit, this patch may not be immediately usable for some builds with Poudriere. There's a new release of the Eclipse IDE and dependent components, R4_25. Interim update for R4_24 => R4_25 (needs network for maven dependencies)
0 Comments
Leave a Reply. |