Quick question: Would the user have to do anything to migrate from the 2.1.x version to the 2.2.x versions. I specifically DIDN'T merge this down cause at the time, you were still investigating how people that use JDOM might be impacted. I know you and talked about trying to auto-detect the JDOM usage and have it "just work", but I don't remember how you made out on that.
If current stuff will "just work", I have absolutely no problem merging it down. I just didn't want a bunch of things that worked with 2.1.3 to stop working with 2.1.4 without changing a bunch of config. Dan On Tue February 17 2009 8:50:45 am Benson Margulies wrote: > The trunk version of Aegis is (again) significantly different from the > 2.1.x branch, insofar as I modified it to use XmlSchema instead of the > DOM to assemble and manage schema. Which is in turn significantly > different from 2.0.x, which has the old straight port from XFire. > > Here we have a JIRA noting something broken in 2.1.x. The whole reason > to do the XmlSchema rework was to put these problems behind us. > > Does anyone have any enthusiasm for tackling a backport of this stuff > to 2.1.x, which would imply bumping the dependency on XmlSchema to the > latest? I, for one, have a hard time finding time and motivation for > fixing the bug in the old code. After all, that's why I rewrote it. -- Daniel Kulp [email protected] http://www.dankulp.com/blog
