You really would have to fork and use bootclasspath only for unit tests, because the changes that would allow you to swap different XSLT implementations all still have to conform the JAXP APIs--there are no compilation changes. That would help lower the impact of such a change.
For unit testing it would be important to be able to declare a dependency on a more recent/improved implementation of a swappable component like Xalan in the project and have this reflected in tests. --kd >It seems to me that one way to resolve these type of issues would be to >allow a <bootclasspath/> element, or something similar, within the ><dependency> tags. I suppose that maven would have to fork the javac >process in order to take advantage of this, but at least it would keep >the information in one place. > ============================================================================== This e-mail is intended only for the use of the addressees. Any copying, forwarding, printing or other use of this e-mail by persons other than the addressees is not authorized. This e-mail may contain information that is privileged, confidential and exempt from disclosure. If you are not the intended recipient, please notify us immediately by return e-mail (including the original message in your reply) and then delete and discard all copies of the e-mail. Thank you. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
