jkesselm commented on code in PR #101: URL: https://github.com/apache/xalan-java/pull/101#discussion_r1359591340
########## pom.xml: ########## @@ -0,0 +1,194 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd";> + <packaging>pom</packaging> + <!-- KNOWN ISSUES: + "Production" jar/tar files? + Doclet and taglet (taglet working, but only for ./xalan?) + stylebook (currenly, see stylebook.docgen.sh) + + xalan-test compatibility/success/submodule + + NOTE: To get dependency tree from a multi-module project, use the + command "mvn compile dependency:tree" so everything is in scope. + --> + + <modelVersion>4.0.0</modelVersion> + <groupId>apache-xalan-j-2.7.3-maint-main</groupId> + <artifactId>apache-xalan-j-2.7.3-maint-main</artifactId> Review Comment: Thanks for the suggestion. I wasn't sure how to handle that, given that what I've made sub-modules was just subdirectories broken out into separate jar files by the ant build script. Not sure how best to handle the version number so it gets into all the right file names and fields. It looks like Maven generates a Version class for the latter, which we could wrap our existing Version interface around...? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
