Closed tsmaeder closed 9 months ago
GH build actions would also be helpful to have faster build verification (as Github actions are currently relative fast compared to Jenkins). See https://github.com/eclipse-platform/eclipse.platform.resources/blob/master/.github/workflows/maven.yml for an example
True, dat, but IMO moving CI deserves a separate issue: this is purely process help.
In any case you should document the "how to build JDT" process from the recent JDT discussions, its looks like even experience JDT developer have problems building JDT core on the command line. https://www.eclipse.org/lists/jdt-dev/msg02098.html
That is a good idea, but my pronouns are we/us ;-) Feel free to open an issue to that effect.
That is a good idea, but my pronouns are we/us ;-) Feel free to open an issue to that effect.
I have no plans for this, belongs IMHO to this issue and if you disagree, that is fine for me. I just find it shocking that even JDT core developers have no idea no to build JDt core, and hence added this suggestion to your "lets improve contibutor documentation" issue.
I just find it shocking that even JDT core developers have no idea no to build JDt core
Why would that be shocking? It's not a necessary step for developing JDT Core.
I just find it shocking that even JDT core developers have no idea no to build JDt core
Why would that be shocking? It's not a necessary step for developing JDT Core.
IMHO making the software easy to build is essential to be inviting to contributors. If you check the readmes I have created for the various platform repos other the years you find that I (almost9 always added the build instructions. to build the repo.
Done, except for codeowners which is a no-go now.
We can help contributors by providing certain files like