Thanks, xmlstarlet makes it straightforward to get the canonical XML. It looks like our schema.xml files are rather different from files like solr/example/solr/collection1/conf/schema.xml
Any suggestions of sections I should focus on? On Sat, May 4, 2019 at 8:11 AM Alexandre Rafalovitch <arafa...@gmail.com> wrote: > XMLStarlet still works just fine. So if you want the fast way, that is the > one. > > Otherwise, some xml editors can do it (not sure which ones) or you can look > for XSLT or XQuery examples on the web. > > XMLStarlet actually just spits out XSLT internally, or even externally if > you ask. > > Regards, > Alex > > > On Fri, May 3, 2019, 10:30 PM Doug Reeder, <d...@ahlbrandsgroup.com> > wrote: > > > Thanks! Diffs for solr.xml and zoo.cfg were easy, but it looks like we'll > > need to strip the comments before we can get a useful diff of > > solrconfig.xml or schema.xml. Can you recommend tools to normalize XML > > files? XMLStarlet is hosted on SourceForge, which I no longer trust, and > > hasn't been updated in years. > > > > > > On Fri, May 3, 2019 at 4:24 PM Shawn Heisey <apa...@elyograg.org> wrote: > > > > > On 5/3/2019 1:44 PM, Erick Erickson wrote: > > > > Then git will let you check out any previous branch. 4.2 is from > before > > > we switched to Git, co I’m not sure you can go that far back, but 4x is > > > probably close enough for comparing configs. > > > > > > Git has all of Lucene's history, and most of Solr's history, back to > > > when Lucene and Solr were merged before the 3.1.0 release. So the 4.x > > > releases are there: > > > > > > -------------------- > > > elyograg@smeagol:~/asf/lucene-solr$ git checkout > > > releases/lucene-solr/4.2.1 > > > Checking out files: 100% (13209/13209), done. > > > Note: checking out 'releases/lucene-solr/4.2.1'. > > > > > > You are in 'detached HEAD' state. You can look around, make > experimental > > > changes and commit them, and you can discard any commits you make in > > > this state without impacting any branches by performing another > checkout. > > > > > > If you want to create a new branch to retain commits you create, you > may > > > do so (now or later) by using -b with the checkout command again. > > Example: > > > > > > git checkout -b <new-branch-name> > > > > > > HEAD is now at 50c41a3e5c Lucene Java 4.2.1 release. > > > -------------------- > > > > > > Thanks, > > > Shawn > > > > > >
