When we decomposed the toolchain, we kept the original naming conventions of the EF regarding our repository names.
We are kicking around a mass rename to essentially follow maven naming conventions.
jetty.websocket.api - > jetty-websocket-api
jetty.servlet.api -> jetty-servlet-api
jetty.setuid -> jetty-setuid
jetty.test.helper -> jetty-test-helper
jetty.perf.helper -> jetty-perf-helper
jetty.alpn.api - > jetty-alpn-api
jetty.artifact.resources -> jetty-artifact-remote-resources
jetty.assembly.descriptors -> jetty-assembly-descriptors
jetty.schemas -> jetty-schemas
jetty.schemas.xhtml -> jetty-xhtml-schemas
jetty.docker -> jetty-docker
jetty.parent -> jetty-parent
jetty.test.policy -> jetty-test-policy
We are also thinking of fixing jetty.project so:
jetty.project -> jetty
The website is in a bit of flux but eventually:
jetty.website.2020 -> jetty-website-2020
jetty-website -> jetty-website-2023
jetty.website -> jetty-website ( or just website ) once jetty.org is deployable
When we decomposed the toolchain, we kept the original naming conventions of the EF regarding our repository names.
We are kicking around a mass rename to essentially follow maven naming conventions.
jetty.websocket.api - > jetty-websocket-api
jetty.servlet.api -> jetty-servlet-api
jetty.setuid -> jetty-setuid
jetty.test.helper -> jetty-test-helper
jetty.perf.helper -> jetty-perf-helper
jetty.alpn.api - > jetty-alpn-api
jetty.artifact.resources -> jetty-artifact-remote-resources
jetty.assembly.descriptors -> jetty-assembly-descriptors
jetty.schemas -> jetty-schemas
jetty.schemas.xhtml -> jetty-xhtml-schemas
jetty.docker -> jetty-docker
jetty.parent -> jetty-parent
jetty.test.policy -> jetty-test-policy
We are also thinking of fixing jetty.project so:
jetty.project -> jetty
The website is in a bit of flux but eventually:
jetty.website.2020 -> jetty-website-2020
jetty-website -> jetty-website-2023
jetty.website -> jetty-website ( or just website ) once jetty.org is deployable