Hi Gary, On Fri, Mar 22, 2019 at 5:59 PM Gary Gregory <[email protected]> wrote:
> If you dig though the archives you should find emails from me fumbling > around asking for help on building Xalan-J and the state of various > branches. > Ok. I'll look at those information. If still i'll have any doubts about any past Xalan-J topics, I'll ask please. > IIRC, I think I built 2.7.2 from the maintenance branch. > It seems to me that, the branch you're referring to is, http://svn.apache.org/repos/asf/xalan/java/branches/xalan-j_2_7_1_maint/. I guess, 2.7.2 version was released from this branch. I also think that, previous mentioned branch is the current development branch of Xalan-J team here. It also seems, Xalan-J 2.7.3 (the would be XSLT 1.0 processor) would also be released from the previous mentioned branch. Since I think, the file http://svn.apache.org/repos/asf/xalan/java/branches/xalan-j_2_7_1_maint/build.xml says <!-- Xalan Java version information --> <property name="version.VERSION" value="2"/> <property name="version.RELEASE" value="7"/> <property name="version.DEVELOPER" value=""/> <!-- Set this to 'D' if a developer release; blank "" if maintenance release --> <property name="version.MINOR" value="3"/> I think, to develop something these days for Xalan-J XSLT 1.0 processor, we should use the codebase at branch xalan-j_2_7_1_maint (at the previously mentioned branch URL). To also confirm, I guess the Xalan-J trunk still has 2.7.1 version code, and nothing more on that location. Please correct me, on any of above mentioned points, in case there is any disconnect. IMO, we should start this reboot with migrating from svn to gitbox. > I personally, would be fine with this. But I believe, I'll have a bit of learning curve for that. I think, gitbox is Apache's brand for a git backend, but otherwise its git (I've worked with git & github earlier, and it should not be a problem for me to use gitbox). But I feel, certain other people on this group may have issues working with gitbox. Xalan-J and Xerces-J are closely related and share lots of codebase between each other. If we're thinking to migrate Xalan-J to gitbox, then I feel Xerces-J should also migrate to that. Would Xerces-J migrate to gitbox due to Xalan-J's migration ? I've some doubts with that, since I haven't seen any major discussion about this on Xerces-J's list. As I can find with my readings as of yesterday, migrating to gitbox is currently not mandatory for Apache projects. If any Apache project wishes to continue with SVN, they can do so. My own wish seems to be, to continue with SVN at Xalan-J if possible. But I'll work with gitbox at Xalan-J, if that is decided. Also, are there any technical benefits of using gitbox instead of SVN, for Xalan-J ? -- Regards, Mukul Gandhi
