Le 17/06/2019 à 18:56, Mark Thomas a écrit : > The complication is the svn:external that picks up the > org.apache.tomcat.jni package from 9.0.x. Now 9.0.x has moved to git, > this no longer works.
Has it been considered to move the org.apache.tomcat.jni package from tomcat to tomcat-native? Since these Java classes are the counterpart of the native code, always evolving in sync, it would be sensible to have them in the same project. > I looked at a workaround using the "GitHub makes itself look like svn" > but that timed out for the Tomcat repo. I suspect due to size. > > I then looked at Git based solutions. sub-modules and sub-trees look to > be the two options. Of the two, sub-trees looks better: > - it is more suited to "read-only" importing > - it doesn't require any additional commands to populate the imported > code What is the workflow to use git subtrees? I googled quickly yesterday and it didn't seem that simple, but maybe I'm missing something. My understanding is that the subtree has to be explicitly configured with non trivial commands after a 'git clone'. Emmanuel Bourg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
