Hi Joe, A normal Maven build creates a main jar and a test jar, you don't have to do anything special, assuming the files are in the standard directory layout for Maven.
I encourage you to follow Maven convention, otherwise you'll end up with thousands of lines of XML. Gary On Sun, Sep 10, 2023, 5:16 AM Joseph Kessselman <kesh...@alum.mit.edu> wrote: > I'm still working on excluding things from the Maven-generated xalan.jar > which weren't present in the Ant-generated version. > > Currently, the main nuisance is that Maven is putting classes from > javax/annotation into the xalan jarfile. This is probably because one of > the dependencies is missing the "provided" mark, but I haven't yet > figured out which. > > Once I get that straightened out, I should be able to start testing > xsltc and see how much of a mess I've made out of the JFlex adaptation. > > And if a miracle happens and _that_ can be made to work, all that should > still be needed is jarfile aggregation at the top-level directory, > dealing with samples, and (arguably) moving xalan-test into the > xalan-java project. > > (Yes, we theoretically separated xalan-test from xalan-java because the > plan was to have xalan-test reusable for other XPath/XSLT processors. I > don't know whether anyone is actually still using that, or whether > they'd care a lot about having to fetch all of xalan-java to get the > tests.) > > > We've reached the hour where it has stopped getting late and started > getting early. Time for me to fall over before I make _egregiously_ > stupid mistakes. Hasta pronto... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org > For additional commands, e-mail: dev-h...@xalan.apache.org > >
