From jonathan.gibbons at oracle.com Thu Mar 5 01:15:29 2020 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Wed, 4 Mar 2020 17:15:29 -0800 Subject: Result: New Code Tools Committer: Erik Helin In-Reply-To: <06f49610-3186-c07f-8abd-aa37948731e1@oracle.com> References: <06f49610-3186-c07f-8abd-aa37948731e1@oracle.com> Message-ID: Voting for Erik Helin [1] is now closed. Yes: 5 Veto: 0 Abstain: 0 According to the Bylaws definition of Lazy Consensus, this is sufficient to approve the nomination. -- Jonathan Gibbons [1] https://mail.openjdk.java.net/pipermail/code-tools-dev/2020-February/000567.html From jonathan.gibbons at oracle.com Wed Mar 18 17:06:10 2020 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Wed, 18 Mar 2020 10:06:10 -0700 Subject: Code-Tools, Git and Skara Message-ID: <6f9be6f4-6c3c-7e2a-0cd6-57c627cf180d@oracle.com> As many or most of you know, there is work underway to investigate moving OpenJDK repos from Mercurial to Git. This is described in Project Skara[1], JEP 357[2] and JEP 369[3]. Project Skara provides CLI tools for interacting with Git and GitHub[4] for those contributors that prefer working from a terminal. You can find more info about these CLI tools on the Skara wiki page [5]. There are already Git mirrors for many OpenJDK repos on Github and some projects have already migrated. The Code Tools Project is a collection of sub-projects. There are currently read-only mirrors of all Code Tools sub-projects on GitHub, you can it use to try out Git and some of the CLI tooling, though submitting pull requests and pushing will not work (as they are read-only mirrors). Now, some Code Tools sub-projects are now interested to migrate as well. A transition for a Code Tools sub-project entails switching to Git as an SCM and the repository will be hosted on GitHub. After the transition, the current Mercurial repository for the sub-project will become a read-only archive and will no longer be updated. The following Code Tools sub-projects have already expressed an interesting in transitioning Git, GitHub and Skara: - JCov - JTHarness - asmtools Announcements and discussions of such transitions will take place on each sub-project's mailing list, for example jtharness-dev at openjdk.java.net for the JTHarness sub-project. Thanks, Jonathan Gibbons [1] https://openjdk.java.net/projects/skara/ [2] https://openjdk.java.net/jeps/357 [3] https://openjdk.java.net/jeps/369 [4] https://github.com/openjdk/ [5] https://wiki.openjdk.java.net/display/skara From christoph.langer at sap.com Thu Mar 19 09:39:14 2020 From: christoph.langer at sap.com (Langer, Christoph) Date: Thu, 19 Mar 2020 09:39:14 +0000 Subject: jcheck and python3 Message-ID: Hi, I recently updated mercurial on my Mac via brew and now I'm at python3. I had to recognize, that jcheck is still python2 only. I played a bit with it but had to recognize that it seems quite a bit of work to make jcheck python3 compatible. On the other hand, I don't know how to switch my brew installed mercurial back to python 2.7. So, I'd like to ask on the mailing list: Has anybody started work on making jcheck python3 compatible? Or alternatively, how can I change python version of my mercurial installation? Thanks Christoph From erik.helin at oracle.com Mon Mar 23 14:33:14 2020 From: erik.helin at oracle.com (Erik Helin) Date: Mon, 23 Mar 2020 15:33:14 +0100 Subject: jcheck and python3 In-Reply-To: References: Message-ID: <4a85a8d5-c5f8-b520-e603-43d17adb8879@oracle.com> On 3/19/20 10:39 AM, Langer, Christoph wrote: > Hi, > > I recently updated mercurial on my Mac via brew and now I'm at python3. I had to recognize, that jcheck is still python2 only. I played a bit with it but had to recognize that it seems quite a bit of work to make jcheck python3 compatible. On the other hand, I don't know how to switch my brew installed mercurial back to python 2.7. > > So, I'd like to ask on the mailing list: Has anybody started work on making jcheck python3 compatible? Or alternatively, how can I change python version of my mercurial installation? I have not worked on making jcheck [0] Python 3 compatible, but I can mention that Skara's Mercurial extension [1] is Python 3 compatible and gives you access to backwards compatible (and Python 3 compatible) versions of defpath, jcheck and webrev. So if you want you can just install the Skara Mercurial extension [1] and then you should be able to use `hg defpath`, `hg jcheck` and `hg webrev` as usual. If you find anything that is not working or something that is not backwards compatible, then please file a bug. Thanks, Erik PS. The Skara Mercurial extension is just a very thin wrapper around the Skara CLI tools [2]. So if you already have the Skara CLI tools installed then you can just pass the --mercurial flag to git-defpath, git-jcheck and/or git-webrev and they will work on Mercurial repositories as well. [0]: https://hg.openjdk.java.net/code-tools/jcheck [1]: https://wiki.openjdk.java.net/display/skara/Mercurial [2]: https://wiki.openjdk.java.net/display/SKARA/CLI+Tools > Thanks > Christoph