Source: devops.com
Oracle Proposes Replacing Mercurial SCM for Java With GitCategory: Business, Kubernetes, github, gitlab
Home » Blogs » DevOps Practice » Oracle Proposes Replacing Mercurial SCM for Java With Git
Oracle today at its Oracle Developer Live—Java event proposed making a bevy of updates to Java that includes replacing the Mercurial source code management (SCM) platform, which is the repository Oracle created to share updates to the Java community, with Git starting with the initial availability of Java 16 and then migrating the project itself to GitHub. In addition, Oracle has developed server-side tooling compatible with GitHub and GitLab and client-side tooling compatible with Git and Mercurial to aid in the migration.
Oracle is also proposing to add a Vector application programming interface (API), along with enabling some C++ features in Java 16.
By embracing Git and GitHub, the Java community will be able to more fluidly coexist with a wide range of open source projects being created using a diverse range of programming tools.
Oracle today at its Oracle Developer Live—Java event proposed making a bevy of updates to Java that includes replacing the Mercurial source code management (SCM) platform, which is the repository Oracle created to share updates to the Java community, with Git starting with the initial availability of Java 16 and then migrating the project itself to GitHub. In addition, Oracle has developed server-side tooling compatible with GitHub and GitLab and client-side tooling compatible with Git and Mercurial to aid in the migration.
Oracle is also proposing to add a Vector application programming interface (API), along with enabling some C++ features in Java 16.
By embracing Git and GitHub, the Java community will be able to more fluidly coexist with a wide range of open source projects being created using a diverse range of programming tools.
Related Articles
Community Partners
DevOps Careers