From: <fwi...@gm...> - 2020-05-28 23:56:03
|
On Mon, May 25, 2020 at 8:44 AM Jeff Allen <ja...@fa...> wrote: > We've wanted to do this for ages. If you go back far enough, you can > find Jim confidently asserting we'd use GitHub for 2.7.2 > ( > https://sourceforge.net/p/jython/mailman/jython-dev/thread/CAOhO%3DaO_4GruQXQqmZk39a0C%3DXUnKyj%3DG6OcQtBkhtoQm9BCjw%40mail.gmail.com/#msg35054683 > ). > > Building with Gradle and accessing dependencies remotely (no JARs > checked in) were identified as prerequisites at the time. In turn, I > think building with Gradle requires re-organising the code to fit with > its /convention over configuration/ idea > ( > https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:use_standard_conventions). > > At least, doing otherwise in 2.7.2 got too difficult for me, somewhere > around exposed classes ISTR. > > These don't seem to be prerequisites for the move. I would do Jython 3 > that way, but leave 2.7.3 as it is. > > https://bugs.jython.org/issue2892 opened to cover this. I'll try, > starting withthe obvious way > ( > https://help.github.com/en/github/importing-your-projects-to-github/importing-a-repository-with-github-importer) > > and reading what CPython did. I'd be happy to take input from anyone > with a sure-fire answer. > Great news! -Frank |