Gianugo Rabellino wrote:
My first suggestion remains the same, just the players are different.Sam Ruby wrote:Just to be clear: the *purpose* of gump is to alert developers of situations where some package that they are depending on is making an incompatible change that will likely affect them in the future.This was clear to me, but my question actually was a bit different: I'm confident that we can find a way to work together between Xindice and Xalan, and it's our (Xindice, not Xalan) fault for not having done it before: we should have got in touch with the Xalan team way before, alerting them that we were using their internal APIs.
My recommendation is that some of the developers of Xindice (an ASF project) actually talk to some of the developers of Xalan (another ASF project) to see if there is some way that the needs of users of Xinidce (which by necessity are users of Xalan) for backwards compatibility can be met.
But this said, our problem is different because we have a third party jar (Xupdate) on which we have little or no control (not being in itself an ASF project) and that is failing with recent version of Xalan. To further complicate things, the XUpdate project ATM seems like a dead horse, so we have to stick to what we got in the short term.
If Xalan has made a change which breaks usage out in the real world (in this case XUpdate), then this is something that should be investigated. Perhaps this change is required, perhaps it was unintentional. So perhaps it can be mitigated and/or corrected.
So we have (for the moment) to keep an old xalan version in CVS, since Xindice as a whole would fail if Xupdate is broken, but this also means that we can't patch our code to support most recent Xalan versions.It is possible to configure gump to use this old xalan version, or any other jar that you have checked into cvs. Simply declare a project without any build instructions and depend on it. You can find a number of examples of this at the bottom of the cococoon project definition:
http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-gump/project/xml-cocoon2.xml?content-type=text/plain
This being said, it is my preference that all other avenues be exhausted before this is done.
The file to be updated is http://cvs.apache.org/viewcvs/jakarta-gump/project/xml-xindice.xml, and the jakarta-gump cvs is open to all ASF committers.
- Sam Ruby
