Todd O'Bryan

I hit an error with this today. Was very confusing. As a stop-gap, don't have `refreshVersions migrate` replace this if it can't do anything about it. :-)

Yeah. I would be really impressed if the migration tool could handle this. I was just suggesting that it "first do no harm." When you have to force a certain...

Seeing a similar issue with `resolutionStrategy.force(...)` being replaced with an underscore, but then `refreshVersions` doesn't fill it in with the appropriate version.

Bump on this. Our workaround is to specify that we use 2.12.2 for Xerces, but some devs are asking why we just don't dump Xom for a more actively maintained...

Can't you just default to Xerces 2.12.2 and have a way for users to specify an older version if they'd like? The issue is that we have customers who require...

Are there tests that should fail in Xom if we force Xerces 2.12.2? I tried to do that and didn't see any, but I'm not sure I succeeded at changing...

We ended up having to get rid of Xom because Xalan had a vulnerability and no path to upgrade. We're back to only using the functionality provided in the JDK....

To make matters worse, ktlint seems to be causing the problem and then complaining that it can't fix it. I'm using KotlinPoet to generate some code. The code that comes...

I think the problem is the one identified in this paper: https://tratt.net/laurie/research/pubs/html/tratt__direct_left_recursive_parsing_expression_grammars/ That talks about an interaction with left- and right-hand recursion and identifies a problem with the Warth et...

Ah, no problem. I wish JetBrains would come out with some better K2 plugin docs. :-)