jkesselm commented on PR #101:
URL: https://github.com/apache/xalan-java/pull/101#issuecomment-1763486829

   Well, grump.
   
   Discovered that xalan-test apparently has a bunch of dependencies on stuff 
in xalan-java/lib. Eliminating those binaries was a large part of the reason 
for moving to Maven in the first place. My testing's been working fine because 
I've been **overwriting** a "normal" xalan-java with the jarfiles from 
xalan-java-mvn, so those dependencies were still being met.  When I **replace** 
xalan-java with xalan-java-mvn, the missing libs cause smoketest to fail.
   
   Cleanest stopgap solution I see would be to copy the old xalan-java/lib into 
xalan-test/lib and fix the test's paths to look there. That should mostly be a 
no-op for testing pre-Maven Xalan, outside of the risk of the libraries getting 
out of synch -- but since we don't intend to allow the duplication to last very 
long, I think it's acceptable.
   
   **PLEASE OBJECT LOUDLY AND SUGGEST ALTERNATIVES** if you think that's a bad 
idea and have a better solution (short of mavenizing xalan-test, which I'm 
trying not to do just yet. Otherwise I'll move ahead with that, get it 
committed, then come back to this changeset.
   
   (We're all committed here. Or should be.)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org

Reply via email to