Open issues:

1) Do we have, or can we find, anyone willing to tackle getting the "site" generation part of the maven build working? Doclets, taglets, stylebook... it's a bit of a nuisance and honestly I'd rather not deal. (We might be able to leave the documentation build in Ant for now, or handcode it, and port it later, but ... emphatic ugh.)

2) If we move xalan-test into xalan-java, we also need to think about making it look more like the test frameworks Maven is used to invoking. Not sure what the least-effort way of doing that would be, or if this is another case of "just handcode it for now". We should also separate the serializer tests, xalan tests, and sample tests (if there are any), since each module should carry its own tests.


Deferred issues:

1) I'm not bothering to separate out all the individual xsltc*.jar files, just shoving them all into samples.jar. Realistically, given today's storage and networks, I don't think it's worth breaking out those subsets right now. We can deal with it later if folks feel it's still desirable.

2) I'm not worrying about exactly matching filenames for the jars to those produced by the Ant build. If we're going with Maven, better to follow Maven naming conventions, I think. I'm also not (yet?) bothering to aggregate them all up to the top-level project, or to deal with the production of .tar and .zip files, though we might want to consider gzipping the jarfiles for convenience. We *could* make the aggregation stage deal with renaming, eg copying xalan/target/xalan-*-SNAPSHOT.jar to target/xalan.jar for the convenience of users who prefer the old names, but I'm not sure it's worth the effort.

3) I don't know whether source for the doclet and taglet jarfiles exists anywhere; we don't seem to have it. The taglet's relatively simple and could probably be decompiled and reconstructed easily; the doclet is considerably larger. I suspect both of them are based on standard Apache documentation tools, but haven't gone digging. More "binary dependencies" to be resolved...

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

Reply via email to