HannesWell opened a new issue, #277: URL: https://github.com/apache/maven-archetype/issues/277
### New feature, improvement proposal Currently archetype-common uses `jdom2` in the `MavenJDOMWriter` and associated utility classes, AFAICT mainly write a pom in `DefaultPomManager.writePom()`. In order to reduce the dependency footprint, would it be possible to migrate off jdom2 and use the DOM-parser/builder built into the JDK instead? Or are there particular reasons to use jdom(2) instead? If you consider `MavenJDOMWriter` or the associated utility classes as part of the API, for now, it could just be deprecated and a colocated `MavenDOMWriter` could be added, which is used by archetype and the dependency to jdom2 could be made optional. -- 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: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
